Gage Hugo 95edaaab06 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: I833e6e0d7792acf49f816050ad7a63e8ea4f702f		2020-01-09 15:55:48 +00:00
..
__init__.py	Always hash passwords on their way into the DB	2014-02-20 13:06:37 +00:00
test_cache.py	Distributed cache namespace to invalidate regions	2016-08-29 16:38:55 +00:00
test_database_conflicts.py	Finish refactoring self.*_api out of tests	2018-02-05 23:26:08 +00:00
test_json_home.py	Use https for docs.openstack.org references	2017-01-30 16:05:08 -08:00
test_notifications.py	Always have username in CADF initiator	2020-01-09 15:55:48 +00:00
test_provider_api.py	Fix RBACEnforcer get_member_from_driver mechanism	2018-09-10 13:32:14 -07:00
test_rbac_enforcer.py	Correcting tests with project_id	2019-02-13 14:32:19 +05:30
test_resource_options_common.py	Code-Defined Resource-specific Options	2017-01-25 16:15:44 -08:00
test_sql_core.py	Do not call `to_dict` outside of a session context	2017-01-25 06:12:20 +00:00
test_utils.py	Remove unused util function	2018-08-10 15:53:29 +00:00