Comment 3 for bug 1925239
Revision history for this message
| Zachary Buhman (zachary-buhman) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> The change and bug you linked were due to being unable to track users across openstack because all initiator.ids were just random uuids
The 1780503 description wasn't quite accurate. pre-fd8b5f3 all Keystone APIs, including /auth/tokens, the behavior was that initiator.id is random if x-auth-token is not present, and is non-random if it is present.
I referenced 1780503 because this seems to be where the semantics of "initiator" in Keystone changed, but because this semantics change isn't explicitly called out in the bug, I suspect this semantics change is not intentional.
My specific suggestion is that we reconsider/revert the semantics change.
1780503 instead would be implemented differently: the user in the request body would be logged as target.id instead.