-
Suggestion
-
Resolution: Low Engagement
-
4
-
At the moment, the org audit logs has events for create and revoke operations of Organization Admin API Keys.
date | location | actor | Created admin API key |
date | location | actor | Revoked admin API key |
However, the entries do not point to which admin API key was involved in the event. The event will be hard to track if there are multiple admin API keys configured for the organization.
Suggestion :
Include the following information on the admin API key audit logs (create and revoke)
- Name
- Creator
- Created Date
- Expiration Date
date | location | actor | Created admin API key <Details> |
date | location | actor | Revoked admin API key <Details> |
[ACCESS-1196] Add details on the admin API key to org audit logs
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: guard-s7 | New: cll-tf3202505 guard-s7 |
Remote Link | New: This issue links to "Page (Confluence)" [ 1003358 ] |
Support reference count | Original: 3 | New: 4 |
Labels | New: guard-s7 |
Remote Link | New: This issue links to "Page (Confluence)" [ 899259 ] |
Support reference count | Original: 2 | New: 3 |
Remote Link | Original: This issue links to "ENT-840 (Jira)" [ 668428 ] | New: This issue links to "ENT-840 (Hello Jira)" [ 668428 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 758287 ] |
Support reference count | Original: 1 | New: 2 |