Create User in OIC Easily

Share

Introduction

Creating users in an Oracle Integration Cloud instance is one of the most critical administrative tasks in any integration project. Whether you are onboarding a developer, assigning roles to a tester, or granting access to support teams, proper user management ensures secure and efficient usage of your integration platform.

In real-world Oracle Cloud implementations, especially in enterprise environments using Oracle Cloud Infrastructure, user provisioning is not just a one-time activity—it is part of ongoing governance, compliance, and security operations. If done incorrectly, it can lead to unauthorized access, integration failures, or audit issues.

This article provides a complete, practical, step-by-step guide on how to create users in Oracle Integration Cloud (OIC Gen 3), along with real project scenarios, best practices, and troubleshooting insights.


What is User Creation in Oracle Integration Cloud?

User creation in Oracle Integration Cloud is the process of provisioning user identities and assigning appropriate roles so that individuals can access and perform operations within OIC.

Unlike older middleware platforms, OIC does not manage users internally. Instead, it relies on OCI Identity and Access Management (IAM) for:

  • User authentication
  • Role-based access control
  • Security enforcement

This means that when you create a user for OIC, you are actually creating a user in OCI IAM and assigning OIC-specific roles.

Key Concept

OIC uses OCI IAM for identity management, not local user creation.


Key Features of User Management in OIC

Here are the major capabilities you should understand:

1. Centralized Identity Management

All users are managed centrally in OCI IAM, ensuring consistency across services.

2. Role-Based Access Control (RBAC)

Access is controlled via predefined roles such as:

  • ServiceDeveloper
  • ServiceAdministrator
  • ServiceMonitor

3. Fine-Grained Permissions

You can restrict access based on:

  • Integration design
  • Monitoring
  • Administration

4. Federation Support

Supports integration with corporate identity providers (Azure AD, Okta, etc.)

5. Secure Access with Policies

OCI policies control who can assign roles and manage users.


Real-World Integration Use Cases

Use Case 1: Developer Onboarding in a Project

In a live OIC implementation for a retail client:

  • New developers joined the project
  • Admin created users in OCI IAM
  • Assigned ServiceDeveloper role
  • Developers started building integrations immediately

Use Case 2: Production Support Access

A banking client needed:

  • Read-only access for support team
  • Assigned ServiceMonitor role
  • Ensured no accidental changes in production

Use Case 3: Controlled Admin Access

In a healthcare project:

  • Only 2 users were given ServiceAdministrator role
  • Prevented unauthorized configuration changes
  • Maintained audit compliance

Architecture / Technical Flow

Understanding the flow helps avoid confusion during implementation.

User Creation Flow

  1. User is created in OCI IAM
  2. User is assigned to a Group
  3. Group is mapped to Policies
  4. Policies grant access to OIC
  5. User logs into OIC instance

Logical Architecture

User → Group → Policy → OIC Access

Important Insight

You never directly assign permissions to users in OIC. Everything flows through OCI IAM groups and policies.


Prerequisites

Before creating users, ensure the following:

1. OCI Access

You must have access to:

  • OCI Console
  • Identity & Security module

2. Required Permissions

You should have:

  • IAM Admin privileges
    or
  • Policy allowing user creation

Example policy:

Allow group AdminGroup to manage users in tenancy

3. OIC Instance Availability

Ensure your OIC Gen 3 instance is:

  • Active
  • Accessible via URL

Step-by-Step: Create User in Oracle Integration Cloud (OIC Gen 3)

Step 1 – Login to OCI Console

Navigate to:

👉 https://cloud.oracle.com

Enter:

  • Username
  • Password
  • Tenancy

Step 2 – Navigate to Identity & Security

Navigation Path:

OCI Console → Identity & Security → Domains → Default Domain → Users


Step 3 – Create New User

Click on Create User

Enter the following details:

Field Example Value Description
Name john.doe Unique username
Description OIC Developer Optional
Email john.doe@company.com Required for notifications

Click Create


Step 4 – Assign User to a Group

After user creation:

  1. Open the user
  2. Click Groups → Add User to Group

Select appropriate group:

  • OIC_Developers
  • OIC_Admins
  • OIC_Monitors

Click Add


Step 5 – Create Group (If Not Exists)

Navigation:

Identity & Security → Groups → Create Group

Example:

Field Value
Name OIC_Developers
Description OIC Development Team

Step 6 – Create Policy for OIC Access

Navigation:

Identity & Security → Policies → Create Policy

Example Policy:

Allow group OIC_Developers to use integration-instances in compartment OIC_Compartment

For Admins:

Allow group OIC_Admins to manage integration-instances in compartment OIC_Compartment

Step 7 – Assign Roles in OIC

Once user logs into OIC:

Navigation:

OIC Console → Settings → Roles

Assign roles like:

  • ServiceDeveloper
  • ServiceAdministrator
  • ServiceMonitor

Step 8 – Send Login Credentials

OCI will:

  • Send email notification
  • Prompt user to set password

Testing the User Setup

After configuration, always validate access.

Test Scenario

User: john.doe
Role: ServiceDeveloper

Steps:

  1. Login to OIC URL
  2. Navigate to Integrations
  3. Try to create a new integration

Expected Result:

  • User should access design screen
  • Able to create integration
  • No admin-level access

Validation Checks

  • Can user see integrations?
  • Can user edit integrations?
  • Is access restricted correctly?

Common Errors and Troubleshooting

1. User Cannot Access OIC

Cause:

  • Missing policy

Solution:

  • Verify OCI policy syntax

2. User Logged In But No Permissions

Cause:

  • Role not assigned in OIC

Solution:

  • Assign ServiceDeveloper role

3. Group Assignment Missing

Cause:

  • User not added to group

Solution:

  • Add user to correct IAM group

4. Incorrect Compartment Access

Cause:

  • Policy mapped to wrong compartment

Solution:

  • Update policy with correct compartment

5. Email Not Received

Cause:

  • Wrong email or spam filter

Solution:

  • Reset password manually

Best Practices from Real Projects

1. Use Role-Based Groups

Instead of assigning roles individually:

  • Create groups like:
    • OIC_DEV
    • OIC_ADMIN
    • OIC_SUPPORT

2. Follow Least Privilege Principle

Never give admin access unless required.


3. Separate Environments

Use different groups for:

  • DEV
  • TEST
  • PROD

4. Naming Standards

Use consistent naming:

OIC_DEV_GROUP OIC_ADMIN_GROUP

5. Audit Regularly

Review:

  • Active users
  • Role assignments
  • Policy definitions

6. Use Federation (Advanced)

In large enterprises:

  • Integrate OCI with Azure AD
  • Avoid manual user creation

Real Consultant Insight

In one of the large telecom implementations:

  • Over 200 users were created manually
  • No grouping strategy was followed

Result:

  • Access issues
  • Security risks
  • Audit failures

After redesign:

  • Introduced group-based access
  • Reduced admin effort by 70%
  • Improved compliance

Summary

Creating users in Oracle Integration Cloud is not just a technical step—it is a foundational activity for secure and scalable integration architecture.

Key takeaways:

  • Always create users via OCI IAM
  • Use groups and policies for access control
  • Assign OIC roles after login
  • Test every user setup
  • Follow best practices for governance

For detailed official documentation, refer to:
https://docs.oracle.com/en/cloud/saas/index.html


FAQs

1. Can we create users directly in OIC?

No. Users must be created in OCI IAM and then granted access to OIC.


2. What is the difference between ServiceDeveloper and ServiceAdministrator?

  • ServiceDeveloper → Build integrations
  • ServiceAdministrator → Full control including settings

3. How many users can we create in OIC?

There is no strict limit, but it depends on OCI tenancy and licensing.


Share

Leave a Reply

Your email address will not be published. Required fields are marked *