Authentication using Okta, a cloud-based identity management service, is available in Octopus 3.16 and later.
To use Okta authentication with Octopus you will need to:
- Configure Okta to trust your Octopus Deploy instance (by setting it up as an app in Okta).
- Configure your Octopus Deploy instance to trust and use Okta as an Identity Provider.
The first steps are to configure Okta to trust your instance of Octopus Deploy by configuring an app in your Okta account.
Configure an app
Once you have an account, log in to the Okta admin portal.
After signing up to Okta you will receive your own url to access the Okta portal. For a developer account, it will look something similar to:
Select the Applications tab and click the Add Application button.
Click the Create New App button.
Choose Web for the Platform and OpenID Connect for the Sign on method and click the Create button.
Enter an Application Name like Octopus Deploy and for the Login redirect URIs enter
https://octopus.example.comwith the public url of your Octopus Server, and click the Save button.
Reply URLs are case-sensitive
Please take care when adding this URL. They are case-sensitive and can be sensitive to trailing slash characters.
Not using SSL?
We highly recommend using SSL, but we know its not always possible. You can use
http if you do not have SSL enabled on your Octopus Server. Please beware of the security implications in accepting a security token over an insecure channel.
Octopus now integrates with Let's Encrypt making it easier to setup SSL on your Octopus Server.
Under the General Settings for the app you have just created, ensure that Implicit (Hybrid) and Allow ID Token with implicit grant type are both checked, under the Allowed grant types. Click the Save button to continue.
If you want to allow users to log in directly from Okta then change the Login initiated by to Either Okta or App, set Login flow to Redirect to app to initiate login, and set the Initiate login URI to
OpenID Connect settings
There are two values you will need from the Okta configuration to complete the Octopus configuration: the Client ID and Issuer. (The Client ID is also referred to as Audience.)
First, use Okta's Classic UI by selecting it in the upper right hand menu
Now select the Sign On tab and scroll down to the OpenID Connect ID Token section. Take note of the Issuer and Audience as you will need both these values to configure your Octopus Server.
Okta group integration
If you want Okta groups to flow through to Octopus, you'll need to change the Groups claim fields as follows:
Note that the Regex is
.*, the period is important!
Active Directory integration
If you want to configure Okta to present your active directory groups, use a similar approach to Okta group integration, however we recommend that you use a Groups claim type of Expression instead of Filter.
For example, if you have all of your Octopus groups prefixed with
Octopus.Deployers, etc.) then you could use the following expression to pass along the correct AD groups:
Groups.startsWith("active_directory", "Octopus.", 10)
This expression will search
active_directory for any groups that start with the name
Octopus. and only return the first 10 results.
A complete guide to Okta's group expressions are available here
Next you will need to assign your app to people or groups within your Okta directory.
Select the Assignments tab and click the Assign button. You can assign your app to people, and to groups.
To assign the app to all users, you can simply assign the default Everyone group to the app, and click Done.
Configure Octopus Server
You will need the Client ID (aka Audience) and Issuer obtained from the Okta portal as described above.
Your Client ID should be a string value like
Your Issuer should be a URL like
Once you have those values, run the following from a command prompt in the folder where you installed Octopus Server:
Octopus.Server.exe configure --OktaIsEnabled=true --OktaIssuer=Issuer --OktaClientId=ClientID #Eg: # Octopus.Server.exe configure --OktaIsEnabled=true --OktaIssuer=https://dev-xxxxxx.oktapreview.com --OktaClientId=0a4bxxxxxxxxxxxx9yc3
Alternatively these settings can be defined through the user interface by selecting Configuration ➜ Settings ➜ Okta and populating the fields
In versions prior to Octopus 2018.3.5 the Role Claim Type and Scope had different defaults and these values will need to be updated. For new installations of Octopus 2018.3.5 and greater these values should default to the above values.
Octopus user accounts are still required
Octopus still requires a user account so you can assign those people to Octopus teams and subsequently grant permissions to Octopus resources. Octopus will automatically create a user account based on the profile information returned in the security token, which includes an Identifier, Name, and Email Address.
How Octopus matches external identities to user accounts
When the security token is returned from the external identity provider, Octopus looks for a user account with a matching Identifier. If there is no match, Octopus looks for a user account with a matching Email Address. If a user account is found, the External Identifier will be added to the user account for next time. If a user account is not found, Octopus will create one using the profile information in the security token.
Already have Octopus user accounts?
If you already have Octopus user accounts and you want to enable external authentication, simply make sure the Email Address matches in both Octopus and the external identity provider. This means your existing users will be able to sign in using an external identity provider and still belong to the same teams in Octopus.
If you are installing a clean instance of Octopus Deploy you will need to seed it with at least one admin user. This user will have access to create and configure other users as required. To add a user, execute the following command
Octopus.Server.exe admin --username USERNAME --email EMAIL
The most important part of this command is the email, as usernames are not necessarily included in the claims from the external providers. When the user logs in the matching logic must be able to align their user record based on the email from the external provider or they will not be granted permissions.
We do our best to log warnings to your Octopus Server log whenever possible. If you are having difficulty configuring Octopus to authenticate with Okta, be sure to check your server logs for warnings.
You can also check Okta logs by clicking the View Logs link on the Okta admin portal.
Double and triple check your configuration
Unfortunately security-related configuration is sensitive to everything. Make sure:
- You don't have any typos or copy-paste errors.
- Remember things are case-sensitive.
- Remember to remove or add slash characters - they matter too!
Check OpenID Connect metadata is working
You can see the OpenID Connect metadata by going to the Issuer address in your browser adding
/.well-known/openid-configuration to the end. In our example this would have been something like
Inspect the contents of the security token
Perhaps the contents of the security token sent back by Okta aren't exactly the way Octopus expected, especially certain claims which may be missing or named differently. This will usually result in the Okta user incorrectly mapping to a different Octopus User than expected. The best way to diagnose this is to inspect the JSON Web Token (JWT) which is sent from Okta to Octopus via your browser. To inspect the contents of your security token:
Open the Developer Tools of your browser and enable Network logging making sure the network logging is preserved across requests.
In Chrome Dev Tools this is called "Preserve Log".
Attempt to sign into Octopus using Okta and find the HTTP POST coming back to your Octopus instance from Okta on a route like
/api/users/authenticatedToken/Okta. You should see an
id_tokenfield in the HTTP POST body.
Grab the contents of the
id_tokenfield and paste that into https://jwt.io/ which will decode the token for you.
Don't worry if jwt.io complains about the token signature, it doesn't support RS256 which is used by Okta.
- Octopus uses most of the data to validate the token, but primarily uses the
nameclaims. If these claims are not present you will likely see unexpected behavior.
- If you are not able to figure out what is going wrong, please send a copy of the decoded payload to our support team and let them know what behavior you are experiencing.
Need support? We're here to help.