Let Oomnitza be your single source of truth!
You'll get visibility of your Okta users as data from Okta is automatically transformed into consumable information and actionable insights.
Choose from one or more of the following user loads in Oomnitza:
Okta User Load: Retrieves information about users that have the following status: ACTIVE,STAGED,PROVISIONED, PASSWORD_EXPIRED, RECOVERYand LOCKED_OUT.
When configuring the Okta User Load, you need to specify the number of days since the last sync. To retrieve all of the active user records when you run the integration for the first time, you enter 0 in the Days Since Last Sync field. When all the user records are uploaded, you can change the value so that only new or updated records are retrieved.
Let's say you ran the Okta User Load last Sunday and you scheduled the Okta User Load to run every Sunday at 6 AM. To reduce the performance workload, you enter 7 in the Days Since Last Sync field. The next time that the Okta User Load is run only the new records that were added or the user records that were updated since the last run are retrieved.
Okta Deprovisioned Load: Enables you to filter users by status. You can input any status, such as:DEPROVISIONED, SUSPENDED, ACTIVE, STAGED , PROVISIONED, RECOVERY, PASSWORD_EXPIRED or LOCKED_OUT
For information on the API used in the user loads, see User List API
Information
Before configuring any integrations with Okta, you need to add your Okta credentials to Oomnitza.
Okta supports both OAuth and API key authentication. However, Okta has announced that API key authentication will soon be deprecated. Although it is still supported currently and no deprecation timeline has been provided, we recommend switching to OAuth authentication as soon as possible.
Creating Okta OAuth credentials
Add the Okta subdomain to global settings
To save time entering information when you integrate Okta with Oomnitza and when you create the user integration and workflows, you can add the Okta subdomain value as a global variable in Oomnitza.
- Go to Configuration>General>Global Settings.
- Click Add new variable (+).
- Enter Okta.Subdomain as the key value.
- Enter the value. Refer to the table below.
- Click SAVE.
| Okta Instance URL | Subdomain |
https://MyCompanyName.okta.com |
MyCompanyName.okta |
https://MyCompanyName.oktapreview.com |
MyCompanyName.oktapreview |
Creating the user integration
- In Oomnitza, click Configuration > Integrations > Overview.
- Click Block view
.
- On the Integrations page, scroll down to the Extended section for user integrations.
- Click NEW INTEGRATION.
- In the sidebar, search for the integration.
- Click ADD.
Integration details overview
More information is provided about the following fields to help you complete the integration:
- User only. Add user records.
- User plus SaaS user. Add user and SaaS user records.
The benefit of adding SaaS user records is that you can run a workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that can be retrieved depends on whether SaaS user workflows are available for the integration.
Installation types
- Cloud. Store credentials in the Oomnitza cloud.
- Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication.
Integration preferences
- Create & Update. Add and update records.
- Create only. Add records.
- Update only. Update records.
Editing the integration details
When you edit the Integration details section, you can select the name or names of integration contacts. Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.
- Click Edit
.
- Make your changes.
Editing the credential details
If you selected Cloud as the installation type, choose one of the following options:
- Select the credentials that were created for the integration.
- Edit the credentials that were created for the integration.
- Create new credentials
Scheduling the integration
By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.
- Click Edit
.
- Make and save your changes.
Mapping fields to Oomnitza
To map the fields to Oomnitza, click Edit .
Select Edit integration to add rules for syncing data.
Filtering integration results.
You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.
Custom mappings
Map the Okta fields to Oomnitza fields and create custom mappings to get the user information you need.
Complete these actions:
- Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
- Create a custom mapping to map the Okta Id to Oomnitza.
- Click the down arrow on the Id field.
- Select Add new Oomnitza users field.
- Change the name of the field to Okta User Id.
- Select the Unique checkbox.
- Click CREATE.
- Ensure that the Email is mapped to the
- Username field on the Oomnitza side (required for integration).
- Email field on the Oomnitza side (required for integration).
- Select the Role field on the Oomnitza mapping side.
- Choose a suitable role from the list (a defined role is necessary for the integration)
- Assign a sync key to a unique field, such as the Email.
- Click UPDATE.
Activated
Created Date
Email
First Name
ID
Last Login Date
Last Name
Last Updated Date
Login
Mobile Phone
Password Changed Date
Second Email
Status
Status Changed Date
Launching the integration
Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration.
If you selected Cloud as the installation type when creating the integration, see Running an extended integration
If you selected Local as the installation type when creating the integration, see Running an extended integration locally.
Viewing data ingested by Oomnitza
Viewing ingested asset data
For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.
Viewing ingested user data
For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab.
Related Links
Unleash the power of Oomnitza
To get valuable actionable insights that help you manage your assets, learn how to:
- Configure dashboards for your users and software
- Configure custom reports about your users and software
- Create workflows to automate tasks
See Getting started for more information.
Comments
0 comments
Please sign in to leave a comment.