Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
AWS
Below, you find information to setup SSO for AWS 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.
- AWS with Just-In-Time Provisioning
Setting up authentication via SAML with AWS and using Jut-in-Time provisioning to create/update user accounts during login.
AWS does not support transmitting groups via SAML attributes. Hence, groups must be managed locally in your Atlassian product.
- AWS with Manual Provisioning
Setting up authentication via SAML with AWS 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 AWS 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 AWS. Thus, groups must be managed locally. See our detailed article for JIT.
- LDAP synchronisation from Active Directory. If 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 AWS 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 |
---|---|---|
Just in Time Provisioning | Medium, need to manage groups locally on your product instance |
|
Manual User Management | High |
|