Below, you find information to set up PingOne 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

Step-by-Step Guides

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

  • PingOne with Just-in-Time Provisioning
    Setting up authentication via SAML with PingOne and using Just-in-Time Provisioning to create/update User Accounts during login.

  • PingOne with Manual Provisioning
    Setting up authentication via SAML with PingOne for Users that already exist in the Atlassian product.
  • 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.

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

  1. Just in Time Provisioning allows creating and updating users on the fly when they log in. See our detailed article for JIT.
  2. LDAP synchronization from Active Directory. Your instance is still synchronized to your Active Directory via LDAP, you can continue to do so. Please follow the "Manual User Management" Guide in this scenario.
  3. For Manual User Management, the administrator has to create and update users on PingOne and your Atlassian Data Center or Server product by hand.
    We do not recommend it. See our article for Manual User Management.


Admin Effort

Pros and Cons

Just-in-Time Provisioning


  • 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 ManagementHigh 

  • Here no sync happens
  • Needs manual maintenance of 2 User bases (or is done via custom developments).