- Provisioning and Administering Oracle Integration and Oracle Integration for SaaS, Generation 2
- Setting Up Users and Groups
- Setting Up Users and Groups in Cloud Accounts That Do Not Use Identity Domains
- Creating an Oracle Cloud Infrastructure Policy
Creating an Oracle Cloud Infrastructure Policy
Create a policy to grant permission to the users in a group to work with Oracle Integration instances within a specified tenancy or compartment.
This topic applies only to cloud accounts that do not use
identity domains. See About Setting Up Users and Groups.
- Open the navigation menu and click Identity & Security. Under Identity, click Policies.
- Click Create Policy.
- In the Create Policy window, enter a name (for example,
IntegrationGroupPolicy
) and a description. - In the Policy
Builder, select Show manual editor and enter the
required policy statements.
Syntax:
-
allow group
group_name
to
verb resource-type
in compartment
compartment-name
allow group
group_name
to
verb resource-type
in tenancy
Example:
allow group oci-integration-admins to manage integration-instance in compartment OICCompartment
This policy statement allows the
oci-integration-admins
group in theadmin
domain tomanage
instanceintegration-instance
in compartmentOICCompartment
.You can create separate groups for different permissions, such as a group with
read
permission only.Want to learn more about policies? See How Policies Work and Policy Reference, or click Help in the window.
-
When defining policy statements, you can specify either verbs (as used in these steps) or permissions (typically used by power users).
-
The
read
andmanage
verbs are most applicable to Oracle Integration. Themanage
verb has the most permissions (create
,delete
,edit
,move
, andview
).Verb Access read
Includes permission to view Oracle Integration instances and their details.
manage
Includes all permissions for Oracle Integration instances.
-
- If desired, you can add a policy to allow members of the group to view message metrics,
as described in Viewing Message Metrics.
For example:
allow group oci-integration-admins to read metrics in compartment OICPMCompartment
- If you intend to use custom endpoints, add one or more additional policy statements.
Otherwise, skip this step.Add policies that specify the compartment in which vaults and secrets reside and allow the admin group to manage secrets in it. See Configure a Custom Endpoint for an Instance.Note that you should specify the resource to return in
<resource-type>
, as described in Details for the Vault Service. Also note that Oracle Integration requires theread
verb only butmanage
is recommended if the same group will also be administering the secrets (uploading/lifecycle operations).Syntax:
allow group group-name to manage resource-type in compartment secrets-compartment
Examples:
-
allow oci-integration-admins to manage secrets in compartment SecretsCompartment
allow oci-integration-admins to manage vaults in compartment SecretsCompartment
-
- Click Create. The policy statements are validated and syntax errors are displayed.