Super Admin Restoration
The Super Admin role is a predefined administrative role and the only role with full administrative permission for the entire deployment. A Super Admin can:
- Delegate roles to all other administrators.
- Create the security domain hierarchy.
The Super Admin is created during deployment. Only a Super Admin can perform certain critical tasks. A deployment must have at least one Super Admin.
If a Super Admin is deleted, use the Super Admin Restoration utility, restore-admin, to create a new Super Admin. RSA recommends that you assign the Super Admin role to only the most trusted administrators.
You need to restore a Super Admin if any of the following conditions exist:
- The sole Super Admin has been deleted from the deployment.
- No users have been assigned the Super Admin role.
- The sole Super Admin has been locked out.
If a Super Admin has been locked out, recovery can occur in any of the following ways:
- Another Super Admin can manually unlock the Super Admin.
- If the lockout policy that applies to the Super Admin allows auto-unlock, you can wait for lockout to expire.
If the previous methods fail, use the Super Admin Restoration utility. For more information, see Restore the Super Admin.
Related Articles
Add a Super Admin 54Number of Views Restore the Super Admin 194Number of Views Authentication error with LDAP user assigned the Super Admin role while providing additional credentials to the RSA Authen… 208Number of Views How to add a new admin to RSA Web Express 2Number of Views AveksaAdmin Super Account Locked or Password Lost in RSA Governance & Lifecycle 1.79KNumber of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Indirect Relationship Processing fails with ORA-30926 and 'ORA-06512: at "AVUSER.CE_USERS" ' errors when collecting Groups…