This is an updated and improved version of the Okta connector! If you’re setting up Okta with ConductorOne for the first time, you’re in the right place.

Capabilities

Syncing standard and custom admin roles requires a super admin token.

Gather Okta credentials

Configuring the connector requires you to pass in credentials generated in Okta. Gather these credentials before you move on.

API token permissions and ConductorOne capabilities

ConductorOne’s capabilities depend on the permissions of the API token used to set up the connector:

Instead of generating a new API token, you can use an existing API token generated with Super Admin or a combination of Read Only/App Admin/Group Admin privileges. To learn more about Okta roles, visit https://help.okta.com/en/prod/Content/Topics/Security/administrators-admin-comparison.htm

(Optional) Create a custom read-only admin role

To give the ConductorOne integration limited read-only admin permissions, you’ll need to create a custom Okta admin role and resource set and assign them to the admin you’ll use to generate the API key.

1. In Okta, log in to the Admin Dashboards and navigate to Security > Administrators > Roles.

2. Click Create new role.

3. Give the new role a name and description, such as “ConductorOne integration read-only admin”.

4. Give the role the View roles, resources, and admin assignments permission (this is found in the Identity and access management permissions section).

5. Click Save role.

6. Next, navigate to Security > Administrators > Resources.

7. Click Create new resource set.

8. Give the new resource set a name and description, such as “Read-only admin for C1 integration”.

9. Click Add resources.

10. Find the Identity and access management resource type and select View roles, resources, and admin assignments.

11. Click Save selection, then click Create. The resource set is now shown on the Resources tab.

12. Now we’ll assign the resource set to an admin. (If you need to do so, make a service account following the instructions below, then return to finish this process.) Click Edit on the new resource set and select View or edit assignments.

13. In the Complete the assignment section of the page, select the role and resource set you just created.

14. Click Save changes.

Now you can skip ahead to the instructions to create an API token.

(Optional) Create a service account for the API token

If desired, you can create a service account user in Okta that has the permissions for the API token.

1. Navigate to Directory > People and click Add person.

   

2. Enter the necessary user details to create a user. You might want to use identifiers that make it easily recognizable as a service account, such as First Name: ReadOnly, Last Name: ServiceUser.

3. Set the Password for the account and carefully save it somewhere secure.

4. Click Save.

   At this point, if you’ve created a custom read-only role, stop here and return to the instructions above. If you’re using a standard Okta admin role, continue on.

4. Navigate to Security > Administrator and click Add administrator.

5. Enter the email address for your newly created Service Account to select the user.

6. Select the administrator roles to grant: Super Administrator or a combination of Read Only + Application Admin + Group Admin.

   

7. Click Add Administrator.

Create an API token

When creating an API token, Okta assigns the permissions of the currently logged-in user to the token. If, for example, you wish to use a Read Only Admin-scoped API token, you must log in to Okta as a user with the Read Only Admin role assigned.

1. Log into Okta with the account you’ll use to generate the API token. The account must have Super Administrator, the custom read-only role you created above, or a combination of Read Only/App Admin/Group Admin privileges. The permissions on the API token affects what features and functionality are available from ConductorOne. Before you begin, review the chart in API permissions and ConductorOne capabilities to make sure you’re creating a token with the right permissions for your needs.

2. In the Okta console, navigate to Security > API and click Tokens.

   

3. Click Create Token.

4. Give your token a name, such as ConductorOne, and click Create Token.

5. Copy and save the new API token.

That’s it! Next, move on to the connector configuration instructions.

Configure the Okta connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Okta credentials generated by following the instructions above

# baton-okta-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-okta-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Okta credentials
  BATON_API_TOKEN: <Okta API token>
  BATON_DOMAIN: <Your Okta domain>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

# baton-okta.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-okta
  labels:
    app: baton-okta
spec:
  selector:
    matchLabels:
      app: baton-okta
  template:
    metadata:
      labels:
        app: baton-okta
        baton: true
        baton-app: okta
    spec:
      containers:
      - name: baton-okta
        image: ghcr.io/conductorone/baton-okta:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-okta-secrets

What’s next?

If Okta is your company’s identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the Create applications page for important information about how to set up connectors for the SCIMed apps.