Hide Forgot
It was reported [1] that if a domain is invalidated (which generates a revocation event), that revocation event won't match domain-scoped tokens so those tokens won't be revoked. This is because the code to calculate the fields for a domain-scoped token don't use the domain-scope so that information can't be used when testing against the revocation events. CVE request has been sent to oss-security by upstream [2] Upstream commit that fixes this issue: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c4447f16da036fe878382ce4e1b05b84bdcc4d4e [1]: https://bugs.launchpad.net/keystone/+bug/1349597 [2]: http://seclists.org/oss-sec/2014/q3/296
It's stated in the Launchpad ticket that this would only impact Icehouse (openstack-2014.X) since that's where revocation events were added.
Statement: This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0.
Keystone in RHEL-OSP-5 (Icehouse) includes this code, although it is marked as experimental in Icehouse upstream, we do include an example of how to enable it in our documentation and thus will need to release an erratum.
IssueDescription: It was discovered that domain-scoped tokens were not revoked when a domain was disabled. Only OpenStack Identity setups configured to make use of revocation events were affected.
This issue has been addressed in following products: OpenStack 5 for RHEL 6 Via RHSA-2014:1122 https://rhn.redhat.com/errata/RHSA-2014-1122.html
This issue has been addressed in following products: OpenStack 5 for RHEL 7 Via RHSA-2014:1121 https://rhn.redhat.com/errata/RHSA-2014-1121.html