Below, you find information to setup OneLogin and our SAML SSO apps for Atlassian Data Center and Server products. If you need our need help or have questions, you can contact us via our helpdesk 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 OneLogin with User Sync.

OneLogin with User Sync
Setting up User synchronization with OneLogin, as well as authentication via SAML
OneLogin with Just-in-Time Provisioning
Setting up authentication via SAML with OneLogin and using Just-in-Time Provisioning to create/update User Accounts during login.
OneLogin with Manual Provisioning
Setting up authentication via SAML with OneLogin for Users that already exist in the Atlassian product.

Some important notes:

User Sync functionality is currently only available for Jira, Confluence & Bitbucket Server and Data Center

Fisheye only supports Manual User Management.

Which Step-by-Step Guide should you pick?

Depending on your Atlassian Data Center or Server 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 OneLogin we support the following ways for user provisioning:

User Sync allows to sync users periodically from OneLogin, 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 creating and update users on-the-fly when they log in. See our detailed article for JIT.
LDAP synchronisation from Active Directory. Is you instance still synchronised to your Active Directory via LDAP, you can continue to do so. Please follow the "Manual User Management" Guide in this scenario.
For Manual User Management, the administrator has to create and update users on OneLogin and your Atlassian Data Center or Server 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 OneLogin API to perform regular sync
Users and Groups created & updated shortly after done in OneLogin
Users can be disabled
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 happens
Needs manual maintenance of 2 User bases (or is done via custom developments).

Step-by-Step Guides

Which Step-by-Step Guide should you pick?

SAML Single Sign-On is available for Atlassian Server & Atlassian Data Center products. Our Jira Data Center, Confluence Data Center, Bitbucket Data Center, Jira Server, Confluence Server, Bitbucket Server and other apps are all available on the Atlassian Marketplace.

SAML Single Sign-On is available for Atlassian Server & Atlassian Data Center products.

Our Jira Data Center, Confluence Data Center, Bitbucket Data Center, Jira Server, Confluence Server, Bitbucket Server and other apps are all available on the Atlassian Marketplace.