• Improved Groovy attribute transformations. If you're using custom Groovy based attribute transformations, please check that user attributes are assigned properly after upgrading. There may be edge cases where adjusting the Groovy code is beneficial or required. If unsure, please open a support ticket and attach your configuration before upgrading so we can validate it.
• When using Crowd directories backed by LDAP, triggering the LDAP update in Crowd uses a builtin REST endpoint, so our Crowd plugin is no longer required.
• SAML Single Sign-On 5.1.2 comes with the User Sync 2.1.1 bugfix release, see 2.1.x release notes.

• Improved Groovy attribute transformations. If you're using custom Groovy based attribute transformations, please check that user attributes are assigned properly after upgrading. There may be edge cases where adjusting the Groovy code is beneficial or required. If unsure, please open a support ticket and attach your configuration before upgrading so we can validate it.
• When using Crowd directories backed by LDAP, triggering the LDAP update in Crowd uses a builtin REST endpoint, so our Crowd plugin is no longer required.
• SAML Single Sign-On 5.1.2 comes with the User Sync 2.1.1 bugfix release, see 2.1.x release notes.

• SAML Single Sign-On 5.0.7 comes with the User Sync 2.0.5 bugfix release, see 2.0.x release notes.

• SAML Single Sign-On 5.0.7 comes with the User Sync 2.0.5 bugfix release, see 2.0.x release notes.

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known

Sorry! - We have to ask you to update (again!)

On July 29th, we released a "fix version" for a critical security vulnerability, however, due to researcher feedback & additional follow-up, we realized another attack vector.

This version (released August 12th) addresses this additional scenario. We expected this to be the final & complete fix.

To allow upgrades to a fix version without major upgrades in the Atlassian application, all public versions in the marketplace include the fix to the security vulnerability.

Please reference the version history for the most relevant version for your instance. https://marketplace.atlassian.com/apps/1217045/saml-single-sign-on-saml-sso-bitbucket/version-history

Please refer to this wiki page for the latest status: https://wiki.resolution.de/doc/saml-sso/latest/jira/security-advisories/2021-07-29-authentication-bypass-network-attacker-can-login-to-users-accounts-when-usernames-are-known