New Landing Page for PingOne

Below, you find information to setup PingOne and our apps. If you 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 PingOne with Just-In-Time Provisioning.

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 does not support to transmit groups via SAML attributes. Hence, groups must be managed locally in your Atlassian product.
Step-By-Step Guide for PingOne with Manual Provisioning
Setting up authentication via SAML with PingOne for Users that already exist in the Atlassian product.

Which Step-by-Step Guide you should pick?

Depending on your Atlassian product, you can choose from different user provisioning models.

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

Just in Time Provisioning allows to create and update users on-the-fly when they log in. It is not possible to send groups via SAML for PingOne. Thus, groups must be managed locally. See our detailed article for (6.15.x) 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 PingOne and your Atlassian product by hand. We do not recommend it. See our article for (6.15.x) Manuel User Management.

Model/Function	Admin Effort	Pro's and Con's
Just in Time Provisioning	Medium, need to manage groups locally on your product instance	Creates & Updates users based on information in the SAML Response during Login PingOne does NOT support transmitting groups. Users are only created on their first Login. Users & Groups are updated only during SAML authentication. Users cannot be marked disabled (as PingOne will not complete the Authentication for a deleted/disabled User)

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

Model/Function

Admin Effort

Pro's and Con's

Just in Time Provisioning

Medium,

need to manage groups locally on your product instance

Creates & Updates users based on information in the SAML Response during Login
PingOne does NOT support transmitting groups.
Users are only created on their first Login.
Users & Groups are updated only during SAML authentication.
Users cannot be marked disabled (as PingOne will not complete the Authentication for a deleted/disabled User)

Manual User Management

High

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