SAML Single Sign On Setup Guides for SAML SSO Current: OpenAM OpenAM Below, you find information to setup OpenAM 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 GuidesBased on your user provisioning model, pick one of the following step-by-step guides.In most cases we recommend to use OpenAM with Just-In-Time ProvisioningOpenAM with Just-In-Time ProvisioningSetting up authentication via SAML with OpenAM and using Just-in-Time Provisioning to create/update User Accounts during login. OpenAM does not support to transmit groups via SAML attributes. Hence, groups must be managed locally in your Atlassian product.OpenAM with Manual ProvisioningSetting up authentication via SAML with OpenAM 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 OpenAM 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 OpenAM. Thus, groups must be managed locally. 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 has to create and update users on OpenAM and your Atlassian product by hand. We do not recommend it. See our article for Manuel User Management.Model/FunctionAdmin EffortPro's and Con'sJust in Time ProvisioningMedium,need to manage groups locally on your product instanceCreates & Updates users based on information in the SAML Response during LoginOpenAM does NOT support transmitting groups.Users are only created on their first Login.Users are updated only during SAML authentication.Users cannot be marked disabled (as OpenAM will not complete the Authentication for a deleted/disabled User)Manual User ManagementHigh Here no sync happensNeeds manual maintenance of 2 User bases (or is done via custom developments). You might also find following documentation helpful: Frequently Asked Questions OpenAM with Just-In-Time Provisioning OpenAM with Manual Provisioning Further Configuration OpenAM with Just-In-Time Provisioning OpenAM with Manual Provisioning Troubleshooting OpenAM with Just-In-Time Provisioning OpenAM with Manual Provisioning 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.