We are pleased to announce Kantega SSO Enterprise 6.38.0.

Compatible applications

In general, the latest version of Kantega SSO Enterprise is compatible with the oldest version that has not reached end of life. See Atlassian’s End-of-life (EOL) policy to get an overview of versions and EOL dates.

Changelog

Changes in 6.38.6

Release summary: Bug fixes

Bug fixes

  • Bug fixes for newer compatibility versions: see release 7.38.6.

Other changes

  • Introduced a dark feature for Content-security policy customization and and set-cookie property SameSite=None to offer the capability to still render the host in an iframe when it’s needed. Hidden in a dark feature, navigate directly to the setting through `/plugins/servlet/no.kantega.kerberosauth.kerberosauth-plugin/samesiteContentSecurityPolicyHeaders
    See more: https://kantega-sso.atlassian.net/wiki/x/kwCOdg

Changes in 6.38.5

Release summary: Bug fixes and improvements

Improvements

  • The kerberos test page now shows group based permission checks more clearly

  • Add more DEBUG level log lines to JIT group memberships provisioning for better troubleshooting

Bug fixes

  • The user properties feature had a nullpointer bug if the user was not found

  • Fix broken link to the “disable kerberos for specific users” page

Changes in 6.38.4

Release summary: Jira feature to set properties on login and other improvements

Features

Improvements

  • Better UI for presenting default Force paths

  • Better feedback when a non-writable directory has been selected for creating users

Changes in 6.38.3

Bug fixes

  • Fixed a bug that would cause the restore backup function to fail if one of the IDP configurations (or subfolders of jira-home/kerberos) had been deleted between creating of the backup and restore attempt.
    The issue shows a 500 error page upon backup restore:
    /plugins/servlet/no.kantega.kerberosauth.kerberosauth-plugin/restore-backup
    And an entry in the logs:
    java.nio.file.NoSuchFileException
    If that happens you should still have the configuration before the restore attempt in the Atlassian Data Center app home folder (jira-home or on with cluster jira-shared)
    jira-home/kerberos_oldhome
    First you can disable Kantega SSO plugin
    Move
    jira-home/kerberos to jira-home/kerberos-failed-restore
    and then move
    jira-home/kerberos_oldhome to jira-home/kerberos
    Then enable Kantega SSO plugin

Changes in 6.38.2

Bug fixes

  • Fixed a bug introduced in 6.38.1 that caused instances with “Prevent traditional login” on to have problems with REST endpoints resulting in exceptions.

  • Fixed an issue that could cause User Cleanup page to not display at all when license was not present

Changes in 6.38.1

Release summary: Bug fixes and dark feature user administration

Bug fixes

  • Fix combinations all of prevent traditional login for JSM and Jira

  • Allow SSO websudo for all admin URLs

  • : Allow really large git requests to pass successfully through SSO filters

Improvements

  • Directory admin: Allow to create, rename and delete internal directories on URL:
    /plugins/servlet/no.kantega.kerberosauth.kerberosauth-plugin/manageInternalDirectories

  • User admin: Allow search for and to move specified users from one directory to another on URL:
    /plugins/servlet/no.kantega.kerberosauth.kerberosauth-plugin/manageUsersInDirectories

Improvements

  • Internal rewrites to standardise login behavior and to prepare for new features in Just-in-time and anonymous browsing coming soon

Bug fixes

  • resume login will now verify that IdP config is enabled

Changes in 6.38.0

Release summary: Major internal rewrite SAML/OIDC to make login behavior the same

Improvements

  • Internal rewrites to standardise login behavior and to prepare for new features in Just-in-time and anonymous browsing coming soon

Bug fixes

  • resume login will now verify that IdP config is enabled

  • Managed groups fails to provision group memberships