Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Changelog

Excerpt

Changes in 6.15.

0

5

23 Aug 14 17:30 00 CEST

SSO on logout and group / directory rules to Prevent Basic Auth

Features

Status
colourRed
titlesaml

Bug fix: update to 6.15.x from 6.3.0 broke basic auth IP restrictions

Bug fixes

Status
titleremoved
Skipped due to issue with release publishing
  • Status
    colourYellow
    titleoidc
    Added support for triggering single sign-on redirect upon logout in redirect rules. Note that this will for automatic redirect modes render users unable to properly log out of the application unless Single Logout (SLO) is configured

  • Status
    titlehttp basic authentication
    Change switch from “enabling / disabling” basic auth to Prevent Basic Auth, which is matching the similar feature, Prevent Traditional Login. This change will trigger an update of configuration. If you have already configured IP restrictions to Basic Auth, these will persist

Changes in 6.15.1

13:00 CEST

Bug fix redirect to root page after login

Bug fixes

  • A change to the redirect engine redirecting already logged in users to the root page broke deep linking and lead to possible redirect loops when a proxy rule is interfering with the same URI

Changes in 6.15.2

09:15 CEST

Fix another issue with deep broken deep linking on redirect

Bug fixes

  • Another change in the same release had a similar, but not as intrusive effect that broke deep linking in some cases.

Changes in 6.15.3

09:15 CEST

  • basic auth
    Update to 6.15.x and above has breaking changes for Basic Auth since group and directory restrictions are added. Due to an error in the update range, updates from 6.3.0 did not trigger the update procedure, but all other versions in the range [6.3.1, 6.15>

Changes in 6.15.4

14:00 CEST

Bug fix: logged out users redirected back to the login page after login

Bug fixes

  • Status
    colourRed
    titleinstant redirect
    Broken support for context path, so systems like https://company-jira.com/contextpath/login.jsp got redirected to a 404 page after logging out and logging in again on instant redirect for SAML / OIDC

  • Status
    colourRed
    titleinstant redirect
    While fixing the support for deep linking for instant redirect, the user is now taken to the login form after being logged in, instead of redirected to the login page. With this fix, deep linking is preserved. The login respects the os_destination parameter if present, but otherwise users are redirected to the root page (dashboard) for SAML/OIDC

Changes in 6.15.

5

3

11 17 09:00 15 CEST

Bug fix: update to 6.15.x from 6.3.0 broke basic auth IP restrictions

Bug fixes

Status
colourYellow
titlebasic auth
Update to 6.15.x and above has breaking changes for Basic Auth since group and directory restrictions are added. Due to an error in the update range, updates from 6.3.0 did not trigger the update procedure, but all other versions in the range [6.3.1, 6.15>

Status
titleremoved
Skipped due to issue with release publishing

Changes in 6.15.2

09:15 CEST

Fix another issue with deep broken deep linking on redirect

Bug fixes

  • Another change in the same release had a similar, but not as intrusive effect that broke deep linking in some cases.

Changes in 6.15.1

13:00 CEST

Bug fix redirect to root page after login

Bug fixes

  • A change to the redirect engine redirecting already logged in users to the root page broke deep linking and lead to possible redirect loops when a proxy rule is interfering with the same URI

Changes in 6.15.0

14:30 CEST

SSO on logout and group / directory rules to Prevent Basic Auth

Features

  • Status
    colourRed
    titlesaml
    Status
    colourYellow
    titleoidc
    Added support for triggering single sign-on redirect upon logout in redirect rules. Note that this will for automatic redirect modes render users unable to properly log out of the application unless Single Logout (SLO) is configured

  • Status
    titlehttp basic authentication
    Change switch from “enabling / disabling” basic auth to Prevent Basic Auth, which is matching the similar feature, Prevent Traditional Login. This change will trigger an update of configuration. If you have already configured IP restrictions to Basic Auth, these will persist