The change and bug you linked were due to being unable to track users across openstack because all initiator.ids were just random uuids. This was observed in a deployment using LDAP backed users, it was impossible to track when users were authenticating and what they were doing, which is a huge issue when trying to audit.
> fd8b5f3 introduces a regression. Post-fd8b5f3, for authenticate events only, initiator.id is the user ID in the request body, and not the authenticating user.
The initiator has the user_id of the authenticating user, I am not sure what you mean here. Prior to the change it did not have the user id of the authenticating user, it was a random uuid.
Is there another scenario here that isn't quite working as expected?
The change and bug you linked were due to being unable to track users across openstack because all initiator.ids were just random uuids. This was observed in a deployment using LDAP backed users, it was impossible to track when users were authenticating and what they were doing, which is a huge issue when trying to audit.
> fd8b5f3 introduces a regression. Post-fd8b5f3, for authenticate events only, initiator.id is the user ID in the request body, and not the authenticating user.
The initiator has the user_id of the authenticating user, I am not sure what you mean here. Prior to the change it did not have the user id of the authenticating user, it was a random uuid.
Is there another scenario here that isn't quite working as expected?