Setting Up Users and Groups in Cloud Accounts That Do Not Use Identity Domains

For a cloud account in a region not yet updated to use identity domains prior to the creation of the cloud account, users and groups are set up in Oracle Cloud Infrastructure Identity and Access Management (IAM) and Oracle Identity Cloud Service (IDCS).

Note

This section applies only to cloud accounts that do not use identity domains. If you are not sure if your cloud account uses identity domains, see About Setting Up Users and Groups.

For more information about Oracle Cloud Infrastructure IAM, IDCS, and the documentation that provides the information you need, see Documentation to Use for Cloud Identity in Overview of Identity and Access Management in the Oracle Cloud Infrastructure documentation.

Without identity domains, roles are assigned to IDCS groups, then linked to Oracle Cloud Infrastructure IAM groups using federation, as illustrated in the following diagram.


Description of idcs-iam-config.png follows

Understanding Oracle Visual Builder Federation

If your cloud account does not use identity domains, Oracle Cloud Infrastructure Identity and Access Management (IAM) must be federated with Oracle Identity Cloud Service (IDCS) for your tenancy.

User federation refers to linking a user's identity and attributes across multiple identity management systems. Oracle Visual Builder federation means that identities are linked in IDCS and Oracle Cloud Infrastructure Identity and Access Management (IAM).

Oracle Visual Builder uses both IDCS and IAM to manage users and groups:

  • Create and manage users in IDCS. By default, most tenancies are federated with IDCS. For more information about Oracle Identity Cloud Service, see Understanding Administrator Roles in Administering Oracle Identity Cloud Service.

  • Manage permissions using policies in Oracle Cloud Infrastructure's IAM service.

For background information on federation with IDCS, see Federating with Identity Providers and Federating with Oracle Identity Cloud Service.

Whether your tenancy needs federation depends on several factors, such as when your cloud account was created and the Oracle Visual Builder version you're provisioning. Your tenancy may be:

  • Already fully federated: Nearly all accounts in regions that have not yet been updated to use identity domains fall into this category. You'll follow standard steps to set up users and groups, as described in the topics in this section.

  • Mostly federated: If you have an older account that was created before 21 December 2018, you may need to complete a final federation step. You'll follow steps to set up users and groups, as described in the topics in this section. At the mapping step (Mapping the IDCS and OCI Groups), you'll be asked to enter information.

  • Needing federation: If you’re configuring Oracle Visual Builder with a government SKU in a commercial data center, you'll likely need to perform manual federation steps as part of setting up users and groups. See Manually Federating Your Tenancy.

Not sure about your federation? See Is My Tenancy Federated Between Oracle Cloud Infrastructure IAM and Oracle Cloud Identity Service?

Create IDCS Groups and Users

To grant access to Visual Builder instances, assign the users a Visual Builder role. You can grant the role individually to each IDCS user, or create an IDCS group of users and assign the role to the group. You can create Oracle Identity Cloud Service groups for later mapping them to Oracle Cloud Infrastructure Identity and Access Management identities.

Before you create users or groups, learn about available Oracle Visual Builder Roles and Privileges.
  1. Sign in to the OCI Console.
  2. In the upper-left corner, click Navigation Menu the Menu icon.
  3. Select Identity & Security and then under Identity, select Federation.

    The Federation screen is shown, and includes the identity provider, called OracleIdentityCloudService. This is the default federation between the Oracle Identity Cloud Service stripe and the OCI tenancy in a cloud account.

  4. Click OracleIdentityCloudService.
  5. Create IDCS users and groups, and add users to the groups.
  6. Click the Oracle Identity Cloud Service Console link.
  7. In the upper-left corner, click Navigation Menu the Menu icon and select Oracle Cloud Services.
  8. Click the Visual Builder service name.
  9. Click the Application Roles tab.
  10. Click the menu options icon shown next the role, and select Assign Users. If you want to assign the role to a group, select Assign Groups.
  11. Select the check box next to the name of each user or group that you want to add to the role, and then click OK.

Create Oracle Cloud Infrastructure Groups and Policies

To allow other non-admin users to create and manage Visual Builder instances, create an OCI group of non-admin users and assign them the correct OCI policies.

If you're a tenant administrator and plan to create Visual Builder instances yourself, skip this procedure.
  1. Sign in to the OCI Console.
  2. Open the navigation menu and click Identity & Security. Under Identity, click Groups.
  3. Create an OCI group.

    In the Create Group screen, assign a name to the group that differentiates it from the IDCS group (for example, oci-visualbuilder-admins), and enter a description.

  4. Create a policy with one or more of these statements:

    Table 3-1 Syntax for policy statements for a group

    Policy Syntax
    Allow the group to manage (create, delete, edit, move, and view) the Visual Builder instance in a compartment Allow group <group_name> to manage visualbuilder-instances in compartment <compartment-name>

    Here's an example:

    Allow group VBInstanceAdmins to manage visualbuilder-instances in compartment MyVBCompartment
    Allow the group to manage (create, delete, edit, move, and view) all Visual Builder instances of the tenancy Allow group <group_name> to manage visualbuilder-instances in tenancy

    Here's an example:

    Allow group VBInstanceAdmins to manage visualbuilder-instances in tenancy
    If you intend to use custom endpoints, allow the group to access secrets and vaults of a compartment.

    allow group <group-name> to manage secrets in compartment <secrets-compartment>

    allow group <group-name> to manage vaults in compartment <secrets-compartment>

    Here's an example:

    Allow group VBInstanceAdmins to manage secrets in compartment MySecretCompartment

    and

    Allow group VBInstanceAdmins to manage vaults in compartment MySecretCompartment

Mapping the IDCS and OCI Groups

You can now map your instance administrator group in IAM to your previously created IDCS group. For details, see Map the IDCS group with the OCI group.

  1. Open the OCI navigation menu and click Identity & Security. Under Identity, click Federation.
  2. On the Federation page, select the OracleIdentityCloudService link.
  3. From the Resources options, choose Group Mapping.
  4. Click Edit Mapping.
  5. In the Edit Identity Provider dialog, click Add Mapping at the bottom.
    1. If the following dialog appears prompting you to provide credentials, enter this information from the COMPUTEBAREMETAL IDCS application in your IDCS account. This dialog indicates that your tenancy is mostly federated and requires only this final step. See Understanding Federation. (If you aren't able to locate this information, file a service request to get help from Oracle Support.)
      Description of complete_federation.png follows

    2. Click Continue.
  6. Select your IDCS group in the Identity Provider Group field and your OCI group in the OCI Group field.
  7. Click Submit.

Adding and Assigning Oracle Cloud Infrastructure Users for Read Only Access

After creating a view only group and adding its policy, add users for read only access to Oracle Visual Builder instances.

  1. Add an OCI user.
    1. Open the navigation menu and click Identity & Security. Under Identity, click Users.
    2. Click Create User.
    3. Complete the fields to identify the user.

      Description of create_read_only_user.png follows

    4. Click Create.
  2. Assign the user to the read only group.
    1. Select Groups from the Identity options.
    2. Select the read only group you created (for example, oci-visualbuilder-viewers).
    3. Click Add User to Group.
    4. In the Add User to Group dialog, select the user you created and click Add.
  3. Create the user's password.
    1. From the Group Members table on the Group Details screen, select the user you added.
    2. Click Create/Reset Password. The Create/Reset Password dialog is displayed with a one-time password listed.
    3. Click Copy, then Close.
  4. Provide read only users the information they need to sign in.
    1. Copy the password in an email to the user.
    2. Instruct the read only user to sign in using the User Name and Password fields.
      Description of admin-oci-signin.png follows

    3. Upon signing in, the user will be prompted to enter a new password.
    4. View Visual Builder instances.
      Read only users can view Visual Builder instances by selecting Visual Builder in the navigation pane.

Assigning Oracle Visual Builder Service Roles to Groups

After a Visual Builder instance has been created, assign Visual Builder roles to groups of users in Oracle Visual Builder to allow them to work with the features of the Visual Builder instance.

Note

It's a best practice to assign Visual Builder service roles to selected groups rather than individual users.

Oracle Visual Builder provides a standard set of set of service roles, which govern access to features. Depending on the Visual Builder features your organization uses, you may choose to create groups named for the service role they are granted. For example, VBServiceAdministrators for administration permissions.

  1. Open the navigation menu and click Identity & Security. Under Identity, click Federation.
  2. On the Federation screen, select the OracleIdentityCloudService link to view the default Oracle Identity Cloud Service identity federation.
  3. On the Identity Provider Details page, select Groups from the Resources options.
  4. From the table, select an IDCS group to grant the users in the group access.
  5. On the Group Details page, click Manage Service Roles.
  6. On the Manage Service Roles page, locate your Visual Builder service (VISUALBUILDERAUTO). At the far right, click Task menu , and select Manage instance access.
    The Manage Access screen lists instances. Note that you must assign roles for each instance individually.
    • Instance names follow this format: displayname-tenancyid-regionid

    • Instance URLs follow this format: https://displayname-tenancyid-regionid.visualbuilder.ocp.oraclecloud.com/ic/home/
  7. From the Manage Access options, select instance roles for the group under one or more specified instances.
  8. Click Save Instance Settings, then Apply Service Role Settings.