Actions Supported by Identity Policy-based Authorization

Actions

Actions are specific operations that are allowed or denied in an identity policy.

• The Access Level column describes how the action is classified (list, read, or write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
• The Resource Type column indicates whether the action supports resource-level permissions.
  • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
  • If this column includes a resource type, you must specify the URN in the Resource element of your statements.
  • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

  For details about the resource types defined by CTS, see Resources.

• The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
  • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
  • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
  • If the Condition Key column is empty (-) for an action, the action does not support any condition keys.

  For details about the condition keys defined by CTS, see Conditions.

• The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for CTS.

Each API of CTS usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for CTS.

Conditions

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

• The condition key that you specify can be a global condition key or a service-specific condition key.
  • Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
  • Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, cts:) only apply to operations of the CTS service. For details, see Table 4.
  • The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
• A condition operator, a condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

The following table lists the condition keys that you can define in SCPs for CTS. You can include these condition keys to specify conditions for when your SCP is in effect.