text
stringlengths 65
20k
|
|---|
Users can then access services and perform operations based on the policies set for the groups in which they are members.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.As an administrator, follow these main steps: Create an Oracle Cloud Infrastructure Group and Users Create an Oracle Cloud Infrastructure Policy Assign Policies to Oracle Integration Service Role Groups Create an Oracle Cloud Infrastructure Group and Users To create an instance administrator group in Oracle Cloud Infrastructure IAM and add users to it: 1.Open the navigation menu and click Identity & Security .Under Identity , click Groups .2.Click Create Group .3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later. |
Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.As an administrator, follow these main steps: Create an Oracle Cloud Infrastructure Group and Users Create an Oracle Cloud Infrastructure Policy Assign Policies to Oracle Integration Service Role Groups Create an Oracle Cloud Infrastructure Group and Users To create an instance administrator group in Oracle Cloud Infrastructure IAM and add users to it: 1.Open the navigation menu and click Identity & Security .Under Identity , click Groups .2.Click Create Group .3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @. |
As an administrator, follow these main steps: Create an Oracle Cloud Infrastructure Group and Users Create an Oracle Cloud Infrastructure Policy Assign Policies to Oracle Integration Service Role Groups Create an Oracle Cloud Infrastructure Group and Users To create an instance administrator group in Oracle Cloud Infrastructure IAM and add users to it: 1.Open the navigation menu and click Identity & Security .Under Identity , click Groups .2.Click Create Group .3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information. |
Under Identity , click Groups .2.Click Create Group .3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later. |
2.Click Create Group .3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user. |
3.In the Create Group screen, assign a name to the group (for example, oci-integration- admins ), and enter a description.2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery. |
2-1 4.Click Create .5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy. |
5.Add users to your new group so they can create and manage Oracle Integration instances.a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here. |
a.Open the navigation menu and click Identity & Security .Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later. |
Under Identity , click Users .b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group. |
b.Click Create User .c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation. |
c.Complete the following entries and click Create .Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group . |
Name: A unique name or email address for the user.The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add. |
The name must be unique across all users in your tenancy.You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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. |
You cannot change this value later.The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security . |
The name must meet the following requirements: no spaces, only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies . |
Description: This value could be the user's full name, a nickname, or other descriptive information.You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy . |
You can change this value later.Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description. |
Email: Enter an email address for the user.This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment . |
This email address is used for password recovery.The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .You can create separate groups for different permissions, such as a group with read permission only. |
The email address must be unique in the tenancy.If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .You can create separate groups for different permissions, such as a group with read permission only.Want to learn more about policies? |
If the user forgets their password, they can click Forgot Password on the sign on page, and a temporary password is generated and sent to the email address provided here.The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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. |
The user or an administrator can also update the email address later.d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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). |
d.On the user details page, add users to the group.Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration. |
Note: For more information, see Managing Users in the Oracle Cloud Infrastructure Documentation.Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view). |
Click Groups .Chapter 2 Configure Access to Create and Manage Instances 2-2Click Add User to Group .Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details. |
Select the group from the drop-down list, and then click Add.Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances. |
Create 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.To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create . |
To create and assign a policy to the Oracle Cloud Infrastructure group: 1.Open the navigation menu and click Identity & Security .Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed. |
Under Identity , click Policies .2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed. |
2.Click Create Policy .3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups. |
3.In the Create Policy window, enter a name (for example, IntegrationGroupPolicy ) and a description.4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features. |
4.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 the admin domain to manage instance integration-instance in compartment OICCompartment .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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles . |
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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users. |
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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users . |
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 and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles. |
When defining policy statements, you can specify either verbs (as used in these steps) or permissions (typically used by power users).The read and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies. |
The read and manage verbs are most applicable to Oracle Integration.The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause. |
The manage verb has the most permissions ( create , delete , edit, move, and view).Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment . |
Verb Access read Includes permission to view Oracle Integration instances and their details.manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment . |
manage Includes all permissions for Oracle Integration instances.Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features. |
Chapter 2 Configure Access to Create and Manage Instances 2-3 5.Click Create .The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform. |
The policy statements are validated and syntax errors are displayed.Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups. |
Assign Policies to Oracle Integration Service Role Groups After an Oracle Integration instance has been created, create and assign a policy for each Oracle Integration service role and scope needed.Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance. |
Extend Oracle Integration permissions to Oracle Cloud Infrastructure users by creating groups for key Oracle Integration roles, adding users to the groups, then creating policies that grant access to specified resources and permissions to users in those groups.Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance. |
Oracle Integration provides a standard set of service roles, which govern access to features.See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations. |
See Oracle Integration Service Roles .To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance. |
To assign policies to Oracle Integration service role groups: 1.Create the appropriate groups and users.See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed. |
See Create an Oracle Cloud Infrastructure Group and Users .Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it. |
Depending on the Oracle Integration features your organization uses, you may need to create groups for some or all of the roles.For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything. |
For example, you might create and name groups as follows: OICServiceAdministrators to grant admin permissions in service instances OICServiceDevelopers to grant developer permissions in service instances OICServiceInvokers to grant service invoke only permission to one instance OICServiceMonitors to grant monitor only permission to one or more instances 2.Create the appropriate policies.See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature. |
See Create an Oracle Cloud Infrastructure Policy .Chapter 2 Configure Access to Create and Manage Instances 2-4Syntax: allow group group_name to be service_role for resource-type in compartment compartment-name Note: You can also restrict access to a specified instance by including an optional where clause.Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications. |
Description Example Policy Grant the ServiceAdministrator role for a compartmentallow group OICAdminGroup to be ServiceAdministrator for integration-instances in compartment OICCompartment Grant the ServiceDeveloper role for a compartmentallow group OICDeveloperGroup to be ServiceDeveloper for integration-instances in compartment OICCompartment Grant the ServiceInvoker role for an Oracle Integration instanceallow group OICInvokerGroup to be ServiceInvoker for integration-instances in compartment OICCompartment where all {target.app.name='test-instance1', target.app.type='integration-instances'} Here the where clause grants users assigned to group OICInvokerGroup the ServiceInvoker role to one Oracle Integration instance identified by its instance name and created in OICCompartment .Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything. |
Grant the ServiceMonitor role for two Oracle Integration instancesallow group OICMonitorGroup to be ServiceMonitor for integration-instances in compartment OICCompartment where any {target.app.name='test-instance1', target.app.name='instance-prod-1'} This policy grants the ServiceMonitor Role to the OICMonitorGroup group over two instances identified by their respective names in OICCompartment .Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations. |
Oracle Integration Service Roles Oracle Integration predefined roles govern access to various Oracle Integration features.The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration. |
The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform.You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface. |
You can assign one or more of the predefined roles to Oracle Integration users and groups.Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs. |
Oracle Integration Description ServiceAdministrator A super user who can manage and administer the features provisioned in an Oracle Integration instance.ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details. |
ServiceDeveloper Develops the artifacts specific to the features provisioned in an Oracle Integration instance.A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages. |
A developer can create integrations.ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance. |
ServiceMonitor Monitors the features provisioned in an Oracle Integration instance.For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user. |
For example, a user assigned this roled can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed.This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features. |
This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it.This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent. |
This user role does not grant permissions to change anything.ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials. |
ServiceDeployer Publishes the artifacts developed in a feature.This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported. |
This role is not applicable for the Integrations feature.Chapter 2 Configure Access to Create and Manage Instances 2-5Oracle Integration Description ServiceUser Privileges to utilize only the basic functionality of a feature such as access to the staged and published applications.For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile. |
For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can't edit or modify anything.The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console. |
The user can also run integrations.ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available. |
ServiceInvoker Invokes any integration flow in an Oracle Integration instance that is exposed through SOAP/REST APIs or a scheduled integration.A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance. |
A user with ServiceInvoker role cannot: Navigate to the Oracle Integration user interface or perform any administrative actions in the user interface.Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access. |
Invoke any of the documented Oracle Integration REST APIs.ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke. |
ServiceViewer Navigates to all Oracle Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details.The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed. |
The user cannot edit any resources or navigate to the administrative setting pages.In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one. |
In Oracle Integration, when you assign a role to a user, the user is granted that role for all Oracle Integration features provisioned on an instance.Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password. |
Further, each role grants different privileges for different features to the same user.Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token. |
Note that not all Oracle Integration predefined roles are available in all features.Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL . |
Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments Configure OAuth 2.0 or Basic Authentication using client credentials, and configure a connectivity agent.Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane. |
Topics: Configure OAuth 2.0 Authentication Using Client Credentials Configure Basic Authentication Using Client Credentials Configure the Connectivity Agent Configure OAuth 2.0 Authentication Using Client Credentials To configure OAuth 2.0 authentication for invoking Oracle Integration APIs, configure and use client credentials.For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc. |
For OAuth authentication in Oracle Cloud Infrastructure in government environments, client credentials is the only authorization grant flow supported.OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty. |
OAuth client credentials grant flow semantics are built into Oracle Cloud Infrastructure's IAM and scoped to an IAM user profile.Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar. |
Any user can create an OAuth 2.0 client credentials user for their user account using the Oracle Cloud Infrastructure Console.To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize? |
To configure OAuth client credentials, follow these main steps: Gather Needed Information Generate the Client Credentials Obtain an OAuth Bearer Token Use the Bearer Token to Invoke Oracle Integration APIsChapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-6Gather Needed Information Ensure you have the information described in the following table available.Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers. |
Field Description Example Value Instance (friendly URL)The friendly URL of your Oracle Integration instance.On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe. |
On the Integration Instance Details page , this is the value of the Service Console URL .https://canary02- oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud .com/ic/home Audience (permanent URL)The unique URL of the Oracle Integration resource this client is allowed to access.This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential. |
This value is automatically populated by the OAuth resource selector.https:// 1403FE2A654445B7AAC83480F67E 8C48.0001.integration.dev.oc p.oc-test.com:443 Scope The applications you want this client to invoke or the APIs of the service instances you want to invoke.Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once. |
Scopes relevant for Oracle Integration are listed.You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security . |
You can use either one.This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users . |
This value is automatically populated by the OAuth resource selector.urn:opc:resource:consume r::all /ic/api/ Associated UPI stripeThe associated UPI stripe for the Oracle Integration instance, along with its admin user and admin password.This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update. |
This is used to obtain an OAuth 2.0 token.To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed. |
To find the UPI stripe: 1.On the Integration Instance Details page , copy the Service Console URL .For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user. |
For example: https://canary02-oicnusgovacc01- lf.0002.integration.us- langley-1.ocp.oraclegovcloud.com/ic/home 2.Open a browser window, then right-click on the browser and select Inspect to open the developer tools pane.3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level. |
3.In the developer tools pane, click the Network tab, then click Doc.Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential . |
Make sure that the Filter field is empty.4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed. |
4.Paste the service console URL from step 1 into your browser address bar.5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields. |
5.In the developer tools pane, in the Name column, click the authorize?call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy. |
call, then click Headers.The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access. |
The first part of the Request URL specifies the UPI stripe.For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below. |
For example: https://idcs- df980486fe044f09a5428c7862e7b2b0.idcs.identity.u s-langley-1.oci.oraclegovcloud.comUPI stripe: https://idcs- df980486fe044f09a5428c78 62e7b2b0.idcs.identity.u s- langley-1.oci.oraclegovc loud.com Admin user: upi-test- admin-user Admin password: Welcome@123456Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-7Field Description Example Value Client ID The OCID of the generated OAuth 2.0 client credentials and can be retrieved from the UI next to the client credentials on the client credentials page.ocid1.credential.oc1..aaaaaa aaulplph33maqltcttppjoyb56jl m5asx5ikcojntvzj5mnvp25qnq Client Secret The secret generated when you generate the OAuth 2.0 client credential.Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional. |
Copy it when it appears once.It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog. |
It isnt shown again; the only option is to regenerate another secret.i7BKNOG:1z1A)bqaY(]F Generate the Client Credentials To generate the client credentials: 1.Open the navigation menu and click Identity & Security .Under Identity , click Users .In the Name column, click the user name that you want to update.The User Details screen is displayed.To programmatically invoke an API, you typically create a client credential under a service account user.The credential must be created at the user level, not a group level.2.Under Resources , select OAuth 2.0 Client Credentials .Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-83.Click Generate OAuth 2.0 Client Credential .The Generate OAuth 2.0 Client Credential dialog is displayed.4.Use the resource selector to select an Oracle Integration instance and populate audience and scope fields.The resource selector dropdown lists all Oracle Integration instances across all subscribed regions in your Oracle Cloud Infrastructure tenancy.The list is further filtered by the compartments to which you have access.This view enables you to select the Oracle Integration instance that the client needs to invoke, and doing so automatically populates the audience and scope values, as shown below.Note that IAM users and by extension OAuth 2.0 client credentials are global, whereas Oracle Integration instances are created in a region and so are regional.Chapter 2 Configure OAuth Authentication in Oracle Cloud Infrastructure US Government Cloud Environments 2-9 5.Complete additional entries in the Generate OAuth 2.0 Client Credential dialog.For more information, refer to the table in Gather Needed Information . |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.