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.
3.1.x release notes
What's new
Several enhancements for User Sync for Jira and Confluence with built-in connectors for Azure AD, Okta and G Suite
Added a Disable Inactive Users connector to UserSync
Added several Identity Providers to the SAML SSO wizard
Upgrade consideration
We introduced the new JSON configuration version 7. Automated scripts using the undocumented PUT /config REST API might have to be modified:
- There is now an enum field for "User Update Method" in the IdP configurations. The options are NONE, SAML, CONNECTOR, CONNECTORANDSAML. See the front-end for a description of this option.
Important! There was a problem with the config migration of group / organization transformation options in 3.1.0-3.1.2.
- If you're using group transformations, Jira Service Desk organization transformations and / or the "Skip untransformed groups / organizations" options AND
- you've upgraded your SAML SSO app to 3.1.0 or 3.1.1 or 3.1.2
then you should upgrade to version 3.1.3 or higher immediately.
If you've saved your config via the web interface after upgrading then the aforementioned settings might have been lost. In that case, please contact our support at https://wiki.resolution.de/go/support They will guide you through restoring your configuration. We will create a written guide on how to restore it yourself soon.
Data Center
This version is fully compatible with Jira and Confluence Data Center. It will also be available for Bitbucket Data Center soon. Until then Bitbucket customers should stay on the 2.4.x versions, which are still maintained and compatible with Data Center.
Changelog
3.1.7
Released on 23 May 2019 for Jira and Confluence (Server and Data Center)
- Includes UserSync 1.1.6, see UserSync 1.1.x release notes
- Added support for OpenAM.
- Added support for NameID format X509SubjectName.
- Fixed Single Logout for Azure AD.
- Fixed combining of attributes when using email as authentication attribute.
Changes specific to Jira
- Fixed several Single Logout problems for Service Desk customers.
- Fixed a problem with Non-SSO URLs for Service Desk.
Changes specific to Confluence
- None
3.1.6
Released on 7 April 2019 for Jira and Confluence (Server and Data Center)
- Includes UserSync 1.1.4, see UserSync 1.1.x release notes
- Single Logout is now considered as stable and no longer experimental.
- Added option to define the AuthenticationContext in the SAML request.
- Set caching headers to fix problems in environments with reverse proxies.
- Improved logging and validation.
3.1.5
Released on 7 March 2019 for Jira and Confluence (Server and Data Center)
- Includes UserSync 1.1.2, see UserSync 1.1.x release notes
- Fixes group assigment for users in read only LDAP directories with local groups when using Just In Time Provisioning.
3.1.4
Released on 1 March 2019 for Jira and Confluence (Server and Data Center)
- Fixes a NullPointerException during Single Sign On when using Just In Time Provisioning together with using email as authentication attribute.
- Fixes double quotation of regular expression of Non-SSO URLs during migration from version <=3.0.x.
3.1.3
Important! There was a problem with the config migration of group / organization transformation options in 3.1.0-3.1.2.
- If you're using group transformations, Jira Service Desk organization transformations and / or the "Skip untransformed groups / organizations" options AND
- you've upgraded your SAML SSO app to 3.1.0 or 3.1.1 or 3.1.2
then you should upgrade to version 3.1.3 or higher immediately.
If you've saved your config via the web interface after upgrading then the aforementioned settings might have been lost. In that case, please contact our support at https://wiki.resolution.de/go/support They will guide you through restoring your configuration. We will create a written guide on how to restore it yourself soon.
Released on 22 February 2019 for Jira and Confluence (Server and Data Center)
- Fixes an issue preventing users from logging in if E-Mail is the authentication attribute and SAML user update is enabled.
- Fixes a migration issue for group transformations, Jira Service Desk organization transformations and the "Skip untransformed groups / organizations" options.
3.1.2
Released on 20 February 2019 for Jira and Confluence (Server and Data Center)
- Fixes an issue preventing users in directories with unset external IDs from logging in for certain configurations ("User with username some-username is null but should not")
3.1.1
Released on 13 February 2019 for Jira and Confluence (Server and Data Center)
- Fixes an issue with migrations from older app versions
3.1.0
Released on 12 February 2019 for Jira and Confluence (Server and Data Center)
- Includes UserSync 1.1.0, see UserSync 1.1.x release notes
- Fixed a cross-site scripting vulnerability on the logged out page: 2019-02-12 XSS Vulnerability on Logged Out Page
- Added several Identity Providers to the wizard
- Fixed caching issue with redirects
- Enhancements for authentication trackers
- Lookup attribute for single user update is selectable now.
- Enhanced configuration for user update from UserSync and SAML-Response
Changes specific to Jira
- Added compatibility for Jira 8 and Jira SD 4
Changes specific to Confluence
- Selectable directory for new users created from the SAML-response