Bug 1041858 - [RFE][keystone]: List Revocation Events
Summary: [RFE][keystone]: List Revocation Events
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Udi Kalifon
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks: 1041856
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:44 UTC by RHOS Integration
Modified: 2016-04-26 14:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 13:35:37 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:44:38 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/revocation-events.

Description:

List the events that lead to revoked tokens instead of the revoked token ids

revocation events will be a tuple:  UserId, ProjectId, time.
The list of revocation events will only last until the project has expired.
Revocation lists will be grouped by domain id or project id

As a consequence of this blueprint, GET /v3/auth/tokens/OS-PKI/revoked should be deprecated.

This will close bug 1242620.

Specification URL (additional information):

https://etherpad.openstack.org/keystone-revocation-events

Comment 2 Udi Kalifon 2014-04-09 14:10:00 UTC
Arthur, is this listing of revocation events something internal, or is there a use case we can test it with? How can we see the events (is there an API for it or can we write a small listener that shows the events)?

Comment 3 Arthur Berezin 2014-04-29 08:36:02 UTC
Deferring to the father of the feature

Comment 4 Udi Kalifon 2014-04-30 13:26:38 UTC
Adam's answer:
ukalifon, don't bother testing the internal events...that BP was written in support of the revocation events


Note You need to log in before you can comment on or make changes to this bug.