This release focuses on introduction of the following new features and improvements:
CustomerID REST API with OAuth2 Access Tokens
Access control of a system API, we recognise that some of our customers require the core APIs for CustomerID to be available to a diverse group of users, both internal and external to their organisation. In this release, you will be allowed, as owner of the service, to give access to specific administrator users in your system to perform API calls with OAuth2 access tokens. With the addition of OAuth2 access tokens, we have also include the disabling of the current username / password option if the system operator wants to limit all users to only use OAuth2 access tokens for API calls. It should be noted that there is no RBAC functionality within this release. Therefore, it is recommended to use this release version in your testing environment or with known administrators as the OAuth2 access token will permit an administrator to perform any known CustomerID API function - all API requests will be logged, but a malicious administrator could misuse API's within your platform just like they could misuse API calls if they have the username/password credentials currently. The future RBAC controls will limit administrator scope and view to defined API calls.
Proof Key for Code Exchange (PKCE) for OAuth 2.0
Whenever mobile clients or single-page applications are starting user sessions using OAuth 2.0, there is opportunity for malicious code on the mobile device to intercept the token setup and either highjack the session, start a new session with an authorised token by copying the just received good token or inject unwanted code into an otherwise secure session. This is often referred to an "authorisation code interception attack". To resolve this, Proof Key for Code Exchange or PKCE ("pixy"), can be implements as a method to ensure the security of the initial token exchange. During the authorisation request, PKCE requires any enabled OAuth 2.0 application, mobile or desktop, to generate a random value which is hashed (PKCE recommends SHA-256), this hashed value becomes the security check-sum to be verified. If you are looking for code flow or more details, there is a good writeup of PKCE here. The addition of PKCE for SSO as Authorisation server (IDP) is an example of our continued commitment towards helping to secure your operational environment. Additionally, it is worth noting that PKCE will become a requirement within the upcoming OAuth 2.1 specification.
Life cycle management
Life cycle management of the Ubisecure Identity Server is key and core to our corporate values. During this 2021.1 development cycle we have combined a number of manual procedures into automated elements operating all the time within our development pipeline. Like most modern applications, Identity Server utilises open source software to both speed development of our core features and to ensure that the Identity Platform benefits from shared security of the global open source community. The open source code we use is probed, hacked and patched regularly. Keeping the libraries we use up-to-date is an essential part of our commitment to you. In addition to removing security vulnerabilities (CVEs), the updating of open source libraries will often remove deviations (bugs) found in the open source code which may have caused user errors or other unintended consequences when using our Identity Sever. The work we completed at the start of this year, related to our continuous integration pipelines, has given us the ability to easily update the third party components and libraries used. Thus ensuring that every updated version of code you install contains the latest patched open source software available when we release updates. Applying the patches and updating Identity Sever regularly is the best way you can secure and optimise the performance in your operational environment.
Starting in 2021.2 Release Notes, we will be adding in a technical life cycle management track to all release notes. The technical track will follow the supported lifecycle management of all main external components used within supported installations of our Identity Server Platform. Questions like which Tomcat version is in use and how long is the current PostgreSQL being supported will be answered clearly, and maintained in the future. For existing installations, we will be testing and updating instructions to assist your move from 9.6 to 12.5 during the first half of 2021. Prior to that if you have any questions over supported versions or life cycle management, please check our System Recommendations and Supported Platforms page or open a ticket with our Support team.
Additionally, you will find a listing of known issues, with internal ticket references at the bottom of this page.
- 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-2766 - CustomerID REST API now support OAuth2 access tokens for authentication. This allows Administrators to enable access to specific users instead of relying on hardcoded username and password being distributed throughout the organisation. More information on how to configure this for your system can be found from Configuring OAuth2 authentication for REST API
- IDS-2767 - API calls using OAuth2 access tokens have been added to audit logs. This will allow Administrators of the system to better monitor which users are using with API calls compared to previous hardcoded username and password. More information can be found from Logging - CustomerID
- IDS-2768 - Administrators are able to disable basic HTTP authentication and query parameter authentication using simple username and password for REST APIs to make sure REST calls can only be done with OAuth2 access tokens. See REST API configuration options - CustomerID for details
- IDS-2707 - CustomerID dependencies have been updated to remove vulnerabilities. You can find the latest versions used in the CustomerID Table 1 on 3rd party licenses - CustomerID
- IDS-2855 - CustomerID REST API 1.0 has been updated to use same authentication methods as other API versions. Information on how to use different authentications can be found from REST API authentication - CustomerID
|IDS-561||There is a known issue where SSO does not check the mappingURL value when creating or editing an inboundDirectoryMappings when using the SSO REST API. Directory Mappings are possible to be created, but then not opened or edited.|
|IDS-608||There is a known UI/UX issue where a very large site list is displayed within the SSO management UI. This results in hard to use UI if large lists of sites are present in the SSO deployment. A possible workaround is to use an ldap editor to configure the authorization policies and groups.|
|IDS-941||There is a known issue where unregistered SMTP OTP authentication will not permit TLS or any secure authentication. Documentation improvement will be made to ensure proper configuration is shown if unsecure SMTP servers are required.|
|IDS-1030||There is a known issue where running the CertAP setup.cmd in a windows environment will post errors of missing linux tags. While these errors are unsightly, they can be safely ignored. This issue will be corrected in a future release.|
|IDS-1039||There is a known issue where a user account will ask for a sixth OTP verification after five consecutive failed OTP verifications have occurred. The five consecutive failures results in a locked account, the user should be informed that they must wait for the OTP timeout to expire before they attempt to login again.|
|IDS-1127||There are known documentation issues within OpenLDAP clustering with SSO.|
|IDS-1171||There is a known issue when using OpenLDAP 2.4.44 when performing SSO session cleanup which will cause replication issues.|
|IDS-1499||There is a known issue where SSO will return http 401, rather than http 400 when token introspection without an authentication header or when invalid credentials are present.|
There is a known issue with the tokens used to reset your password. If a user requests multiple password reset tokens, the old ones are not invalidated, however they are not refreshed and will become invalid after expiration time.
There are built-in features that can be used to mitigate
|IDS-1525||There is a known issue where SSO logs will contain a stopped search warning entry when tomcat is shutdown. This error can be safely ignored. |
|IDS-1526||There is a known issue where SSO logs will contain a unstopped thread warning entry when tomcat is shutdown. This error can be safely ignored.|
|IDS-1832||There is a known issue where editing an existing authorisation policy (example case added an attribute) resulted in the alteration of ubiloginNameValue. This affects SSO 8.3.0 and later. There is no work around at this time.|
|IDS-1893||There is a known issue if you use OpenID authentication, a user cannot access SAML or Ubilogin web applications. Work around use any other non-OpenID authentication method. If OpenID is required, then use OAuth 2.0 application.|
|IDS-1995||When using BankID and Safari, during initial login Safari displays a 0kb file being downloaded when there is no downloaded file|
|IDS-2059||There is a known issue where the authorisation endpoint may become corrupted if a URL contains "%b" in URL encoded format.|
|IDS-2089||There is a known issue where shutting down Ubisecure Accounting service on a windows server will show errors within the ids-accounting.log.|
|IDS-2090||There is a known issue where the SSO management UI will not filter results correctly if the filter expression is short, contains incorrect filter expressions and there are Scandinavian characters included.|
|IDS-2092||There is a known issue where the tomcat log will show a severe servlet warning for com.ubisecure.ss-ui. However, this warning is due to a user repeating the same action (double clicking an item or using the back button). This warning can be safely ignored and will be addressed in a future release.|
|IDS-2094||There is a known issue where disabling the main account in the SSO login directory does not disable the User Driven Federation accounts. Users are still able to login to services with the Federated account even while the main account is disabled. Work around: Administrators who are disabling a main login directory account should ensure that they check and disable any associated UDF accounts at the same time. This issue will be addressed in a future release.|
|IDS-2095||There is a known issue that the Acccounting service generates a temp folder under Ubisecure\ubilogin-sso\accounting\temp each time it is restarted. A workaround that system administrator can do is to create a cron job that removes these folders on a regular interval.|
There is a known issue where attempting to use exceptionally long SAML Entity IDs will result in creation failure (larger than 64 characters) . There is no known work around and may not be possible to resolve due to LDAP field limitations. We will address this in a future release.
|IDS-2120||There is a known issue where dual node SSO will require jndi.properties to be manually configured on the second node during SSO upgrade.|
|IDS-2121||There is a known issue where dual node SSO will require settings.sh to be manually configured on the second node during SSO upgrade.|
|IDS-2226||There is a known issue with using escape characters like '=' for a Site that causes the SSO management UI to be unable to map applications to the site. Workaround is to make sure not to use any Escape values for Site names (https://ldapwiki.com/wiki/DN%20Escape%20Values).|
|IDS-2247||There is a known issue with OTP_LOGIN_REMAINING_PASSWORD_AMOUNT configuration that prevents SSO from showing warning message to the end-user when OTP list is running out. Currently there is no workaround known.|
There is a known installation issue when using SSO Password reset. Using the installation instructions for password reset tool requires an administrator to run tomcat update. This occasionally results in an empty context.xml file being created which causes SSO to fail when being restarted. Workaround, repeat the run tomcat update step which will create a correct .xml file and SSO will restart.
|IDS-2314||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.|
|IDS-2315||There is a known issue that SSO returns refresh token for un-registered users. This should not be done since there is no way of handling the lifecycle of the un-registered user's refresh token.|
|IDS-2332||There is a known issue when using OpenLDAP in SSO where slapd runs out of connections to process incoming requests.|
|IDS-2478||There is a known issue in SSO that it is not possible to have different localisations for access_denied returned by IdP and local access_denied, for example if directory user mapping fails after successful authentication|
|IDS-2663||There is a known issue where creating a new site via a Safari browser where the site as an @ symbol in the email address will cause an error and no site will be created. This error is not experiences with current Chrome or Firefox browsers. As a work around please use one of these alternate browsers.|
|IDS-2721||There is a known issue when using OAuth2 applications where the target application name is not shown, but should be by using the client_name parameter in the JSON metadata.|
|IDS-2750||There is a known issue where refresh tokens are invalid for Unregistered SMS with an Ubilogin Directory user. There is no work around for this item.|
|IDS-2790||There is a known issue with sending in invalid formatted request to introspection endpoint returns stack trace including server version number. This can be mitigated by following our Security considerations for using reverse proxy and customising error pages with HAProxy Security considerations for production environments - SSO|
|IDS-2828||There is a known issue with Ubiki.jar which causes it to be unable to output a CSR file for the certificate contained in unix/win32.config|
|IDS-2829||There is a known issue that TOTP API is unable to generate secret for user if keysize has not been configured in the method. This is mitigated by ensuring that keysize is set when creating TOTP method.|
There is a known issue with user approvals from Users view. If there are required attributes for the approval step, these are not validated if approval is done through the Users view.
|IDS-1332||There is a known issue with CustomerID where it is not possible to use one email account for multiple UIDs created in CustomerID. Work around: It is possible for the system administrator to use custom attributes holding the same email address in the second or third CustomerID UID.|
|IDS-1358||There is a known issue within CustomerID where an administrator applying permissions across a whole organization will result in a failure of CustomerID to initialise. Work around: Admins should ensure that they do not apply permissions to an entire organisation, but apply the permission to a specific organisation class. All classes within an organisation may have the permission added, but not to the whole organisation at the same time, during the same commit.|
|IDS-1365||There is a known UI improvement for lists of Users and Roles for CustomerID administrators. Currently the lists are not ajax based, which means that cannot be called via popup, unlike other lists seen in CustomerID Admin UI. While this does not cause an error, it is not ideal from a usage point of view.|
|IDS-1373||There is a known issue in CustomerID when a new user is created in a non-virtual organisation, the invitation can contain a role when no role has been approved for that user.|
|IDS-1380||There is a known issue with CustomerID organisational attributes where the UI validation (validation.json) is not utilised. This impacts MOD001, POST100, PUT101 and MOD003. Using the API calls will result in good responses, but no organisational attribute change will be made.|
|IDS-1382||There is a known issue within CustomerID mandates where no email is sent to the user or organisation when the configuration is set to false ( mandate.receiver.approval = false), even though the administrator requests a mail to be sent. No error or warning screen is displayed.|
|IDS-1389||There is a known usage limit in CustomerID Mandates. When viewing a mandate, currently only the role is shown. It would be more user friendly to show both the role and its organisation within the mandate view. There is no workaround.|
|IDS-1411||There is a known issue within the CustomerID XML schema ID, if an administrator makes an error and reuses and existing variable ID, this second use of the variable ID will not be assigned but the organisation will still be created. No error is reported. This can cause troubleshooting and usage errors. Workaround: Administrators should ensure that variable IDs are unique prior to creating new variable IDs within the system installation.|
|IDS-1413||There is a known error in CustomerID mandates if the mandate name is longer than 61 characters. If longer than 61 characters, creating the mandate will fail. Workaround: Do not create mandate names longer than 61 characters.|
|IDS-1418||There is a known issue with CustomerID REST API MOD008. If an administrator removes a single mandate role from a user with multiple mandate role, the original (removed) mandate template still exists within the LDAP database. This can result in troubleshooting errors and database checking errors (backup, etc).|
There is a known issue with CustomerID REST API MOD021 when creating a new user. Even when the API call appears to work, the user is not added to the organisation. Workaround: Do not use REST MOD021 (modification) during the of a new account. Please ensure you use create APIs when making new users.
|IDS-1446||There is a known issue when using CustomerID REST API MOD009 to create a new user. The API will return 200 OK even when the new user password is not set; this results in a failed account creation. Workaround: Do not use REST API MOD009 (modification) to create a new user account. Please ensure you use create APIs when making new users.|
|IDS-1463||There is a known issue when using the CustomerID lost password recovery wizard where the wildfly server will log an exception in the error log. The password reset works correctly for the end user, but the resulting log file is cumbersome for large deployments where end users often reset their passwords. The error exceptions can be safely ignored, these will be corrected in a future release.|
|IDS-1468||There is a known issue caused by an Administrator altering the name of an Organisation when a new user has registered but not yet been approved. An application error occurs and is logged. Workaround: To avoid this only change an organization name when the pending user view is empty.|
|IDS-1474||There is a known issue that results in unsaved organisational custom attributes occurring when approval is set to false; attributes are saved when they should not be.|
|IDS-1476||There is a known issue within User DrivenFederation (UDF) of a social login during registration. If a user attempts to register more than one social login (UDF) against an external account a warning error message is presents. Resolution will be to provide the user a message explaining that they have already UDF'd a social account to this internal account and it is not possible to register a second social account.|
|IDS-1478||There is a known issue that results in a null pointer exception with stack trace if a user attempts Self Service User Driven Registration (UDF) of a social login account when UDF is not enabled within the CustomerID service.|
|IDS-1494||There is a known issue that causes occasional error pages to be displayed when a user logs out of their federated (User Driven Federation, UDF) social login account.|
|IDS-1500||There is a known issue where an error condition is caused if a user creates a password via the UI with 3 or more characters of their first or last name. Password verification does not permit this, and an error is raised. This error is not present if user passwords are created via API call.|
|IDS-1504||This known issue is a regression. When a user is invited to multiple roles, only one role appears in the invitation screen. This impacts both CustomerID Admin UI and user Self-Service.|
|IDS-1509||There is a known issue where a new user being invited to a virtual organisation the CustomerID administrator cannot approve the user; an internal server error occurs.|
|IDS-1555||There is a known issue where the mandate tab cannot be accessed on the CustomerID UI if the localisation information is incomplete. Workaround is to ensure that all localisation fields are completed.|
|IDS-1681||There is a known issue where the cursor focus remains in the mobile text field after a user has selected the email confirmation, when both email and mobile confirmations are required.|
|IDS-1706||There is a known issue with null values (DbAssignable.set and DbAssignable.isNull) which may result in NullPointer exceptions when using REST calls. This impacts Roles, Mandates and Invitations.|
|IDS-2033||Search response when using the CustomerID authoriser rule will return duplicate entries if capitalisation is present in the searched term or in the database field. In the future, no duplicates will be returned even if capitals are used or present in the naming field. Example: friendlyName and friendlyname.|
|IDS-2091||There is a known issue that the "New Organization" field in the "Open user applications" approval tab sometimes shows incorrect status|
|IDS-2093||There is a known issue that listing of users doesn't take into considerations users that are in locked status|
|IDS-2162||There is a known issue in CustomerID within Mandates, where no renotify email is sent to the administrator when an existing user requests a mandate for an existing additional organisation. No email is sent to Administrators for approval and no errors are logged. There is no workaround for this issue.|
|IDS-2201||There is a known issue in CustomerID where an email to a user with a single expiring or expired role will have all open roll invitations listed in the email, not just the expiring or expired role invitation.|
|IDS-2205||There is a know issue in user registration where the "Mobile input field was not confirmed" error message is left in the UI even after the user has verified their mobile number if they have other invalid fields to correct|
|IDS-2207||There is a known issue in CustomerID where interrupting the creation of a pending user will reset localisation of the browser session.|
|IDS-2231||There is a known issue when Administrator denies a role request for a user, that user gets two emails sent to them. One stating "Role invitation denied" and a second one stating "Role denied".|
|IDS-2233||There is a known issue in CustomerID API 1.2 REST call MOD025 "Create Role Invitation" related to email notification. If this REST call is used, the inviter mail address configured does not get a notification when the end-user approves the received role. The notification still works if role invitations are done through the GUI.|
|IDS-2234||There is a known issue where a user who has been invited to a role but not registered for that role within the defined time limit does not receive a reminder email that they have been invited to a role. See also: IDS-2235 below.|
|IDS-2235||There is a known issue where a user who has been invited to a role but not registered for that role within the defined time limit is not informed that the role invitation has expired. The user will have an email invitation with URL that does not function, they may become confused as they are not informed that the invitation has expired. See also: IDS-2234 above.|
|IDS-2290||There is an issue opening approval tab under main organization branch if there are around 10 000 sub-organizations. As a workaround, you can choose not to use recursive selection by adding "admin.approvals.recursive.selection.default = false" to you eidm2.properties file. See also: IDS-2310 below.|
|IDS-2310||There is an issue searching roles under main organization branch if there are around 10 000 sub-organizations. As a workaround, you can choose not to use recursive roles by adding "ui.organization.roles.recursive = false" to you eidm2.properties file. See also: IDS-2290 above.|
|IDS-2311||There is a known issue in approval view where changing main organization for a pending user in a sub-organization fails to create the new sub-organization in LDAP. This will need to manually be resolved by removing the invalid sub-organization in SQL|
|IDS-2312||There is a known issue in approval view where changing technical name of an organization to include Scandinavian letters doesn't work.|
|IDS-2420||There is a known issue in registration when pressing Enter without filling in all required fields causes registration to get cancelled instead of highlighting the required fields needed to complete the registration. Identified in CID 5.3.5|
|IDS-2649||There is a known issue with REST API 1.0 (MOD004b) & 2.1 (PUT103) when updating user's custom attribute to empty it does not remove the value for LDAP|
|IDS-2652||There is a known issue if a username attribute is removed via Admin or Self-Service UI then saved in an empty state, the UI will display an internal error.|
|IDS-2683||There is a known issue where CID REST API's 2.0 and 2.1 do not locate organisations with URL encoded characters in their names. Work around, if possible, ensure there are no URL encoded characters within organisation names. (example Ä Ö Å).|
|IDS-2703||There is a known issue where a role name with different case can be created which results in one LDAP entry and two SQL entries.|
|IDS-2709||There is a known issue where an installation which has defined custom attributes will cause a stack trace to be logged if a user is created without filling in all custom attributes. Work around: do not create users without all custom attributes configured.|
|IDS-2712||There is a known issue where an internal error is shown and stack trace is logged when a user registers with the same organisation name as an existing organisation but in a different case. Example. "UBISECURE" when "Ubisecure" already exists.|
|IDS-2713||There is a known issue impacting Windows server installations, where the import and export tools fail to move users between CustomerID 5.3.x and later versions.|
|IDS-2814||There is a known issue where Self Service will not open a user control window if the UDF (user driven federation) link refers to an obsolete authentication method. For example if the external identity has switched from SAML to OIDC. An exception is presented. There is no work around at this time.|
|IDS-2816||There is a known issue which will create an unhandeled exception if the users SMTP server cannot be resolved. This issue will cause a database collision issue which may prevent the same email address from being used, as it already exists within the database but not in a fully created form.|
|IDS-2851||There is a known issue with SSO policy.password.history when used together with password.2 (CustomerID). If this configuration is set for CustomerID password method, new users are unable to be created.|
There is a known issue if user is rejected from UI error is logged "Error when trying to get approval request with ID: null". A stack trace is logged. This stack trace can be safely ignored.
Considerations and limitations
SameSite cookie changes in Google Chrome
In Google Chrome version 80 and above, the default behaviour of cookies that are used in cross-domain use cases have changed. If your applications or services are communicating between different top-level domains you need to take the following actions as described in our SameSite cookies changes technical announcement to ensure that they continue to operate as before.
Long Certificates Require Manual Installation in Linux Version
When a certificate is set in suffix.pfx, whose base64 encoded string is longer than about 4000 characters, the installation of SSO ends in a failure. This is due to an issue with an OpenLDAP tool ldapmodify, which is unable to read lines longer than 4096 characters long and the installation script writes the base64 encoded certificate in one line in secrets.ldif. To address this issue, a tool ldiffold.sh was included with SSO 7.1.0 linux version, which wraps given ldif file so that it no longer contains lines that are too long. It can be run as follows:
Ubilogin Ticket Protocol Attribute Size Limits
The Ubilogin Ticket Protocol uses the HTTP GET method to send authentication and authorization information from UAS to Web Agents. The HTTP GET method has a size limit. The size limit affects the amount of information it is possible to successfully send from UAS to Web Agents. The SAML 2.0 protocol resolves this size limit by using the HTTP POST method to send information from UAS to Web Agents.
Ubilogin SAML Service Providers use SAML 2.0 protocol.
Ubisecure SSO, SAML 2.0 and High Availability
When installing Ubisecure SSO in High Availability mode, there are some restrictions due to some protocol requirements when using SAML 2.0. Please refer to the Ubisecure Clustering document for more information.
Backwards compatibility issues
Swedish BankID Authentication Adapter
As of Ubisecure SSO 8.4.1, the Swedish BankID Mobile authentication adapter has to be configured using the JWKS key id (kid) exposed in the SSO JWKS metadata. See Installing and configuring Swedish BankID - SSO for more details.
- No labels