Configuring Provisioning for Oak Engage

Prerequisites

In order to follow this guide, you must have an administrator account within your Oak site, and be able to manage applications within Okta.

Supported features

For more information on the listed features, visit the Okta Glossary.

Configuration steps

Note

Oak Engage requires the office attribute to be set, but Okta does not have a natural field and therefore there is no default mapping.

Ensure that you review, and if required, customise the example expression for setting a default office. The example presumes that you have added a new custom field to your Okta profile called officeName, but it can be any property that logically contains a user's physical location by name.

(user.officeName != null && user.officeName != '') ? user.officeName : 'Default Office'

Review the remaining field mappings to ensure that they make sense for your Okta profiles.

Troubleshoot

If you receive any errors during SCIM provisioning or need any assistance with configuration, contact your Oak Engage account manager, or our support team who will be happy to help.