List of operator actions that need explicit approval. Any operator action not in the pre-approved list will require explicit approval. Access requests associated with a resource governed by this operator control will be require explicit approval if the access request contains any operator action in this list.
List of user groups who can approve an access request associated with a target resource under the governance of this operator control.
List of users who can approve an access request associated with a target resource under the governance of this operator control.
The OCID of the compartment that contains the operator control.
Defined tags for this resource. Each key is predefined and scoped to a namespace.
Description of operator control.
List of emailId.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
The OCID of the operator control.
Whether the operator control is a default Operator Control.
Whether all the operator actions have been pre-approved. If yes, all access requests associated with a resource governed by this operator control will be auto-approved.
Description associated with the latest modification of the operator control.
The current lifecycle state of the operator control.
Number of approvers required to approve an access request. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Name of the operator control. The name must be unique.
List of pre-approved operator actions. Access requests associated with a resource governed by this operator control will be automatically approved if the access request only contain operator actions in the pre-approved list.
resourceType for which the OperatorControl is applicable
System message that would be displayed to the operator users on accessing the target resource under the governance of this operator control.
Time when the operator control was created expressed in RFC 3339 timestamp format. Example: '2020-05-22T21:10:29.600Z'
Time when deleted expressed in RFC 3339timestamp format. Example: '2020-05-22T21:10:29.600Z'. Note a deleted operator control still stays in the system, so that you can still audit operator actions associated with access requests raised on target resources governed by the deleted operator control.
Time when the operator control was last modified expressed in RFC 3339 timestamp format. Example: '2020-05-22T21:10:29.600Z'
Operator Access Control enables you to grant, audit, or revoke the access Oracle has to your Exadata Cloud@Customer infrastructure, and obtain audit reports of all actions taken by a human operator, in a near real-time manner.