OKTA

Below, you find information to setup Okta with our SAML SSO app. If you need help or have questions,
you can contact us via our help desk or book a free screen share session at https://resolution.de/go/calendly.

Step-by-Step Guides

Based on your user provisioning model, pick one of the following step-by-step guides.

In most cases we recommend to use Okta with User Sync.

(3.6.x) Okta with User Sync
Setting up User synchronisation with Okta, as well as authentication via SAML
(3.6.x) Okta with Just-In-Time Provisioning
Setting up authentication via SAML with Okta and using Just-in-Time Provisioning to create/update User Accounts during login.
(3.6.x) Okta with Manual Provisioning
Setting up authentication via SAML with Okta for Users that already exist in the Atlassian product.

Some important notes:

Which Step-by-Step Guide you should pick?

Depending on your Atlassian product, you can choose from different user provisioning models.
We recommend using User Sync, since it is easy to setup and maintain.

In general, with Okta we support the following ways for user provisioning:

User Sync allows to sync users periodically from Okta, but also when they log in for the first time into your Atlassian product. See our detailed article for User Sync.
Just in Time Provisioning allows to create and update users on-the-fly when they log in. See our detailed article for JIT.
For Manual User Management, the administrator has to create and update users on Okta and your Atlassian product by hand.
We do not recommend it. See our article for Manual User Management.

Model/Function	Admin Effort	Pro's and Con's
User Sync	Low	Uses Okta API to perform regular sync Users and groups created & updated shortly after done in Okta Users in Atlassian application can be disabled as a result of a sync, saving licenses Additional attributes can be written to Jira user properties
Just in Time Provisioning	Medium	Creates & Updates users based on information in the SAML Response during Login Users are only created on their first Login. Users & Groups are updated only during SAML authentication
Manual User Management	High	Here no sync between Okta and Atlassian application happens Needs manual maintenance of two user bases (or is done via custom developments).

Model/Function

Admin Effort

Pro's and Con's

User Sync

Low

Uses Okta API to perform regular sync
Users and groups created & updated shortly after done in Okta
Users in Atlassian application can be disabled as a result of a sync, saving licenses
Additional attributes can be written to Jira user properties

Just in Time Provisioning

Medium

Creates & Updates users based on information in the SAML Response during Login
Users are only created on their first Login.
Users & Groups are updated only during SAML authentication

Manual User Management

High

Here no sync between Okta and Atlassian application happens
Needs manual maintenance of two user bases (or is done via custom developments).

OKTA

Step-by-Step Guides

Which Step-by-Step Guide you should pick?

Our Wiki uses cookies