Configuration

1. Choose a Schema: Select the API Key schema to retrieve Okta assets using an API key

2. Configure plugin: Configure the plugin with the required fields.

   Field	Description	Example
   URL*	The URL used to access the source	https://acme.okta.com
   Skip TLS Certification Validation	Skip certificates validation when using a certificate that is self-signed or unable to be validated through a proper certificate authority	N/A
   API Key*	The API key used to identify the authorization and permissions	ABCDEF0123456789

3. Configure Name: OPTIONAL: You can give the configuration a name to provide an identifiable attribute of the configuration to delineate other similar configurations.

4. Activate Config: To enable this configuration and begin pulling data select "Activate". If you wish to save the configuration to come back later to finish, select "Save Draft". This will save the configuration, but keep it disabled until Activated.

Source Documentation

General

How to find your Okta URL (Please ensure '-admin' is NOT included in your domain)

Creating Credentials

You'll be asked to provide source credentials that Sevco will use to connect to Okta Users. Use instructions provided here: https://developer.okta.com/docs/guides/create-an-api-token/main/

Required Permissions

To ensure the user that created the API token for Sevco to use has the appropriate permissions, follow the instructions in Okta Security - Administrators.
Set the following permissions:

• Permissions: View users' and their details

The following default role contains the required permissions

• Role: Read-only Administrator

API Documentation

https://developer.okta.com/docs/reference/core-okta-api/