Skip to content

Okta

This article includes information on adding Okta as an integration to sync objects to Oblique. To use Okta as an identity provider to authenticate to Oblique, see Single sign-on.

When you connect an Okta org to Oblique, Oblique will automatically sync the org, its users and their profile attributes, its groups, and its apps and their assignments.

As you add or remove users, groups, or app assignments in Okta, these changes are automatically synced to Oblique. If connected in read-write mode, Oblique can also change Okta group membership. Oblique doesn’t change Okta app assignments.

You can add multiple Okta orgs to Oblique. Each is a separate integration, identified by its domain base URI.

Oblique syncs the following from your Okta org. In read-write mode, Oblique can also change Okta group membership.

Okta object Oblique object Capability
Users Users Read-only
Profile attributes User attributes Read-only
Users Accounts Read-only
Organization Resources Read-only
Groups Resources Read-only
Apps Resources Read-only
Organization membership Entitlements Read-only
Group membership Entitlements Read-write
App assignments for users Entitlements Read-only
App assignments for groups Entitlements Read-only

Oblique syncs each user in your Okta org as an Oblique user.

Oblique uses the following profile attributes from Okta to identify users:

  • id
  • firstName
  • lastName
  • email
  • secondEmail

A user who is deactivated in Okta is soft deleted in Oblique. They’re restored if they’re reactivated in Okta.

Users with every other Okta status are synced as active Oblique users. This includes users who are suspended, users who are staged or pending activation and haven’t activated their account yet, and users who are locked out or whose password has expired or is being reset.

Oblique syncs the following profile attributes from Okta as user attributes:

  • employeeNumber
  • userType
  • manager
  • managerId
  • title
  • department
  • division
  • organization
  • costCenter
  • primaryPhone
  • city

Oblique also syncs custom profile attributes with the data type string. Custom profile attributes are attributes defined by your organization in Okta that aren’t part of the default Okta user profile.

Oblique also syncs each user in your Okta org as an Oblique account. Users who are deactivated aren’t synced as accounts. They’re added back if their user is reactivated in Okta. Users with any other status, including suspended users, are synced as accounts.

Oblique automatically matches Okta accounts to users in Oblique. Okta accounts are matched to Oblique users by their ID (id). Oblique syncs every Okta user as an Oblique user, so it matches every Okta account.

Oblique syncs the following from Okta as resources:

  • The Okta org you connected
  • Each group in the org
  • Each app in the org

Every account has an entitlement for the org.

Oblique also syncs active group rules and group push mappings for apps. In Oblique, each group detail page includes additional detail on Okta, like which group rules populate the group, and which apps the group is pushed to.

A group deleted in Okta is soft deleted in Oblique.

The Okta integration doesn’t read information about roles in Okta.

In Okta, where an app is assigned to a group, Oblique represents this as the group having an entitlement to the app. In Oblique, you can see the access that members of the group have through the app.

You must be a Super Administrator in Okta to connect this integration.

If you don’t have sufficient permissions, create an install link so someone who does can connect the integration without being an Oblique admin.

The Okta integration connects using an API Service Integration, with the following scopes for your Okta org:

Okta scope What Oblique uses it for Needed for read-only Needed for read-write
okta.orgs.read Identify the org the connection belongs to Yes Yes
okta.users.read Read users and their profile attributes Yes Yes
okta.groups.read Read groups, their members, and group rules Yes Yes
okta.apps.read Read apps, their assignments, and their group push mappings Yes Yes
okta.groups.manage Add and remove group members Yes
You must be an admin to add an integration.

You connect an Okta org to Oblique by installing the Oblique app from the Okta Integration Network, then adding the client credentials Okta issues to Oblique.

To install the Oblique app, in the Okta Admin Console, navigate to Applications > API Services Integrations:

  1. Select Add Integration.
  2. Search for and select Oblique. Select Next.
  3. Review the requested Okta scopes. Select Install & Authorize.
  4. Copy the client secret that is provided. It won’t be shown again. Store this securely. You will need to provide this to Oblique. Select Done.
  5. Under Client Credentials, also copy the Okta Domain and Client ID.

Then, to add an Okta integration, navigate to the Integrations page:

  1. Select Add integration.
  2. Select Okta.
  3. Enter your Okta domain as the Domain base URI, such as https://example.okta.com. Enter your Client ID and your Client secret from the installation.
  4. Under Connect, select Read-write to let Oblique manage Okta group membership, or Read-only to let Oblique read but not manage it. By default, this is read-write.
  5. Select Add integration.

Oblique will immediately start syncing the Okta org’s users, groups, and apps.

Change Okta integration’s authorizations

Section titled “Change Okta integration’s authorizations”
You must be an admin to replace an integration’s credentials.

If the client credentials are revoked or need rotating, you can replace them without removing the integration. From the integration’s detail page:

  1. Navigate to the Settings tab.
  2. Under Connection, select Replace OAuth client credentials….
  3. Paste the new Client ID and Client secret, then select Replace OAuth client credentials.

You can only replace the credentials with ones for the same Okta org. To change the org, instead delete the integration and add another one.

You can’t change an integration between read-only and read-write. Instead, remove the integration and add it again.

In read-write mode, the Okta integration lets Oblique manage access in your Okta org. Oblique does this by updating Okta group membership. An entitlement for an Oblique group or team to an Okta group is flattened and written in Okta as an individual entitlement for each member’s account.

Oblique can add an account to a group, and remove it from the group.

Oblique can’t create Okta groups, or assign users or groups to Okta apps. To give access to an Okta app through Oblique, assign the app to an Okta group in Okta, and grant access to that group in Oblique.

You must be an admin to remove an integration.

To remove an Okta integration, from the integration’s detail page:

  1. Navigate to the Settings tab.
  2. At the bottom of the page, under Delete integration, select Delete integration….
  3. In the confirmation dialog, type the text to confirm, then select Delete integration.

This will immediately stop all syncing and remove all resources from the integration. Access that Oblique granted in Okta stays as it is.

Adding the integration reports that the domain is already in use

Section titled “Adding the integration reports that the domain is already in use”

Each Okta org can only be connected to an Oblique tenant once. Check the Integrations page for an existing integration with the same domain base URI.

Verify if you connected Oblique to Okta as a read-only integration. From the integration’s detail page, navigate to the Settings tab, and look under Connection, then Permissions.

To start writing access changes, remove the integration and add it again as a read-write integration.

If a problem isn’t covered here, contact support.