Skip to main content
Version: 0.15


Okta setup

Creating Access Token

To set up Okta to sync users and groups with Common Fate we will need to create an access token to communicate with Okta's API.

Sign in to your Okta organization as a user with administrator privileges.


API tokens have the same permissions as the user who creates them, and if the user permissions change, the API token permissions also change.

See the section above on Privilege level, regarding the use of a service account when creating an API token, to specifically control the privilege level associated with the token.

In the Admin Console, select API from the Security menu and then select the Tokens tab from within the API page.

Click Create Token.

Name your token and click Create Token.

A pop up will appear showing your access token, leave this open and continue with the configuration setup below.

Running Gdeploy Commands

This is where we can start up the gdeploy identity sso enable command. Run the following to begin the SSO setup:

> gdeploy identity sso enable

You will be prompted to select you identity provider, select Okta.

? The SSO provider to deploy with  [Use arrows to move, type to filter]
> Okta
  1. For the API Token, copy and paste the token value from the previous steps.
? API Token: ****
  1. For the Okta Org URL set the value to the your okta domain e.g.
? Okta Org URL:

You should see an output similar to the below.

[✔] SSM Parameters set successfully
[i] The following parameters are required to set up a SAML app in your identity provider
| Audience URI | urn:amazon:cognito:sp:us-west-2_abcdefghi |

Next you will need to set up a SAML app, you will see the below prompt, Okta supports both a URL and XML so choose what suits you.

? Would you like to use a metadata URL, an XML string, or load XML from a file?  [Use arrows to move, type to filter]

You will see something like this, follow the next section to get the XML Metadata required for this step.

? Metadata URL

Setting up SAML SSO

To get started navigate to the Applications tab of the admin console in okta.

Click create a new App Integration in Okta, then select the SAML 2.0 option. Give your integration a name, and upload an app logo. Once done click next.

On the Configure SAML page you will need some of the outputs from the previous step in the CLI workflow.

Look back in your terminal for an output that looks like the below.

[i] The following parameters are required to set up a SAML app in your identity provider
| Audience URI | urn:amazon:cognito:sp:us-west-2_abcdefghi |

On the Configure SAML page

  • For the Single sign on URL copy the SAML SSO URL (ACS URL) from the output.
  • For the Audience URI copy the Audience URI from the output.

Configuring SAML Attributes

Under Attribute Statements add a statement with the following information.

  • For Name, enter:
  • For Value, enter:

Click Next and then Finish on the Feedback page to create the application.


You'll need to assign yourself to the application so that you can test the SAML SSO connection.

Follow these steps to assign a user to the application:

On the Assignments tab for your Okta app, for Assign, choose Assign to People.

Choose Assign next to the user that you want to assign.Note: If this is a new account, the only option available is to choose yourself (the admin) as the user.

(Optional) For User Name, enter a user name, or leave it as the user's email address, if you want.

Choose Save and Go Back, followed by Done.

Next navigate to the Sign On tab for your Okta app.

Find the SAML Signing Certificates section where you should see a list of signing certificates. Find the most recent active certificate and click the Actions drop down in the right hand column.

From the drop down click View IdP metadata, you will be redirected to your metadata, copy the URL address of the redirected site. It should look like this, alternatively, you can copy or download the XML depending on what option you chose in the CLI:

Copy the URL. eg. and paste it into the CLI prompt.

? Metadata URL:

Creating Common Fate Administrator Group

Finally you will need to create an administrator group with granted. You will be asked for The ID of the Granted Administrators group in your identity provider:

  • By default granted will set this to granted_administrators, press enter to continue this or enter a admin group name of your choice. We will use the name of this newly created group at the next step.

You should see the following prompts

[i] Updating your deployment config
[✔] Successfully completed SSO configuration
[!] Your changes won't be applied until you redeploy. Run 'gdeploy update' to apply the changes to your CloudFormation deployment.

Users and will be synced every 5 minutes from your identity provider. To finish enabling SSO, follow these steps:
1) Run 'gdeploy update' to apply the changes to your CloudFormation deployment.
2) Run 'gdeploy identity sync' to trigger an immediate sync of your user directory.

Once you have set your administrators group name, we will need to create that corresponding group in Okta In the Okta admin portal, to Directory>Groups

Click the Add Group button

  • Name the group the same name as you set in the gdeploy config setup.

Add yourself and any others you want to make granted admins to the group in Okta.

You will need to redeploy using gdeploy update to update the identity provider changes.


Amazon Cognito has a limitation where IDP-initiated SAML flows don’t work.

In the meantime, there is a workaround available to get a shortcut to Common Fate on team members’ Okta dashboards.

  1. Enable the “Do not display application icon to users” setting in the Common Fate SAML application.

  1. Create a Bookmark App following Okta’s guide here. The URL it points to should be your Granted deployment URL.

  1. Assign the Bookmark App to the same groups that the Common Fate SAML app is assigned to.

Note that you can also add an icon to the Bookmark App so the app is more distinguishable to users.