Jens,
Is that something that is done in certain devstack jobs? I've been trying to recreate this with tempest + keystone setup by devstack locally, where the revocation events are stored in sql [0].
[0] https://github.com/openstack/keystone/blob/64925bf698cb45fde3c0941cfcbec5b45d31a0d7/keystone/common/config.py#L348-L353
Jens,
Is that something that is done in certain devstack jobs? I've been trying to recreate this with tempest + keystone setup by devstack locally, where the revocation events are stored in sql [0].
[0] https:/ /github. com/openstack/ keystone/ blob/64925bf698 cb45fde3c0941cf cbec5b45d31a0d7 /keystone/ common/ config. py#L348- L353