We are pleased to announce Kantega SSO Enterprise 6.22.
Compatible applications
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
Changes in 6.22.1
15:45 CET
Release summary: Performance & visual improvements, bug fixes
Improvements
GLOBAL Fix perfomance issue with plugin collecting user agent info because of high-frequent rotation. Now toggleable (off by default) and persisted in cache replicated across nodes
SAML Support UID as an LDAP user mapping attribute
SCIM Fetch name from
display_name
attribute in sync because Okta syncs updated value indisplay_name
and not in theformatted
attributeRename references to Azure AD to new product name: Entra ID.
SAMLOIDC Improve test page since certain attributes were out of sync on dirty settings before save
Bug fixes
SAML OIDC Fix broken navigation links between dashboards
GLOBAL Fix issue with config update status when the kerberos folder has not yet been created in home folder
GLOBAL Fix issue with a specific user agent that doesn’t persist sessions in Bamboo because a cookie is set
Changes in 6.22.0
15:00 CET
Release summary: SCIM PATCH request adjustments for Okta OIN applications
Features
SCIM User linking on creation: Enable this option to link existing users automatically when they are created in Confluence. This results in POST requests with duplicate username to look up the user by externalId and link them to the existing user. If your SCIM source causes POST requests to fail with 409 response codes on user creation, this option may be a solution linking existing users with the same externalId. This behaviour is outside SCIM standard and may cause unexpected behavior and some SCIM test suits to fail. Disabled by default.
Improvements
SCIM Performance improvements to group membership assignments and group creation.
Patch operations will now be compatible with Okta OIN applications that uses PATCH requests instead of PUT like the default Okta Application.
Applications supported in the Okta OIN catalogue:
For Bearer token authentication:
https://www.okta.com/integrations/scim-2-0-test-app-oauth-bearer-token/
For Basic authentication:
https://www.okta.com/integrations/scim-2-0-test-app-basic-auth/
Bug fixes
SCIM Response codes for some operations like DELETE GROUP or DELETE USER that didn’t have any content returned, changed from 200 to 204