• Fixed issue where filtered LDAP users might be reactivated during login when "Update Users from Remote Directories" is enabled.

• Fixed issue where filtered LDAP users might be reactivated during login when "Update Users from Remote Directories" is enabled.

• SAML Single Sign-On 6.8.3 comes with the User Sync 2.11.3 release, see 2.11.x release notes.
• Fixed an issue where a base URL warning was displayed in the WebSudo popup.

• SAML Single Sign-On 6.8.3 comes with the User Sync 2.11.3 release, see 2.11.x release notes.
• Fixed an issue where a base URL warning was displayed in the WebSudo popup.

• SAML Single Sign-On 6.8.2 comes with the User Sync 2.11.2 release, see 2.11.x release notes.
• Fixed an issue in the AtlasUserResult where the isSuccess() method was missing. The absence of this method could disrupt Groovy Transformations and result in unexpected outcomes.
• Fixed an issue where the relayState was not retained when the "Display a button on Jira's Dashboard login gadget and login page" option was enabled, and as a result, the URL behind IdP-Login-Buttons did not contain the original URL.

• SAML Single Sign-On 6.8.2 comes with the User Sync 2.11.2 release, see 2.11.x release notes.
• Fixed an issue in the AtlasUserResult where the isSuccess() method was missing. The absence of this method could disrupt Groovy Transformations and result in unexpected outcomes.
• Fixed an issue where the relayState was not retained when the "Display a button on Jira's Dashboard login gadget and login page" option was enabled, and as a result, the URL behind IdP-Login-Buttons did not contain the original URL.

• SAML Single Sign-On 6.8.1 comes with the User Sync 2.11.1 release, see 2.11.x release notes.
• Improved error messages in trackers to make them more human-readable.
• Fixed: Resolved an issue where the multi-IdP metadata reload status was not updated in the configuration if a reload failed.
• Fixed a problem where Jira Service Management would redirect to the login page without redirection being enabled, ensuring proper redirection behavior as expected.

• SAML Single Sign-On 6.8.1 comes with the User Sync 2.11.1 release, see 2.11.x release notes.
• Improved error messages in trackers to make them more human-readable.
• Fixed: Resolved an issue where the multi-IdP metadata reload status was not updated in the configuration if a reload failed.
• Fixed a problem where Jira Service Management would redirect to the login page without redirection being enabled, ensuring proper redirection behavior as expected.

• SAML Single Sign-On 6.7.1 comes with the User Sync 2.10.1 release, see 2.10.x release notes. This update resolves high CPU and memory usage during synchronization.

• SAML Single Sign-On 6.7.1 comes with the User Sync 2.10.1 release, see 2.10.x release notes. This update resolves high CPU and memory usage during synchronization.

• SAML Single Sign-On 6.7.0 comes with the User Sync 2.10.0 release, see 2.10.x release notes.
• Added Single Logout for OIDC in Jira Service Management.

• SAML Single Sign-On 6.7.0 comes with the User Sync 2.10.0 release, see 2.10.x release notes.
• Added Single Logout for OIDC in Jira Service Management.

• SAML Single Sign-On 6.6.0 comes with the User Sync 2.9.0 release, see 2.9.x release notes.
• Added WebSudo support for OIDC.
• WebSudo: forceAuthentication can now be deactivated.
• Fixed: the Linchpin endpoints are no longer accessed from the frontend when not running on Confluence.

• SAML Single Sign-On 6.6.0 comes with the User Sync 2.9.0 release, see 2.9.x release notes.
• Added WebSudo support for OIDC.
• WebSudo: forceAuthentication can now be deactivated.
• Fixed: the Linchpin endpoints are no longer accessed from the frontend when not running on Confluence.

• This version includes a bugfix in User Sync 2.8.1, see 2.8.x release notes.

• This version includes a bugfix in User Sync 2.8.1, see 2.8.x release notes.

• SAML Single Sign-On 6.5.0 comes with the User Sync 2.8.0 release, see 2.8.x release notes.
• Added Relying Party Initiated Single Logout for OIDC: Logout from your identity provider and other connected services when logging out from your Atlassian product.
• Added optional IdP selection buttons on login page: Click a button to login via SSO as an alternative to using the redirection.
• Added "auth_fallback" as an additional nosso parameter.
• Added option to sign Single Logout responses.

• SAML Single Sign-On 6.5.0 comes with the User Sync 2.8.0 release, see 2.8.x release notes.
• Added Relying Party Initiated Single Logout for OIDC: Logout from your identity provider and other connected services when logging out from your Atlassian product.
• Added optional IdP selection buttons on login page: Click a button to login via SSO as an alternative to using the redirection.
• Added "auth_fallback" as an additional nosso parameter.
• Added option to sign Single Logout responses.

• SAML Single Sign-On 6.4.0 comes with the User Sync 2.7.1 release, see 2.7.x release notes.
• Added preset for OIDC with Ping One.
• Fixed logout issues when using OIDC.
• Fixed flickering authentication tracker UI for OIDC logins.
• Allow sending SAML authentication requests to a different URLs.
• Added metadata file import to the IdP page.

• SAML Single Sign-On 6.4.0 comes with the User Sync 2.7.1 release, see 2.7.x release notes.
• Added preset for OIDC with Ping One.
• Fixed logout issues when using OIDC.
• Fixed flickering authentication tracker UI for OIDC logins.
• Allow sending SAML authentication requests to a different URLs.
• Added metadata file import to the IdP page.

• Allow OAuth2 authentication with Atlassian, LinkedIn, GitHub, Twitter or Facebook
• Specific SP metadata can be provided per IdP
• User Sync now allows synchronizing profile pictures from Azure or G Suite in Jira and Confluence
• Fix a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed .
• Please check our release notes for more details.

• Allow OAuth2 authentication with Atlassian, LinkedIn, GitHub, Twitter or Facebook
• Specific SP metadata can be provided per IdP
• User Sync now allows synchronizing profile pictures from Azure or G Suite in Jira and Confluence
• Fix a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed .
• Please check our release notes for more details.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.

Fixed a medium level security vulnerability potentially allowing replay attacks, see https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2023-01-12-response-can-be-replayed-with-modified-id-when-only-the-assertion-is-signed.