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

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Okta credentials

Each setup method 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, Read Only 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 service account for the API token

A user with the Read Only Admin or Super Admin role in Okta must perform this task.

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 store it securely in a vault.

   

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: Read Only Admin, 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 Read Only Administrator, Super Administrator, 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 instructions for your chosen setup method.

Set up an Okta AWS Federation cloud-hosted 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

1. In ConductorOne, click Connectors > 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. Optional. If desired, click the checkbox to Sync custom roles.

10. Optional. If desired, click the checkbox to Skip secondary emails when syncing user information.

11. Click Save.

12. 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.