Supported integrations
Integrations connect Oblique with external systems in your organization. Oblique can both pull information from and push access decisions back to integrations.
Supported integrations
Section titled “Supported integrations”Oblique supports the following integrations and objects:
| Integration | Objects | Pull | Push |
|---|---|---|---|
| Okta | Users | ✅ Supported | ❌ Unsupported |
| User attributes | ✅ Supported | ❌ Unsupported | |
| Okta groups | ✅ Supported | ✅ Supported | |
| Okta apps | ✅ Supported | ❌ Unsupported | |
| Okta app assignments (individual) | ✅ Supported | ✅ Supported | |
| Okta app assignments (group) | ✅ Supported | ❌ Unsupported | |
| Users | ✅ Supported | ❌ Unsupported | |
| Google groups | ✅ Supported | ✅ Supported |
Supported attributes
Section titled “Supported attributes”Attributes help match users from different systems, identify users on their profiles, and create attribute-based groups.
Oblique currently supports the following user attributes:
| Attribute | Required | Supported sources | Can be used for attribute-based groups |
|---|---|---|---|
| First name | Yes | Okta (firstName), Google | No |
| Last name | Yes | Okta (lastName), Google | No |
| Yes | Okta (email), Google | No | |
| Secondary email | No | Okta (secondEmail) | No |
| UUID | Yes | Okta (id) | No |
| Manager | No | Okta (managerId) | No |
| Title | No | Okta (title) | Yes |
| Department | No | Okta (department) | Yes |
| Division | No | Okta (division) | Yes |
| User type | No | Okta (userType) | Yes |
| Cost center | No | Okta (costCenter) | Yes |
Custom Okta user attributes
Section titled “Custom Okta user attributes”Custom user attributes are attributes defined by your organization in Okta ↗ that are not part of the default Okta user profile attributes.
For an Okta integration, Oblique automatically detects, imports and syncs custom user attributes from Okta that have the data type string. Oblique does not currently support custom user attributes with other data types.
These custom user attributes are included on a user’s profile and can be used for creating attribute-based groups.
Attribute matching
Section titled “Attribute matching”Oblique uses attributes to uniquely match users imported from different systems.
Both email addresses and user IDs are used to match users:
- When a match is found with new email addresses, those emails are added as secondary emails to the existing user profile.
- If a user ID matches but emails differ, Oblique treats them as the same user and adds the new emails.
- If neither emails nor ID match any existing user, Oblique creates a new user profile.
Canonical attributes
Section titled “Canonical attributes”User profiles show information about all user attributes. Certain attributes are used are displayed as part of the user profile, including name, email, manager, and title.
Oblique currently supports the following canonical attributes and source integrations:
| Canonical attribute | Supported sources |
|---|---|
| Title | Okta (title) |
| Manager | Okta (managerId or manager) |
By default, Oblique uses the first integration you connect that provides each canonical attribute. The source integration for a canonical attribute can be changed.
Manager
Section titled “Manager”Oblique syncs both the managerId and manager user attributes from Okta. If the managerId is an Okta userId, it will be used as the canonical attribute for manager. Otherwise, if the manager attribute is an email, it is used instead.
Attribute-based groups
Section titled “Attribute-based groups”Attributes can be used to create attribute-based groups. This helps create groups of users that share a common attribute, such as all users in the same department.
Sync frequency
Section titled “Sync frequency”Oblique automatically syncs changes to integrations. The frequency depends on the integration.
Oblique lets you manage who has access to resources in integrations by pushing effective access from Oblique entitlements and groups to those resources. You can decide at the resource level whether to allow Oblique to manage access and act as the source of truth.
| Integration | Objects | Pull frequency | Push frequency |
|---|---|---|---|
| Okta | Users | Every 15 seconds | n/a |
| User attributes | Every 15 seconds | n/a | |
| Okta groups | Every 15 seconds | Every 15 seconds | |
| Okta apps | Every 15 seconds | n/a | |
| Okta app assignments (individual) | Every 10 minutes | Every 15 seconds | |
| Okta app assignments (group) | Every 10 minutes | n/a | |
| Users | Every 15 seconds | n/a | |
| User attributes | Every 15 seconds | n/a | |
| Google groups | Every 15 seconds | Every 15 seconds |