Skip to main content
SCIM (System for Cross-domain Identity Management) keeps Vikat in sync with Okta in real time — new users are provisioned, deactivated users are suspended, and group memberships are updated without waiting for the next login or background sync.
Complete SSO using OIDC before setting up SCIM. Okta does not support SCIM on a custom OIDC app, so SCIM runs as a separate app alongside your existing OIDC integration.

​
Step 1: Enable SCIM in Vikat

1

Open your Okta provider

In your Vikat dashboard, go to Governance → User Provisioning and open your configured Okta provider.
Vikat Okta provider dashboard showing connection details and attribute mappings

The Okta provider dashboard showing your connection details and attribute mappings.

2

Enable SCIM provisioning

Click the settings icon to open Provider Configuration.Toggle on Enable SCIM Provisioning and click Save & Enable.
Vikat Provider Configuration with Enable SCIM Provisioning toggle turned on

Enable SCIM Provisioning in Provider Configuration — the SCIM endpoint URL and token are generated after saving.

3

Copy the SCIM credentials

After saving, Vikat shows a Setup Complete dialog with:
  • SCIM Endpoint URL — the base URL Okta will send provisioning requests to
  • Provisioning Token — the bearer token Okta uses to authenticate
Copy both values now — you will need them in Step 3.
Vikat Setup Complete dialog displaying the SCIM Endpoint URL and one-time Provisioning Token

Setup Complete dialog showing the SCIM Endpoint URL and Provisioning Token.

The provisioning token is only shown once. Store it somewhere safe before closing this dialog. You can always rotate it later, but the previous token will immediately become invalid.

​
Step 2: Create a SCIM App in Okta

1

Browse the App Catalog

In the Okta Admin Console, go to Applications → Applications and click Browse App Catalog.
Okta Applications page with Browse App Catalog button highlighted

Click Browse App Catalog from the Applications page.

2

Add the SCIM 2.0 Test App

Search for SCIM 2.0 Test App (Header Auth) and add it.
Okta App Catalog search results with SCIM 2.0 Test App (Header Auth) highlighted

Select SCIM 2.0 Test App (Header Auth) from the catalog.

Name the app Vikat SCIM (or any label you prefer). On the sign-on options screen, skip everything and click Done — this app is used for SCIM provisioning only, not authentication.

​
Step 3: Configure the SCIM App

1

Connect the app to Vikat

Open the Vikat SCIM app and go to the Provisioning tab.Click Configure API Integration, check Enable API Integration, and enter:
  • SCIM 2.0 Base URL: the SCIM Endpoint URL from Step 1
  • API Token: the Provisioning Token from Step 1
Click Test API Credentials to verify the connection, then Save.
Okta SCIM app Configure API Integration dialog with Base URL and API Token fields filled in

Enter the SCIM Endpoint URL and Provisioning Token from Vikat to connect the app.

2

Enable provisioning actions

Still under the Provisioning tab, go to To App and enable:
  • Create Users
  • Update User Attributes
  • Deactivate Users
Click Save.
Okta Provisioning To App section with Create Users, Update User Attributes, and Deactivate Users enabled

Provisioning → To App — enable Create Users, Update User Attributes, and Deactivate Users.

3

Add custom attributes (optional)

Skip this step if you only need to sync standard user fields (name, email, groups).
Custom attributes need to be declared in the SCIM app schema before Okta can include them in provisioning payloads.Go to Directory → Profile Editor and select the Vikat SCIM app profile. Click Add Attribute.
Okta Profile Editor for the Vikat SCIM app showing the Add Attribute and Mappings buttons

Profile Editor for the Vikat SCIM app — click Add Attribute to declare a new custom field.

Configure the attribute — for example, for Employee ID:
Add Attribute dialog with Display name Employee ID, Variable name employeeID, and External name employeeID filled in

Add Attribute dialog — the External name is what Vikat receives and must match exactly what you configure in Vikat's SCIM attribute settings.

Click Save, then click Mappings on the Vikat SCIM profile.
Vikat SCIM Attribute Mappings screen with Go to Profile Editor and Force Sync buttons

Click Mappings on the Vikat SCIM profile to open the attribute mapping view.

Select the Okta User → Vikat SCIM tab.
Okta User to Vikat SCIM mapping direction tab showing attribute mapping fields

Okta User to Vikat SCIM mapping direction — map each Okta profile field to the corresponding SCIM attribute.

Scroll to find your attribute and set its source from the Okta user profile — e.g. user.employeeNumber → employeeID. Click Save Mappings.
Attribute mapping row showing user.employeeID mapped to the employeeID SCIM attribute

Mapping user.employeeID from the Okta user profile to the employeeID SCIM attribute.

Back in Vikat, go to Attribute Mapping in the provider setup and add a SCIM Attribute entry for employeeID. The External name you set in Okta must match this exactly.
Vikat Attribute Mapping step showing SCIM Attributes section with employeeID custom attribute entry

In Vikat's Attribute Mapping step, add the custom SCIM attribute using the same External name configured in Okta.

The External name in Okta’s Profile Editor and the SCIM attribute name in Vikat must match exactly — including case.

​
Step 4: Assign Users and Push Groups

1

Assign users

Go to the Assignments tab in the Vikat SCIM app.Click Assign → Assign to People or Assign to Groups and select the users or groups to sync with Vikat.
Vikat SCIM app Assignments tab with Assign dropdown showing Assign to People and Assign to Groups options

Assign users or groups from the Assignments tab — users are pushed to Vikat immediately on assignment.

Assigned users are pushed to Vikat immediately. When a user is unassigned or deactivated in Okta, Vikat deactivates them in real time.
2

Push groups (for team and BU mapping)

If you use group membership to drive Vikat team or business unit assignments, you need to push the groups themselves — not just the users in them.Go to the Push Groups tab in the Vikat SCIM app and click Push Groups.You can push groups by name (search for specific groups) or by rule (create a filter that automatically pushes any matching groups — useful if your groups follow a naming convention like Vikat-*).
Push Groups tab showing Find groups by name and Find groups by rule options

Push Groups tab — choose to find groups by name or create a rule to push all matching groups automatically.

Push Groups by rule dialog with Rule name Vikat Groups and Group name filter starting with Vikat

Push by rule — set a filter (e.g. Group name starts with 'Vikat') to automatically push all matching groups.

Once groups are pushed and showing as Active, Vikat tracks their membership in real time.
Push Groups list showing Vikat-Admin and Vikat-Viewer groups with Active push status

Pushed groups showing as Active — Vikat now tracks membership changes for these groups in real time.

In Vikat, configure Attribute-to-Team or Attribute-to-Business Unit mappings using the group displayName as the match value to automatically assign users to teams or business units based on their group membership.

​
Step 5: Verify in Vikat

Once assignments and group pushes are active, confirm everything is syncing correctly.
  • Go to Governance → Users to see provisioned users and their assigned roles
  • Go to Governance → Teams to see teams populated from pushed groups
  • Go to Governance → Business Units to see business units resolved from group or attribute mappings
Changes in Okta — new assignments, group membership updates, deactivations — will reflect in Vikat in real time.

​
How Sync Works

Real-time push — Okta pushes user and group changes to Vikat immediately when they occur. Background reconciliation — if you configured an API token in SSO using OIDC Step 4, Vikat also runs a full reconciliation every 24 hours to catch anything the SCIM push may have missed.

​
Troubleshooting

Test API Credentials fails — verify the SCIM Base URL has no trailing slash and the API token matches exactly what Vikat generated. Rotate the token in Vikat and update Okta if needed. Users are pushed but have no role — SCIM provisions the user record; role assignment comes from attribute mappings in the OIDC provider. Confirm your Attribute-to-Role mappings are set and the relevant claims are present in the JWT. Custom attribute is not arriving in Vikat — confirm the External name in Okta’s Profile Editor matches the SCIM attribute name in Vikat exactly (case-sensitive). Also verify the Okta User → Vikat SCIM mapping direction is saved. Group membership is not syncing — ensure groups are added under Push Groups, not just Assignments. Assignments sync users; Push Groups syncs group membership.