<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Why PrivilegeRevoked Field Shows More Admin Roles than Expected

Okta Classic Engine
Okta Identity Engine
Administration

Overview

When an Admin role is revoked, the following is shown in the Okta system log when searching using the following query:

eventType eq "user.account.privilege.revoke"


Revoke user privilege 

Expanding one of the events, the PrivilegeRevoked field is seen populated with the following roles:

  • Super administrator
  • Organization administrator
  • Application administrator (all)
  • Application administrator
  • Read-only admin
  • User administrator (all)
  • User administrator
  • Help Desk administrator (all)
  • Help Desk administrator
  • Mobile administrator
  • API Access Management administrator
  • Report administrator
  • Group Membership administrator


Expended Event  

The goal of this article is to explain the contents of the PrivilegeRevoked field.

Cause

When no other roles remain assigned for a user, it is expected behavior to see all the Standard Admin roles in the PrivilegeRevoked field.

Solution

The Administrator Roles that are listed in the PrivilegeRevoked section do not represent the actual privileges that the user account had before revocation.

  • This is a general message that is logged for every user.account.privilege.revoke event, regardless of the actual administrator roles that were revoked. 
  • When no roles remain assigned for a user, the events will include all the roles and display them by default.
  • If any admin roles remain after revoking a user's admin role, the actual role(s) will be displayed.

Related References

Loading
Okta Support - Why PrivilegeRevoked Field Shows More Admin Roles than Expected