commit bd983f0c7339d30da834c26d6aeacab05a7adaff
Author: Gage Hugo <email address hidden>
Date: Fri Dec 13 14:25:28 2019 -0600
Always have username in CADF initiator
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].
Reviewed: https:/ /review. opendev. org/705334 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=bd983f0c733 9d30da834c26d6a eacab05a7adaff
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit bd983f0c7339d30 da834c26d6aeaca b05a7adaff
Author: Gage Hugo <email address hidden>
Date: Fri Dec 13 14:25:28 2019 -0600
Always have username in CADF initiator
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: I833e6e0d7792ac f49f816050ad7a6 3e8ea4f702f 61411ef97bc2545 d86d579215)
(cherry picked from commit 95edaaab06c6da7