Change log - CustomerID

Change log - CustomerID

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

Ubisecure CustomerID 5.x.x

CustomerID 5.7.0 (20/01/2021)

New Features

  • 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

Improvements

  • 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

CustomerID 5.6.0 (05/11/2020)

Improvements

  • IDS-2719 - ubixmlsec library has been updated to version 1.5.8.50494 to use same version as SSO

CustomerID 5.5.4 (29/09/2020)

Corrections

  • IDS-2309 - Encrypted organizational attributes are now shown in human-readable format for user approval step in the Administrator UI. Earlier these attributes were shown in encrypted format for the Administrator

  • IDS-2257 - Error handling has been fixed when attempting to create a new organization, but with a case, such as "New Organization" vs "new organization". Previously this returned a stack trace in the Administrator UI. This has also been resolved in REST API 1.0, 2.0 and 2.1 to return error 409 in these cases

CustomerID 5.5.3 (25/08/2020)

Corrections

  • IDS-2170 - general.unsecure.debuglog.include.rest.password configuration key is removed due to its insecure nature of making queried passwords logged in the debug log file

  • IDS-2579 - REST API 1.0 (REQ001b) List Users now takes into account maxResults above 127 in AD LDS setup. Previously value above 127 returned all users (or maximum page size of 1000 users)

CustomerID 5.5.2 (18/08/2020)

(CustomerID 5.5.1 was omitted from public release due to a severe issue found and fixed during final release testing)

Improvements

  • IDS-2616 - Language keys in messages_xx.properties have been change to be case-insensitive to help Administrators with localisation

Corrections

  • IDS-2446 - Updating email address for a user through the Administrator GUI now updates all required fields in the database. One field was previously not updated and caused issues with new registrations for previously registered email addresses

  • IDS-2528 - Emptying custom attribute field through API 2.0 (MOD04) now also empties the LDAP field. This field was previously left populated while the SQL field was emptied

  • IDS-2650 - Duplicate language keys in messages_en.properties have been removed. With this fix, there was a change to the role removal confirmation language key "general.ui.actions.removerole" that has been replaced with "general.ui.confirm.removerole". Changes between versions can be found from Configuration changes in versions - CustomerID

  • IDS-2640 - Emptying custom attribute field mapped to SSN through API 2.0 (MOD04) now also empties the LDAP field. This was previously left populated while the SQL field was emptied

CustomerID 5.5.0 (17/06/2020)

Improvements

  • IDS-2225 - Improved version handling of CustomerID components in order to have a better understanding of which version is currently installed. Deployment of correct (i.e. same as the release version) versioned components are shown in the logs

Corrections

  • IDS-2304 - CustomerID again shows the full path of the organisation in the organisation search results in Administration view, this previously only showed the organisation friendly name

  • IDS-2330 - CustomerID roles for main and sub-organisations are again shown in different tables if configured to search for roles in sub-organisations as well (ui.organization.roles.recursive = true)

CustomerID 5.4.1 (18/12/2019)

Improvements

  • IDS-2255 - Query User REST calls in API 2.0 and 2.1 has been updated to also include organizationEntityName and organizationId in the response. More information about what values are returned can be found from REST API 2.0 - CustomerID and REST API 2.1 - CustomerID

Corrections

  • IDS-1467 - There was an ability to alter Organisational structure during the Approval of pending users.  This feature was implemented erroneously and has been removed from the Pending User approval tab. Utilising this feature, in CustomerID 5.4.0 and previous versions will result in a synchronisation error to occur between LDAP and SQL records for all pending users in the modified Organization

  • IDS-81 - Fix for User Defined Federation logout when locale is included in URL

  • IDS-2167 - Fix for NullPointerException in REST API 1.0 REQ004b "Query Organizations" when querying an organization in a non-case sensitive manner

  • IDS-2203 - Fix for Query requests in REST API 2.0 and 2.1 where additional parameters (i.e. exactMatch) are used. In CustomerID 5.4.0 the additional parameters are not considered in the requests. More information about the additional parameters and usage can be found from REST API 2.0 - CustomerID and REST API 2.1 - CustomerID

  • IDS-1704 - Fix for updating user attributes returned by CustomerID backend call during registration process. See documentation on how to use Backend query configuration - CustomerID

  • IDS-2300 - Fix for sending API requests through proxy using X-Forwarded-For with multiple IPs. This previously resulted in UnknownHostException and incorrect client IP was logged

  • IDS-1415 - Fix for Application error if user has pressed Enter key during email confirmation in registration. This fix only resolves error condition, Enter key can still not be used to confirm the email address in registration

  • IDS-1521 - Fix for Administrators to be able to change pending user's organization in approval stage. There are still a few identified issues related to changing organization for pending users, IDS-2311 (changing main organization fails to create new sub-organization) and IDS-2312 (changing technical name of organization to name with Scandinavian letters) 

  • IDS-2301 - Fix for encrypted organization custom attributes if there is an empty value in the field or one of the organizations. Previously this would return Internal Error when querying organization with REST API 2.1

CustomerID 5.4.0 (12/11/2019)

Improvements

  • IDS-80 - CustomerID now supports locale (language setting) URL parameter in registration

  • IDS-209 - Search field and "Filter results"-button is hidden if there are no mandates present

  • IDS-949 - CustomerID now supports configuration for locale parameter in returnURL (General properties - CustomerID)

  • IDS-1079 - Updated CustomerID external library (3rd party) dependencies (3rd party licenses - CustomerID)

  • IDS-1110 - Documented the following : CustomerID database migration from 5.x.x to 5.4 (Single node upgrade - CustomerID)

  • IDS-1168 - REST POST log entries are configurable for testing purposes (General properties - CustomerID)

  • IDS-1314 - Removed unnecessary "Are you sure you want to leave this page?" window in mandate role delegation screen

  • IDS-1568 - Enabled apostrophe ' as valid character in email address, i.e. john.o’reilly@ubisecure.com

Corrections

Approvals

  • IDS-1028 - Fix for cancelling rejection of role approval. If an approver cancels the rejection of role approval, the role does not get removed anymore

  • IDS-1081 - Approval tab button now updates the number of pending approvals if users that have pending approvals get deleted

  • IDS-1126 - Fix for expiration of pending users if approval is required

  • IDS-1198 - Fix for deletion of pending user if a role was added to the user through approval tab

  • IDS-1388 - Fix for unnecessary "Are you sure you want to leave this page?" window in approval rejection

  • IDS-1408 - Fix for deletion of pending user. Previously there might have been references left in the organization where there pending user was created

Configuration

  • IDS-611 - Fix for locales parameter in the eidm2.properties file

  • IDS-1099 - Fix for /eidm2/error/authnCancelled redirection

  • IDS-1187 - Fix for system user privileges related to role removal

Installation

Logging

  • IDS-1072 - Removed invalid error in server.log when user is redirected from registration to CustomerID UI

  • IDS-1367 - Organization changes are now written to diag and audit logs

Mandates

  • IDS-1075 - Fix for re-notification email for pending ORGTOORG mandate

  • IDS-1076 - Fix for expiration email for pending ORGTOORG mandate

  • IDS-1078 - Fix for filtering pending mandates

  • IDS-1362 - Email is now sent to mandatee when their mandate is removed

  • IDS-1363 - Fix for mandates allowed if user has OrganizationOwner role

  • IDS-1420 - Fix for PERTOORG mandate tab UI

  • IDS-1434 - Fix for mandate permission in organization title

  • IDS-1512 - Enforce mandate name in organization creation