95edaaab06
The current initiator object for CADF notifications does not include the username of the user who initiated the action, which leads to issues when using an LDAP backend and not having a direct way to map a username to a user id. This change makes it so that the initiator object for CADF notifications always contains the username for a user as well as the user id. This follows along with the CADF standard for OpenStack[0]. [0] https://www.dmtf.org/sites/default/files/standards/documents/DSP2038_1.1.0.pdf#page=12 Closes-Bug: #1856904 Change-Id: I833e6e0d7792acf49f816050ad7a63e8ea4f702f
10 lines
457 B
YAML
10 lines
457 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`Bug 1856904 <https://bugs.launchpad.net/keystone/+bug/1856904>`_]
|
|
The initiator object for CADF notifications now will always contain the
|
|
username for the user who initated the action. Previously, the initator
|
|
object only contained the user_id, which lead to issues mapping to users
|
|
when using LDAP-backed identity providers. This also helps the initiator
|
|
object better conform to the OpenStack standard for CADF.
|