Changes in 6.2.3

28 Nov 2022 21:30 CET

Bug fix: SAML certificate expired warning crashes the config status endpoint

Bug fixes

• Calls to the /rest/ksso/internal/config/1.0/status REST endpoint, which is invoked whenever a configuration update is needed, will crash with a FileNotFoundException when on an instance where SAML is not configured in Kantega SSO Enterprise, since the Kantega SSO SAML warning made an incorrect assumption about a certificate file being present in the file system.

Changes in 6.2.2

24 Nov 2022 14:30 CET

Special release for Jira. Retry bugfix release for Jira server due to Atlassian Marketplace API failure

Bug fixes

See bug fix description in 6.2.1 above. We had to release another patch since the Atlassian Marketplace API is unstable and failed after successfully releasing the DC version of 6.2.1 to Jira. Unfortunately there is no way to upload the server version of the same app version after the fact, so we had to rebuild the code with an incremented version in attempt to also publish the Server version.

Changes in 6.2.1

24 Nov 2022 14:00 CET

Bug fix: SAML certificate expired warning crashes non-saml configs

Bug fixes

• Visiting any admin page will crash with a FileNotFoundException when on an instance where SAML is not configured in Kantega SSO Enterprise, since the Kantega SSO SAML warning made an incorrect assumption about a certificate file being present in the file system.

Changes in 6.2.0

23 Nov 2022 9:00 CET

JIT user provisioning improvements and new SAML certificate expired warning

Features

• Kantega SSO Enterprise will now give a visible warning when the SAML request signing certificate is about to expire. This will allow you to renew the certificate well before expiry, and avoid SAML being broken at any point.

Improvements

• Include the target URL in the HTTP session for Identity Providers that are unable to send the correct target URL back with the relay state

• Just-in-time (JIT) provisioning now allows you to update names and emails separately, while previouly both could only be updated at the same time.

Bug fixes

• During JIT provisioning, when reactivating a deactivated user, the name and email were updated even if the settings said that name and email are not supposed to be updated from the claims.

• Test result page had a weakness with default values of email and name attribute

• The MSTeams security filter unintentionally blocked JSM knowledgebase lookup.