Go to main content

Oracle MiniCluster S7-2 Security Guide

Exit Print View

Updated: October 2021
 
 

Role-Based Access Control

There is no root user in MiniCluster. Instead, root is a role and is assigned to MCMU users that are registered as primary administrators.

When you create an MCMU user, you assign the user one of these roles:

  • Primary admin (root role) – The root role defines the rights and privileges of primary administrators of the MiniCluster system including all its compute nodes, networks, database, and storage. Users with the root role can perform all installation and all critical administrative operations without any constraints. As primary administrators, they can delegate operations and approve adding and deleting users including new primary and secondary administrators. The user must login with his/her own credentials. All actions and operations carried out are logged and audited based on the user identifier, not the role identifier.

  • Secondary admin (mcadmin role) – This role defines the rights and privileges of secondary administrators of the MiniCluster domains and non-global zones. By default, this role only enables a read-only access to MCMU. All actions and operations carried out are logged and audited based on the user identifier, not the role identifier.

  • Tenant admin (tadmin role) – This role defines the rights and privileges of the administrator of a MiniCluster VM. The role defines the rights and privileges of a VM administer involved with day-to-day administrative operations supporting application installations and deployment. All actions are audited based on the user identifier, not the role identifier.

  • Auditor (auditor role) – Users with this role only have access to the MCMU BUI audit review page where they can view the audit pool status and generate reports for user activity. Only users with this role can access the audit review page. Auditors cannot access the MCMU (except for the audit page), nor can they log into kernel zones or VMs.