Please see the current Release Notes (here - scroll down to change log) for the active release change log

• IDS-1256 - SSO now supports Authorisation Code Flow with Proof Key for Code Exchange (PKCE) and will start validating the code_challenge and code_verifier for clients that are already sending them now. PKCE is currently only supported when SSO acts as Authorisation server (IDP). More information can be found from Authorization code grant - SSO and Provider metadata reference - SSO

• IDS-2784 - Accounting Service dependencies has been updated to remove vulnerabilities. You can find the latest versions used in the Accounting Table 2 on 3rd party licenses - SSO

  • Note: Related to Spring Boot updates, server.use-forward-headers property has been deprecated in favour of server.forward-headers-strategy and logging.name has changed to logging.file.name. Please review Accounting Service additional configuration - SSO for more details

• IDS-2706 - SSO dependencies have been updated to remove vulnerabilities. You can find the latest versions used in the SSO Table 1 on 3rd party licenses - SSO

• IDS-2498 - Issue with policy.password.history parameter has been fixed and new passwords are compared against the amount of previous passwords in the system. If value is set to 5, the user can not change to the any of the 5 previous passwords used. This policy still has issues with CustomerID and causes issues in user creation if enabled for password method used in CustomerID, see IDS-2851 in known issues

• IDS-2985 - Refresh token logging have been extended with details of which refresh token was trying to be accessed to help with troubleshooting. This can be enabled by setting debug level on diag.protocol logs.

• IDS-1885 - SSO now supports Time-based One-time Password as a new step-up method. See TOTP Authentication Method for more details

• IDS-2631 - TOTP API application has been created for handling of user TOTP secrets. These API calls allow Administrators to set and remove the secrets for users through their own self-service UI/application (this is not provided within the Ubisecure Identity Server). See TOTP API - SSO for more info how to setup and configure 

• IDS-2714 - Support for PBKDF2-SHA256 password encoding has been added to SSO. All supported values can be found from Management UI authentication methods

• IDS-2571 - Improvement for handling multiple IPs in "proxy.remote-addr-name = x-forwarded-for" configuration. If there are multiple IPs included in the request, all of the IPs will be shown in the audit logs, separated by ",". This will need to be taken into consideration when parsing the audit logs. Previously multiple IPs caused issues with Ubilogin Management, Logviewer and Search applications.

• IDS-2717 - Changes to application configuration for two-factor authentication methods. If both password and a step-up method is enabled for an application, users who do not have the specific step-up method enabled on their account can log in to the application with password only. See Authentication and authorization process - SSO

• IDS-2719 - ubixmlsec library has been updated to version 1.5.8.50494 to support http://www.w3.org/2009/xmlenc11#aes128-gcm encryption algorithm that will be taken into use by Suomi.fi service in the near future

• IDS-1303 - Mobile Connect integration has been extended with support related to logging and consent. This enables Mobile Operators to take Mobile Connect Authentication and Authentication Plus product into commercial use. The items that have been updated for this feature can be found in the improvements section.

• IDS-2516 - OAuth 2.0 applications can be extended with compatibility flag ExtendedOAuth2AuditLogging. This enables additional log entries to the audit log to facilitate Mobile Connect billing use cases. This can also be use for other OpenID Connect use cases. More detailed information can be found from Additional audit logging for OAuth 2.0

• IDS-1304 - Authorisation policies have been updated with scope field. This will allow Administrators to specify which scopes should be evaluated for OpenID Connect and OAuth 2.0 applications. You can read more about how to Manage authorization policies - SSO here

• IDS-2522 - Improved consent page includes requested scopes and confirm/cancel buttons instead of previous static text and checkbox. This improvement can be used for OpenID Connect methods and OAuth 2.0 applications. For other applications and methods, an updated static page of consent information will be shown to the end user. Read more about how to configure the consent screen from our Login screens - SSO and Internationalization - SSO documentation pages. 

• IDS-1591 - Mobile ID (Mobiilivarmenne) phone number input field has been changed from 'text' to 'tel' to improve the user experience on mobile devices. Users default screen will show number keypad rather than alphabet keyboard, easing use of the service

• IDS-2486 - Optimisation of LDAP search in Password Reset application related to lookup of available methods

• IDS-2014 - Additional information for the different entry types has been added to our Audit log description - SSO

• IDS-2034 - Improved documentation how to setup authentication methods using SSO Management API can be found from OpenID Connect authentication method - SSO

• IDS-750 - Improved documentation related to handling of error situation not to expose any sensitive server or software information. Read more about how to use reverse proxy in our Security considerations for production environments - SSO

• IDS-1487 - Improved version handling of SSO components in order to have a better understanding of which version is currently installed. Logging of correct version (i.e. same as the release version) during SSO startup

• IDS-2445 - Improvement to how threads are handled for Health check API. In clustered environments it was noticed that the health check calls could go into a deadlock due to timing issue when connection was shutting down

• IDS-2615 - OAuth2 / OpenID Connect Token responses have been changed to exclude the id_token for refresh requests. This is to make sure that no additional information is shared with the application that the user has not approved to be shared. Read more about Access Token and ID Token from Authorization code grant and web single sign-on - SSO

• IDS-2608 - Updated audit log field "Web Application User ID" to get username sent to the application in the log entries that have this field available. More information can be found from Audit log description - SSO

• IDS-2158 - Version number in the footer of SSO Management UI now correctly displays the installed version of the application

• IDS-2317 - UsernameUserMappingIdentityFactory flag has been set to disabled as default as specified in SSO 8.4.1 release notes. If this functionality needs to be enabled follow the Enabling UsernameUserMappingIdentityFactory instructions

• IDS-2032 - Changing log levels in SSO management UI will now come into affect without restarting SSO application, this would previously require a restart

• IDS-1182 & IDS-1469 - Documentation has been updated related to how to configure your reverse proxy in order not to expose any sensitive server or software information. Read more about how to use reverse proxy in our Security considerations for production environments - SSO page

• IDS-2537 - Correction to jQuery call that broke WS-Federation logout in 8.4.0 and 8.4.1. If using WS-Federation methods, we suggest to upgrade to SSO 8.5.0 to resolve this issue

• IDS-2161 - Merged changes made in SSO 8.3.8 that did not make it into SSO 8.4.0 release (see Change log - SSO)

• IDS-2058 - Addition of compatibility flag for UsernameUserMapping legacy feature in order to prevent exhaustion of LDAP connections. This will be disabled by default in upcoming SSO 8.5.0 release (Disabling UsernameUserMappingIdentityFactory)

• IDS-2166 - Inclusion of KeyID in metadata generated by SSO Management API (OpenID Connect authentication method - SSO)

• IDS-2283 - Client metadata extension ubisecure_request_parameters / acr_values has been updated to have highest priority in outbound requests in order to ensure that correct values are sent (OpenID Connect authentication method - SSO)

• IDS-1999 - Ability to configure RequestedAuthnContext through AuthnContextClassRef or AuthnContextDeclRef together with comparision for SAML authentication methods (SAML IDP Proxy - SSO)

• IDS-2303 - Ability to configure the thread pool size of Mobile PKI authentication method (Installing and configuring ETSI MSS Mobile PKI - SSO)

• IDS-2208 - Fix for StrictAudiencePolicy to be able to set the compatibility flag system-wide, this did not overwrite application or authentication method flags set in SSO 8.3.8 (OpenID Connect authentication method - SSO)

• IDS-1103 - Accounting Service 

  • More information about this feature can be found from our Developer portal (Accounting Service - SSO)

• IDS-994 - Per user authentication matching 

  • More information about this JavaScript based frontend user interface extension can be found from our public Github repository (https://github.com/ubisecure/per-user-authentication-matching)

• IDS-58 - Server side session storage/Redis product documentation (Use Redis with Identity Server)

• IDS-79 - NameIDPolicy must be set for AuthnRequest sent by SSO

• IDS-110 - Updated SSO external library (3rd party) dependencies (3rd party licenses - SSO)

• IDS-684 - AuthnContextClassRef from a SAML Identity Provider to SSO (IdP Proxy) should also be possible to be forwarded to SP

• IDS-930 - SSO management API for persistentID (PCR) name mapping

• IDS-1080 - Identity Server supports BCrypt for password encoding

• IDS-653 - Name change: Agent has been replaced with Application in SSO UI

• IDS-683 - Fix for deadlock in JLDAP

• IDS-712 - Fix usability on Unregistered SMS login screens. Focus set to OTP field

• IDS-1106 - Fix for SSO server jwks interoperability issue in Chrome

• IDS-1190 - Fix for one time feature not working for OAuth applications when there is SSO session available

• IDS-1412 - Fix for REDIS failover when the node configured in SSO goes offline

This release improves the compatibility with Finnish Trust Network. It also includes improvements on general OpenID Connect compatibility.

• IDS-2037: OpenID Connect: Ability to duplicate parameters outside the request object when sending Authorization requests as JWTs

• IDS-2107: OpenID Connect: Implementation of Key ID in JWKs, JWS and JWE

• IDS-2108: OpenID Connect: Send client_id as a request parameter in Token requests when using client assertions

• IDS-2110: OpenID Connect: Ability to perform relaxed or strict JWT aud claim validation

• IDS-2113: OpenID Connect: Improved UI locale handling

• IDS-2114: OpenID Connect: Ability to perform Authentication request with HTTP POST instead of GET

• IDS-2115: OpenID Connect:: Include the aud claim in client assertions

• IDS-2164: OpenID Connect: Ability to define static ubisecure_request_parameters to be sent with Authorization requests

• This version was omitted from public consumption due to limited use functionality

• IDS-1412: Improvements in support for Redis Cluster failover during server startup and runtime.

  • SSO now supports configuring more than one initial seed nodes which are used during SSO startup. Instructions on setting the initial seed nodes can be found here.

  • SSO now recovers from changes in the Redis cluster's topology during runtime, such as nodes going down and back up.

• IDS-1460: The errors "User not found" and "Invalid credentials" are no longer revealed in "subStatus" attribute of the JSON object "view", which can be found when viewing the page source of the login page.

• IDS-1354: Fixed warning of missing library file commons-daemon.jar in application server log during startup

  • This issue occurred in version 8.3.4 but does not cause regression other than the warning note in the logs

• IDS-1308: Finnish Trust Network: Support for SAML2 LG extension as specified in FTN SAML2 Profile v1.0 chapter 3.5.3.1.

  • SSO is now able to read the LG extension from inbound SAML 2.0 Authentication Requests and use it as the login UI locale; and write it to outbound SAML 2.0 Authentication Requests.

  • For SAML 2.0 Authentication Methods, writing the extension in an Authentication Request requires a new Compatibility Flag FinnishTrustNetwork set for the method.

  • For SAML 2.0 Applications, the Extension is read from an Authentication Request automatically if one is available.

• IDS-1326: Running the setup.sh for Enterprise Linux doesn't require high system entropy.

  • This was an errored requirement used only in 8.3.2 and 8.3.3

• IDS-1279: Mobile Connect Authentication v1.1: Error responses for Mobile Connect authentication requests are now compatible with the updated Authentication 1.1 profile.

• IDS-1146: One-time password format in OAuth SMS/SMTP grant can be freely formatted.

  • Check the documentation from Configuration of unregistered SMTP - SSO and Installing SMS authentication method - SSO.

• IDS-1117: Support for HTML emails in OAuth SMTP-OTP Grant.

  • You can set a new parameter in OAuth and our language files to set an explicit content type for emails and if omitted then plain text will be used for backward compatibility.

  • Check the documentation from Configuration of unregistered SMTP - SSO and Password Reset application internationalization - SSO.

• IDS-947: Corrected ForceAuthn authentications when user has already an existing authentication.

• IDS-1037: Made it possible to update Tomcat version.

  • Check the RefreshServlet security chapter from Security considerations for production environments - SSO and Configuring CORS with credentials - SSO.

• IDS-1106: Corrected JWK interoperability issue with Chrome browser.

• IDS-270: Password Reset - A new web application for resetting a forgotten password.

  • More information in the documentation.

• IDS-639: Support for Swedish BankID via external Authentication Adapter using Ubisecure Backchannel Authentication Adapter (UBAA) Authentication Method.

  • Technical information, installing and configuring Swedish BankID Authentication Adapter is described here

  • Installing the Ubisecure Backchannel Authentication Adapter Authentication Method is described here

    • SSO Management UI supports configuration by providing new method type Backchannel Authentication Adapter

• IDS-963: The LDAP search for finding a ubiloginAuthMapping entry in the Ubilogin Directory, that is performed each time a user is authenticated, consumes less resources

• IDS-78: LDAPS support for SSO install.sh, export.sh and import.sh

• IDS-388: The default font size for error messages is increased from 0.8em to 1.1em

• IDS-60: Disabled users cannot log in to applications with accounts that are linked by User Driven Federation.

  • When a user authenticates with a federated identity and a matching local account is returned by a FederationManager implementation (i.e. CIDFederationManager or UbiloginFederationTable), the local account status is now verified and the access is denied if the status is not valid.

  • The workaround fix Preventing disabled users from logging in with user driven federation as described in the page User driven federation is not needed anymore.

• IDS-1014: SSO management doesn't disclose the client_secret for OAuth2 application agents

  • When uploading a client metadata to an OAuth 2.0 application agent using the SSO Management Console, if the metadata contains a client_secret, the client_secret is now removed before storing the metadata in the agent configuration in Ubilogin Directory.

    • Prior to 8.3, the client_secret was not removed, but stored as is in the agent configuration in Ubilogin Directory.

  • Furthermore, even if the client_secret has already been stored in the agent configuration, as may be the case for agents that have already been activated prior to SSO 8.3, the client_secret will now not be shown in the SSO Management Console nor in the SSO Management API.

    • Prior to 8.3, the client_secret, if set in the client metadata, was shown in SSO Management Console.

• IDS-1052: OTP lists for UbiloginDirectory users created from SSO Management Console are not invalid randomly

• IDS-945: Execute flag is set for the bash scripts in the Linux version

• IDS-723: The SMTP message that is sent by SMTP OTP method sets the Date header as specified in RFC 822

• IDS-821: Some errors (such as LDAP read timeout) during password/reset don't deactivate the servlet that catches it

• IDS-437: Main Class in the MANIFEST.MF of sso-pkipolicy.jar is correct

• IDS-1074: Linux version: OpenLDAP installation script (ldap/openldap/install.sh) doesn't show an unnecessary error message ldap_modify: No such attribute (16)

• IDS-782: Added missing OTP Server files to installation package.

• IDS-578: Configurable status request delay.

  • The delays between the transaction request and the initial status request, as well as the delay between consecutive status requests after the first one, are configurable. The configuration parameters are initialStatusRequestDelay and consecutiveStatusRequestDelay. Refer also to the method configuration guide.

• IDS-658: Separate error message when authentication times out.

  • There is a new error message LOGIN_EXPIRED that is shown whenever authentication timeout occurs. The timeout is set in the ae.timeout configuration parameter. The possible error messages are listed under ETSI MSS Mobile PKI Unregistered Screen in Login Screens.

• IDS-589: Chrome: Forms submitted using POST to SSO's browser endpoints don't work.

  • SSO 8.2.19 and 8.2.24 had the issue with Chrome browser, that Forms submitted using POST method to SSO's browser endpoint return 403 Forbidden HTTP status. This caused problems for example with SAML 2.0 login sequence with Ubisecure SAML SP module, because it uses SAML HTTP-POST binding by default, which is based on send a form using POST. That issue is now fixed.

• IDS-89: Configurable length of Event Identifier

  • Length of the event identifier used for matching the authentication event in the mobile device and the browser can now be configured to be 4 to 8 digits long. This is done by setting the new configuration parameter eventIdLength, which is also described in the method configuration documentation.

• IDS-555: Show the error message for missing or invalid NoSpamCode

  • When NoSpamCode has been asked from a user, but the NoSpamCode the user has given is invalid or missing, error message is now shown to the user to indicate what went wrong.

• IDS-556: NoSpamCode field being visible or not is preserved when error message is shown

  • NoSpamCode field is hidden in login screen with error message, if the field was also hidden before the error. Conversely, the field is shown, if it was also shown before the error.

• IDS-582: Correct text in the label for the phone number is shown in the wait screen

  • The wait screen (the screen where the Event Identifier is shown) shows now correct text MPKI_UNREGISTERED_MOBILENUMBER in the label for the phone number.

• IDS-464: Mobile Connect / OpenID Connect: SSO decrypts an encrypted Mobile Connect login_hint when passed to OpenID Connect Authentication Provider

  • SSO passes login_hint to an Open ID Connect Authentication Provider as a generic unencrypted OpenID Connect login_hint also, if the login_hint originates from a Mobile Connect Authentication Request that contains an encrypted login_hint.

• IAM-2304: OpenID Connect authentication method

  • OpenID Connect authentication providers can now be used as authentication methods in SSO. For more information, please see the documentation in OpenID Connect authentication method - SSO.

• IAM-1038: OpenID Connect: Support for configuration of essential JSON Web Algorithms in encryption and signing

  • Along with the previously supported RS256 digital signing algorithm, we have added support for HS256, in which the signing key is derived from client_secret value. For encryption, there are also options for algorithms in key management and content encryption.
    Complete list of supported algorithms for the various endpoints can be found in the OpenID Connect provider metadata (see documentation for OAuth 2.0 and OpenID Connect metadata - SSO).
    Reference: https://tools.ietf.org/html/rfc7518

• IAM-2156: OpenID Connect: Configurable idtoken encryption and signing

  • Added support for enabling encryption for idtokens, which can be configured by setting id_token_encrypted_response_alg and id_token_encrypted_response_enc configuration parameters in the client metadata. The digital signing algorithm used for idtokens can respectively be configured by setting id_token_signed_response_alg (by default it is "RS256").
    Complete list of supported values is provided in the id_token_encryption_alg_values_supported, id_token_encryption_enc_values_supported and id_token_signing_alg_values_supported attributes in the OpenID Connect provider metadata (see documentation for OAuth 2.0 and OpenID Connect metadata - SSO).

• IAM-2157: OpenID Connect: Configurable userinfo response encryption and signing

  • Added support for enabling encryption for userinfo endpoint responses, which can be configured by setting userinfo_encrypted_response_alg and userinfo_encrypted_response_enc configuration parameters in the client metadata. The digital signing algorithm used for userinfo response can respectively be configured by setting userinfo_signed_response_alg (by default no signature is added to userinfo response).
    Complete list of supported values is provided in the userinfo_encryption_alg_values_supported, userinfo_encryption_enc_values_supported and userinfo_signing_alg_values_supported attributes in the OpenID Connect provider metadata (see documentation for OAuth 2.0 and OpenID Connect metadata - SSO).

• IAM-2303: OpenID Connect client integrations: JSON Web Token (JWT) Profile for Client Authentication

  • Added support for JWT based methods client_secret_jwt and private_key_jwt for client authencation. The method to be used by the client integration can be configured by setting token_endpoint_auth_method and token_endpoint_auth_signing_alg configuration parameters in the client metadata.
    Complete list of supported values is provided in the token_endpoint_auth_methods_supported attribute in the OpenID Connect provider metadata (see documentation for OAuth 2.0 and OpenID Connect metadata - SSO).
    References:
        https://tools.ietf.org/html/rfc7521#section-4.2
        https://tools.ietf.org/html/rfc7523#section-2.2
        http://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
        https://tools.ietf.org/html/rfc7519

• IAM-2364: OpenID Connect client integrations: Any port is allowed for Loopback URI Redirection

  • When a loopback URI (such as "http://localhost/app") is set in the redirect_uri or redirect_uris attribute of the client metadata of an OAuth2 application, then it is allowed use any port in the redirect_uri of the Authorization Request.
    Reference: https://tools.ietf.org/html/draft-ietf-oauth-native-apps-09#section-7.3

• IAM-2363: OpenID Connect client integrations: App-declared Custom URI Scheme Redirection

  • Applications can register customer URI schemes, such as "com.example.app", as their redirect_uris.
    Reference: https://tools.ietf.org/html/draft-ietf-oauth-native-apps-09#section-7.1

• IAM-1435: OpenID Connect client integrations: Support for scope in client metadata

  • Use the client metadata scope setting to restrict and white list the set of allowed scopes for a OAuth client.
    Scopes "openid", "userinfo" and the client_id of the metadata's owner cannot be disallowed, so they are always implicitly included in the scope list (if set in the client metadata in the first place).
    Reference: https://tools.ietf.org/html/rfc7591#section-2

• IAM-1847: Java Runtime Environment is no longer provided in the SSO installation package

  • Ubisecure SSO uses now an existing JRE installation provided in the standard JRE_HOME environment variable. This must be taken into account for all upgrades from pre-8.2 SSO's.

• IAM-2353: SSO writes information of the system environment in the diag log during start up

  • When starting up, SSO writes a comprehensive information printout in the diagnostics log about the system environment it's running on. The printout includes JRE version, environment variables, Java security providers, trusted certificates etc. This is crucial for our support, as with the JRE now removed, it would otherwise be difficult and time consuming to gain knowledge of the exact details of the environment SSO is running on.

• IAM-2873: OpenID Connect: Access token lifetime follows SSO session's lifetime

  • Access token lifetime follows the lifetime of the associated SSO session, in which the token was issued. This means that an access token's lifetime can be extended by extending SSO session's lifetime. Conversely, if an SSO session is terminated, all access tokens issued during that session are revoked.

• IAM-2982: OpenID Connect: Second use of authorization code revokes the access token that was previously issued for the authorization code

  • When authorization code replay is detected, the access token, that has been issued for the replayed authorization code during its first use, is revoked.

• IAM-2891: Error page without authentication methods is now shown also for SAML and Tupas agents

  • The plain error page, that is shown when there are no visible authentication methods to be shown, was previously skipped when the application agent was of type SAML or Tupas whereas for other agent types it was visible. This behaviour is now unified so that the error page is visible with all agents.
    Any other page (such as authentication method list also known as "menu" page) that happened to contain an error message was shown with all agents even in previous versions.

• IDS-22: Improved support for UI template setting in Password Change and Password Reset

  • There are some UI template settings, that hasn't been shown properly in the Password application. These setttings are logo.ico, logolink, logoalt, HEADER_TEXT_1, HEADER_TEXT_2 and COPYRIGHT. Now they are shown and updated correctly based on the selected UI template also in the Password Application.
    Secondly, if user changes the locale in the Password Application, the changed locale is now included in the URL that is sent in the password reset mail. Also, if the password reset was initiated from SSO login page, the changed locale is propagated back to the SSO page when user is returned there after finishing or canceling the reset.

• IAM-2376: The rules specified in methodmenu.rules are now applied correctly

• IAM-2320: Tupas IDP: If A01Y_RETLINK contains query part, the query part is now included also in the tupas response.

• IAM-2300: In fresh SSO installation, user can now define "allowed to" -group for SSO API agent

• IAM-2308: Agent type of SSO API agent is now correctly OAuth agent

• IAM-2326: WS-Federation: Continue button is now shown after successful IDP initated logout, if there's active WS-Federation session

• IAM-2311: Url is corrected for Nordea TUPAS test method (tupas.nordea.1) in methods-tupas.ldif

• IAM-1374: SSO support for wreply and wfresh paraneters in WS-Federation

• IAM-2019: SSO support for wauth and whr parameters in WS-Federation 

• IAM-1352: SSO Management API - New functionality to add/remove/modify users 

• IAM-1457: SSO Management API - New functionality to create mapping configuration (persistentId, refreshtokenPolicy)

• IAM-1735: Sms-mt-otp and smtp-otp grant, added error description to Error Response explaining the error situation

• IAM-1907: OTP Timout for Sms-mt-otp and smtp-otp grant,is now configurable in minutes. By default, there is no timeout.

• IAM-2073: TUPAS IDP A01Y_RETLINK parameter allows ignoring of query parameters from the URL(s)

• IAM-2110: Type and attribute names in SSO Management API calls for input are now case in-sensitive. Type and attribute names in responses are now in CamelCase.

• IAM-2204: Java updated to version jdk-8u121

• IAM-2197: Tomcat updated to version 8.0.42

• IAM-2066: SSO Linux UbiloginDirectory does not fail to start after reboot (because the OS changes /var/run/ubilogin ownership to root:root)

• IAM-2075: Agents with empty template field, no longer show the wrong template in login page

• IAM-2018: Agent activation file download now works also in new Chrome browser

• IAM-1833: MPKI authentication now works with mobileconnectloginhint-compabilityflag and ENCR_MSIDN

• IAM-1320: SSO Server acts as a TUPAS IDP

• IAM-1478: PCR generation - an option to use new kind of UUID format as specified in RFC 4122[9]

• IAM-1493: It is now possible to prevent SSO on server side by using agent setting (using either Forceauthn, oneTimeUse or both parameters)