Release highlights

This release focuses on introduction of the following new features and improvements:  

Client Credential URL Encoding Support. We have improved OAuth2.0 flow support, according to RFC6749 section 2.3.1, to include URL encoded client credentials. This feature is being released with a feature flag, off as a default. This means if your environment requires URL encoding of client credentials you will need to activate the feature flag. NOTE: this feature should be tested for backwards compatibility in your environment. Ensure that you review both the ClientID and the secret URL decoding prior to enabling this feature in your production environment. You can review specifics here. And general guidance for OAuth 2.0 integration here.

System Recommendations. As with every release we continually update the 3rd Party Library's used by the Identity Platform. Among these updates, we would like to point out Tomcat update, while there were globally observed incompatibilities with 9.0.91, these have been resolved and SSO 9.5 is being released with a later patch versiona later patch version (Tomcat 9.0.97). Also Postgres has been updated, within IDS-4904, we have updated the JBDC driver (42.7.4) permitting the latest PostgreSQL 16 to be utilised.  

The Redhat issued an end-of-life statement on Centos 7, to ensure full open source linux deployment options the Identity Platform has been migrated to Rocky8 and Rocky9 distributions. We always encourage Customers to review the System Recommendations page found with each release. If there are any questions, please do not hesitate to open a Service Desk ticket and Operations will be happy to help you resolve any environment or deployment support questions you might have. 

Please ensure you review the updated System Recommendations page and are aware of the 3rd Party License page.

Change log 

SSO 9.5.0

New Features

Improvements

• IDS-2429 - An often requested, but low level improvement to SSO is to create an example-template location within the installation package to permit Administrators creating new environments to more easily locate all of the available configuration options.   create or show link herePlease see the Example configuration directories for Linux and windows within Configuration - SSO.
• IDS-3330 - Ability to configure the timeout value within Redis when used with SSO. Please see Timeout Configuration on Redis Configuration - SSO. 
• IDS-3429 - Improved SMS authentication method (SPI Mobile Phone) to include both GET and POST message sending methods. Default remains as a GET.  Please see the documentation, section 6. Click SPI Mobile Phone tab, for more detail. 
• IDS-4449 - SSO OAuth2 supports URL encoded client credentials as required by section 2.3.1 of RFC6749. 
• IDS-4818 - An improvement has been made to both UI and API for SSO when creating or updated an applications metadata to ensure a unique clientID is used. For more detail please see OAuth 2.0 provider implementation reference - SSO, specifically the Request Parameters tableSSO when creating or updated an applications metadata to ensure a unique clientID is used. 
• IDS-4827 - Included the ability to configure the trusted SAML keys for ETSI MSS MPKI via API. 
• IDS-4856 - Improvements found in audit logging to ensure the Client Display name will be logged for each login event. This will be set with the AuditClientDisplayName flag, details can be found here.IDS-4926 - Customers with multi-node LDAP deployments will benefit from the memory management improvement made in SSO session manager. Specifically, the "clenupLockEnabeld" has been set to default true, which means this memory management improvement is applied as default. Please see the Configuring cleanup of expired SSO sessions in OpenLDAP for more information4719 - Swedish BankID adapter no longer uses a personal number during authentication of a session. Code improvement has been made to remove the use of personal number, which is no longer supported within BankID authentications.

Corrections

• IDS-4885 - Within Client Credentials, password applications which use URL encoded client secret will function without error, see also IDS-4886 in the CustomerID section.
• IDS-4868 / IDS-4763 - Through a customers low level auditing of SSO there was a hypothetical XML expansion bug found within SSO. With extensive knowledge of SSO, it is was possible to craft a hypothetical attack, however in during testing these attacks were found to result in "Ticket Validation Error" being displayed to the user (or attemptive attacker) and ERROR messages being logged. During the investigation an implementable solution was found, therefore it was decided to remove even this theoretical attack vector. A solution has been implemented which prevents this hypothetical XML expansion attack vector. 
• IDS-4847 - a correction of Azure metadata export, where the tenantid is presented with curly braces. SSO will now manage this improper format permitting improved use of this resource.
• IDS-4847 - add comment over correcting the tenantid import where Azure AD is exporting with curly braces.
• IDS-4763 - (need to work this one)
• IDS-4526 - 
• IDS-4431 - client credentials Oauth response improvement4526 - There was a know issue that occurs in SSO Management UI when removing the last user from an existing application, the UI will appear blank with no application to select. Note: Only one user can be impersonated by an application.
• IDS-4431 - There is a known issue where SSO will provide an incomplete OAuth2 response when access has been denied. This has been improved and is no longer a deviation.
• IDS-3117 - removal of The body option has been removed from the TOTP GET call. 
• IDS-3026 - Corrected deviation found in the use of RSA-OAEP-256 encryption and decryption.key management between RSA_OAEP_256 in JWE tokens, used by Nimbus and Jose4j . It has been observed that errors occur when these libraries are used with previous versions of SSO. 
• IDS-2314 - This item is not a defect, SSO verifies the account represented by refresh token still exists, is enabled etc. when a refresh token is used to get a new access token. This is obviously not possible with unregistered users where we by definition have no record of the account. Historically, this ticket carried the following description: There is a known issue with passing a refresh token to token endpoint results in "invalid_grant" error, if the refresh token has been issued to an unregistered user from an authentication method having a connected Directory Service. This issue is now closed. Please open a Service Desk ticket if you require additional details.

SSO Modules

Over the course of twenty years of development, there have been a number of code modules that have been developed for Identity Platform, specifically for SSO, which provide functionality to some deployments but where the code is not an essential component or function of found within the SSO release package itself. Within the IDS 2024.2 development cycle we have updated a number of these external modules. They provide specific solutions for specific use cases, so if you are unaware of these modules, they likely do not impact or benefit your environment. However, if you have been using one or more of these modules, we would like to work with you to ensure that your current operating environment can benefit from these latest updates. Each of the updates require a Java11 environment and have only be tested with SSO 9.5, therefore until your environment upgrades to this release, please continue using your existing modules. We would ask you to contact Support via Service Desk so we can prepare the modules to be downloadable for you - this will occur after the release of the IDS 2024.2 software. 

• Metadata Updater
• SAML SP for Java
• SAML palvelu
• CertAP

CustomerID 6.5.0

New Features

of the IDS 2024.2 software. 

• Metadata Updater
• CertAP
• SAML SP for Java
• SAML palvelu

CustomerID 6.5.0

New Features

Improvements

• IDS-3765 - There was a known issue where JDK 11.0.15 would prevent Wildfly from working/starting correctly. This has been resolved in later versions of JDK 11.x.x

• IDS-1340 - CustomerID Rest 2.1 API has been improved to permit an administrator to force password changes for existing users, this can be performed via Rest API 2.1 - CustomerID.  Please see the documentation for PUT125 Force Password Change for PATCH124 Update User.

• IDS-4911 - Improved the diag logs for CustomerID, it had been observed that warnings were being logged in diag log when invalid event listener was included in a previously release CID package.  While these events could be safely ignored, the invalid event listener has been removed which also removes the warning found in diag logs.

• IDS-4886 - Improvements have been made to CustomerID to DisableOAuth2CredentialsUrlDecoding where the application uses a URL encoded secret 

  IDS-

  permit the use of a URL encoded secret. The following flag is no longer required:  DisableOAuth2CredentialsUrlDecoding.

• IDS-4877 - Improved the management of user with OAuth 2.0 authentication to ensure both API and UI requested user moves are possible for all the following functions; 

  • Password
  • SAML 
  • OIDC
  • SMS
  • SMTP 
  • OTP 
  • TOTP

Corrections

: 

• IDS-3392 / IDS-4889 - There was a known issue when an Administrator user is used moved to another organisation then error was logged. The Administrator users was correctly moved, but a safely ignorable log entry was created. This known issue has been corrected. Now there is no log entry error present.

Please review the change log if you are upgrading your system from a prior version to IDS 2024.12:   Identity Platform

Deviations

The following deviations are found within Identity Platform and are expected to be corrected over time. For a listing of known issues found on Identity Platform please see: Considerations, limitations and known issues

SSO

CustomerID