Set up an Okta AWS Federation connector

ConductorOne provides identity governance and just-in-time provisioning for Okta for AWS federation. Integrate your Okta instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

This connector integrates with Okta for AWS federation through Okta groups. It’s useful for organizations that use the SAML to AWS app config in Okta, wherein Okta mints a SAML cert with correct group memberships to drive IAM roles for the federated user.

Capabilities

Resource	Sync	Provision
Accounts
Groups assigned to the AWS app
Application assignments for the AWS app

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:

ConductorOne capability	Custom read-only token	Read-only + app admin + group admin token	Super admin token
Review group membership
Provision group membership
Review application assignment
Provision application assignment
Review admin roles

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.

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

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

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

   
8. 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 AWS Federation 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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Okta AWS Federation and click Add.

3. Choose how to set up the new Okta AWS Federation connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter your Okta domain (the URL of your Okta instance is <YOUR DOMAIN>.okta.com) into the Okta domain field.

8. Paste your API token into the API token field.

9. Enter your AWS Okta app ID in the AWS Okta app ID field.

10. Optional. If desired, click the checkbox to Allow group to direct assignment conversion for provisioning.

    When this setting is enabled, when AWS roles are requested directly and the user is assigned to the AWS app in Okta via group membership, ConductorOne will convert the user assignment to a direct assignment.

11. Click Save.

12. Finally, set an Okta connector as the source of identities for this connector. This significantly improves the connector’s performance. In the Shared identity source area of the page, click Edit.

13. Select the Okta connector from which you want to pull identities.

14. Click Save.

15. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Okta AWS Federation connector is now pulling access data into ConductorOne.

Self-hosted

Follow these instructions to use a connector, hosted and run in your own environment.

Self-hosted connector not currently available.