Oomnitza's Okta Connector allows organizations to pull user information from Okta and populate it in Oomnitza. More info in Okta can be found here: https://www.okta.com/.
Standard Mappings
The following fields can be mapped from Okta using Oomnitza's User Interface:
- First name
- Last name
- Login
- Mobile phone
Custom Mappings
Additionally, fields from the “Profile” and “Status” sections can be added through the config file. These include custom attributes, and the user’s status, such as Active, Staged, or Deprovisioned.
Setup
Details on setting up the Oomnitza Connector can be found in Oomnitza's Articles on Connector Setup.
The key information required from Okta includes:
- URL - The URL of your Okta Instance. For example: https://oomnitza-admin.okta.com
- API Token - A read-only Okta API Token. Instructions on generating an API token in Okta can be found here.
The full config file should also contain the following fields:
- Enable - When True, turns the Okta connector on. When False turns the Okta connector off.
- Default_role - The default Role ID for newly created users. By default, 25 will create users with the Employee role.
- Default_position - The default Position for newly created users. Defaults to Employee.
- Deprovisioned - When True will pull Deprovisioned users from Okta to Oomnitza. Required for pulling Status information from Okta to Oomnitza.
Example Okta Config
The below example includes a custom field mapping to bring Status. More details on creating custom field mappings can be found here.
[okta]
enable = True
url = https://example-admin.okta.com
api_token = YOUR Okta API TOKEN
default_role = 25
default_position = Employee
deprovisioned = True
mapping.E622E72FC31F4946A77C95828FD1DBC3 = {"source": "status"}
0 Comments