SAML Single Sign-OnSAML Single Sign-On
Try For Free

6.16.x release notes

What's new

ActiveObjects-based configuration storage, user provisioning in read-only mode, and improved regex handling.

Upgrade consideration

On first start after the upgrade, the SAML SSO configuration is migrated from PluginSettings/Bandana to ActiveObjects. The migration runs automatically and is idempotent. Legacy entries are kept in place.

Data Center

This version is fully compatible with Jira, Confluence, Bitbucket, and Bamboo Data Center.

Changelog

6.16.1 & 6.16.1-p8

Released on 18 June 2026 for Confluence Data Center.

  • Fixed logout loop on Confluence 9.2.21 and 10.2.13. The plugin now recognizes Confluence's new /dologout.action logout link (in addition to /logout.action).

6.16.0 & 6.16.0-p8

Released on 28 May 2026 for Jira, Confluence, Bitbucket, and Bamboo Data Center.

  • SAML Single Sign-On 6.16.0 comes with the User Sync 2.19.0 release, see 2.19.x release notes.

  • Configuration is now stored in ActiveObjects, removing the previous 99,000-character limit that prevented saving large configurations on Confluence 10.2.6 and later.

  • The regexTimeout setting is now migrated to 0 on upgrade so existing installations match the default introduced in 6.14.0 for new installations.

  • The User-Agent header is now included in the last 50 tracker details of the Support Information file.

  • Fixed a misleading "Enabled user" log entry that appeared when reactivation failed because the user directory is read-only.

Changes specific to Jira

  • None

Changes specific to Confluence

  • User provisioning now continues while Confluence is in read-only mode, aligning SAML SSO with Atlassian LDAP directories and User Sync.

Changes specific to Bitbucket

  • None

Changes specific to Bamboo

  • None