/
Change log - CustomerID

Change log - CustomerID

2019-11-21

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

Ubisecure CustomerID 5.x.x

Ubisecure CustomerID 5.3.5

Corrections

  • IDS-1471: Corrected MOD026 Create Pending User logic to use the defined password for user, if user doesn't define password during registration flow.

Ubisecure CustomerID 5.3.4

Corrections

  • IDS-1488: Corrected registration behaviour when multiple users performed registration at the same time. This defect caused backend responses with CustomerID XML schema field Modify type=current-user to modify wrong user when multiple users completed registration at the same time.

Ubisecure CustomerID 5.3.3

Corrections

  • IDS-1466: Corrected backend call with disabled fields. This defect prevented having a step in registration which did not contain user editable fields.

Ubisecure CustomerID 5.3.2 (14/03/2019)

Corrections

  • IDS-1276: Corrected backend call error status handling for responses following the Ubisecure CustomerID XML schema.

  • IDS-1277: Corrected backend call error message handling for responses following the Ubisecure CustomerID XML schema.

  • IDS-1330: Corrected parametrized role assignment in registrations when a temporary attribute is used in the role definition.

  • IDS-1335: Corrected some performance problems with the organization's role tab when roles from sub organizations are also included.

Ubisecure CustomerID 5.3.1 (29/01/2019)

Corrections

Ubisecure CustomerID 5.3.0 (03/10/2018)

New Features

  • IDS-334, IDS-335: User status is shown when listing users and when looking at user information details. There is also a new status for pending users: "Waiting for registration", which means that the user has not registered yet. The previous "Pending" status is still used for users that have registered but are waiting for approval. Users that are in either of these statuses are called pending users in most use cases and the background color used for them in user lists is the same. Ability to search and remove pending users from the user interface.

  • IDS-391: Users can unlink federated accounts in CustomerID Self-Service user interface.

Improvements

  • IDS-593: Various minor improvements in the error reporting of command line scripts in the tools folder.

  • IDS-698: Added security related flags (secure and http-only) to session cookies.

  • IDS-111: Security update of 3rd party libraries.

  • IDS-184: CustomerID now supports internationalized email addresses.

  • IDS-804: Roles in mandates are listed more clearly in the user interface.

Corrections

  • IDS-972: Corrected enabling pending user via REST call MOD004 Update User.

  • IDS-1064: Corrected information updating concerning the OTP authentication method in Self-Service user interface.

  • IDS-759: Corrected response of REST API call REQ015 Query Registration when no result could not be found. Now we return 404 Not Found instead of 500 Internal Server Error. 

  • IDS-1060: Corrected Lost Password wizard.

  • IDS-742: Corrected validation error message when trying to input an already existing email address.

  • IDS-421: Corrected role handling in REST API call MOD022 Update Mandate Template.

  • IDS-803: Corrected values of resource keys when using the "show resource keys" language in mandate related user interface screens.

  • IDS-805: Corrected sending person originated mandate invite to new organization.

  • IDS-806: Correction to approval using the drop down action list.

  • IDS-807: Corrected several issues with the addrole configuration.

  • IDS-808: Corrected role request approvals.

  • IDS-839: Corrected error messages for UniqueAttributeValidator concerning the login attribute.

  • IDS-875: Corrected companyid and customerid attribute handling in registrations.

  • IDS-997: Corrected roles listing when using  ui.organization.roles.recursive=true.

  • IDS-1059: Corrected confirmation thresholds.

Ubisecure CustomerID 5.2.18 (23/03/2018)

Corrections

  • IDS-654: Fixed duplicate user check based on SSN in registrations

Ubisecure CustomerID 5.2.17 (19/03/2018)

Corrections

  • IDS-634: Fixed an error with confirmation functionality in registrations

  • IDS-566: Fixed REST call GET106 List Organizations for organizations that have no custom attributes 

Ubisecure CustomerID 5.2.16 (02/03/2018)

Corrections

  • IDS-581: Fixed potential error situation with logging

  • IDS-601: Fixed erronous sending of multiple data confirmation notifications

Ubisecure CustomerID 5.2.15

Improvements

  • IDS-550: Performance improvement for user search

Ubisecure CustomerID 5.2.14 (16/01/2018)

Improvements

  • IDS-440: Performance improvement for role approvals in approval tabs

Corrections

  • IDS-458: Password change related feedback messages have been fixed

Ubisecure CustomerID 5.2.12 (02/01/2018)

New Features

Improvements

  • IAM-2709: User search now checks that all inputs match search results

  • IAM-2077, IAM-1247: CustomerID workers have been separated from the main EAR

  • IAM-2665: Domain whitelisting for CSRF check

  • IAM-2705: Configurable favicon

  • IAM-2833: Unicode support for built-in email address format validator

  • IAM-718: User status can be defined in a human readable way in REST filters

  • IAM-2284: Organization path is visible in summary step when inviting user to multiple roles

Corrections

  • IAM-2711, IAM-2744: Possible problems with role invitation to existing user fixed

  • IAM-2671: Fixed rejecting role invitations to existing users

  • IAM-2687: Fixed name change when Active Directory is in use

  • IAM-2633: Fixed email notification concerning pending user approval

  • IAM-2636: Fixed unnecessary email renotification to pending user when user was waiting for approval

  • IAM-2888: Fixed predefined role requests

  • IAM-2896: Fixed organization removal in case there is an open role invitation for a new user

  • IAM-3018: Fixed unwanted built-in attribute mandatoriness

Ubisecure CustomerID 5.1.9 (03/07/2017)

New Features

  • IAM-1986: Possibility to pass password value to backend call in registration summary step

  • IAM-2524: Password reset works for registered authentications without user having to have an SSN attribute

  • IAM-2354: Java information is logged when the system starts

Improvements

  • Workers have been separated to their own EAR

  • Reorganization of some JARs

Corrections

  • IAM-2064: Long organization names are no longer truncated in role add dialogue

Ubisecure CustomerID 5.1.5 (25/04/2017)

Corrections

  • New version of cid-sso-adapter that does not add duplicate libraries into Ubisecure SSO when it is installed.

Ubisecure CustomerID 5.1.4 (04/2017)

New Features

  • IAM-2003: Authorizer and REST API provide more information concerning delegations

  • In an authorization policy you can use eidm:delegations, which lists role, mandate and mandatee organization for each delegation

  • GET115 and GET116 REST calls added

Improvements

  • Performance improvements

  • IAM-1946: Updated WildFly version to 10.1.0.Final

  • IAM-2005: CSRF prevention checks added

Corrections

  • IAM-1842: Modify operations targeted to current-user from backend now work for existing user

  • IAM-1947: Importtool saves locale to SQL

  • IAM-2035: Corrected a possible NullPointerException in a certain type of role invitation

Ubisecure CustomerID 5.0.x (01/2017)

New Features

  • CID-5: Database layer uses JPA and supports PostgreSQL

  • CID-11: There is a separate Derby to PostgreSQL migration package available to help updating to this version

  • CID-513: Summary step in registrations is now optional

Improvements

  • Performance improvements

  • CID-90: CustomerID uses built-in WildFly (instead of Tomcat)

  • CID-112: CustomerID is packaged as an Enterprise Archive (EAR)

  • CID-89: CustomerID uses Java 8

  • CID-288: Updated Apache Wicket user interface framework version to 7.4.0

  • CID-482: CustomerID logging can be configured via WildFly also logging format structure has been improved

Corrections

  • CID-726: Corrected situation where REST response sometimes included a -1 value in port number

Removed Features

  • CID-727: Removed organization group feature

  • CID-455: Removed network source address based restrictions from CID REST API

  • Back channel logout is no longer supported.

Ubisecure CustomerID 4.x.x

Ubisecure CustomerID 4.6.0 (29/02/2016)

Corrections

  • IAM-45: Notification about pending role reception approval is now sent to new user after successful registration

  • IAM-154: User interface handles long organization name in organization search results correctly

  • IAM-1182: REST password change validates given password against the configured password policy.

Ubisecure CustomerID 4.5.0 (27/11/2015)

New Features

  • IAM-750: REST Query to list mandates received/sent by an organization/user

Corrections

  • IAM-170: Invitation renotification email show correct links

  • IAM-899: Role invitation wizard changes. Mail template step removed.

  • IAM-921: Organization user list and search performance improved when listing users by roles

  • IAM-1111: Updating e-mail address works correctly in AD with long emails (>20 characters)

  • IAM-740: CID Lostpwd shows now actual login ID to user

Ubisecure CustomerID 4.4.1 (30/09/2015)

Corrections

  • IAM-944: Registration allows creation of duplicate users when SSN matches

  • IAM-949: When loginusernprincipalname is used as login then no new users can be created

  • IAM-971: Validators are not working on user approval

  • IAM-945: CID should not include client IP address in AuthnStatement/SubjectLocality in SAML AP requests

Ubisecure CustomerID 4.4.0 (01/09/2015)

New Features

  • IAM-736: Organizations can be created with unique random string identifier automatically

  • IAM-794: Structured authorizer role information 

  • IAM-821: REST: Search organizations by using any attribute

Corrections

  • IAM-909: User transfer from organization to another fails

Ubisecure CustomerID 4.3.0.40230 (07/2015)

New Features

  • IAM-747: Federation linking during registration workflow (UDF)

  • IAM-762: REST: search pending users by email

Improvements

  • Performance improvements

Corrections

  • IAM-775: Wrong language when transferring from registration to application

  • IAM-847: /eidm2/wf/changepwd operation based on temporary token instead of permanent one

  • IAM-260: REST: Creating ORG2ORG mandates fails

Ubisecure CustomerID 4.2.2.40007

New Features

  • IAM-747: A new way to configure authentication method activation step in registrations. It is now possible to also activate (link) external authentication methods to the created user account.

Corrections

  • IAM-738: Automatic role approvals after registration now work also for role invitations made using the REST-interface

Ubisecure CustomerID 4.2.1.39626

Corrections

  • IAM-725: Also pending users can now be searched via REST-interface

Ubisecure CustomerID 4.2.0.39098 (04/2015)

New Features

  • IAM-8: Registration workflow specific email text support

  • IAM-10: Top-level Approvals-tab is hidden in the admin user interface if user has no permissions to manage approvals

  • IAM-20: Email address confirmation is done at the user information wizard step in registrations (This is a change to the previous email address confirmation functionality)

  • IAM-38: Saml AP can be used with returnurl in registrations

Improvements

  • IAM-48: TUPAS methods can be grouped in user driven federation

  • IAM-229: Locale field can now be used also in role invitation wizard

Corrections

  • IAM-56: Mistyped email confirmation code no longer leads to an application error

  • IAM-39: In CustomerID Admin interface, organization name change now updates the view immediately

  • IAM-21: UI layout is no longer broken on approval tab (it was broken when using Firefox)

  • IAM-23: User custom attributes are saved when uniqueID attribute is used in user import

  • IAM-168: organization.class.default.restrictedRoleInvite no longer shows extra role in organization view

Ubisecure CustomerID 4.1.0.38078

New Features

  • Product name has beed changed from Ubisecure CustomerID to GlobalSign CustomerID

  • Configurable validation for attribute values

  • User driven federation support

  • More mobile friendly user interface

  • Registration fields can be prefilled from authentication method attributes

  • EIDM-1340: Automatic generation of organization technical name

  • EIDM-1372: Delete User REST query by user ID

  • EIDM-1384: Second web agent for CustomerID

  • EIDM-1391: Return URL can be given for registrations as an URL parameter

  • EIDM-1401: Verification step in registrations can now support also other authentication methods than TUPAS

  • EIDM-1348: Role invitation information can be queried via REST using user ID Improvements

  • Attribute validation is performed also for REST calls

  • Several performance improvements concerning large user amounts

  • EIDM-1349: Update user REST call can be used also for pending users

  • EIDM-1350: Query user REST call can be made based on user ID

  • EIDM-1351: Update user REST call can be made based on user ID

  • EIDM-1373: Listing users via REST can use any attribute for filtering results

  • EIDM-1374: Query Role REST call can be made based on role ID

Corrections

  • EIDM-173: Bank authentication (TUPAS) method name, title, and logo are now configurable

  • EIDM-572: Password change error messages are no longer duplicated

  • EIDM-598: An unknown TUPAS method in the properties does not present an exception in the browser

  • EIDM-618: Long information does not break the registration confirmation step display

  • EIDM-859: We will correctly report an error message if someone tries to create a sub organization that has the same name as a role in the parent organization

  • EIDM-920: Database update is now quicker

  • EIDM-991: Approval does not close if mandatory fields are left empty when approving

  • EIDM-1198: Removing multiple users is now quicker

  • EIDM-1204: Organization filtering is now quicker

  • EIDM-1255: Users imported with unique ID defined now get proper status

  • EIDM-1267: Custom usernames can now have validation via the new validation configuration option

  • EIDM-1294: Documentation updated concerning removed email.corporateRegisterEmail.message key from mail message configuration

  • EIDM-1377: Password change wizard now only sends the correct email message instead of two different messages

  • EIDM-1379: Verification now works also in protected registrations

  • EIDM-1381: Welcome message is sent for new user after create user wizard also when email confirmation is not required

  • EIDM-1383: Password change now only sends the correct email message and not two different ones

  • EIDM-1386: Reminder message about user registration is now sent correctly

  • EIDM-1392: Corrected possible problems with registration.x.temporary.fields

  • EIDM-1394: Changing language on registration no longer skips backend query

  • EIDM-1397: Pending password change expiration no longer deletes the registered user

  • EIDM-1403: Role add step can now be hidden from create user wizard

  • EIDM-1420: User CN information is now updated correctly also to the SQL database

  • EIDM-1421: Corrections to SSN uniqueness validation

Ubisecure CustomerID 4.0.0.35856

New Features

  • EIDM-1292: Mandate delegation based on user organization membership via received role

  • EIDM-1322: Support for XSLT in connection with backend query responses

Improvements

  • EIDM-1004: Suport for a separate validation code in the email message concerning email address change

  • EIDM-1318: CustomerID backend query message format implementation

  • EIDM-1342: Jersey upgrade (from 1.1x to 2.5.1)

Corrections

  • EIDM-1285: Mandate delegation and removal is now logged to audit logfile

  • EIDM-1311: Deleting organization now works even if there are pending mandates

  • EIDM-1328: Logout corrected in case saml.custid.ap has an active session in SSO

  • EIDM-1337: Role invite expire does not cause an error

  • EIDM-1338: Person mandate to new user does not anymore create a duplicate pending user when there already is a pending user with same email address

  • EIDM-1343: Empty or whitespace-only string as a result from backend query does not cause problems with parameter evaluation

Ubisecure CustomerID 3.x.x

Ubisecure CustomerID 3.12.0.34980

New Features

  • EIDM-1273: You can request predefined role sets from self-service

  • EIDM-1274: Registration workflow supports existing users

Improvements

  • EIDM-1112: Robots.txt search engine hiding

  • EIDM-1225: Role specific approval in registrations

  • EIDM-1272: Creation of several organizations from multivalue registration fields

  • EIDM-1290: Ubisecure favicon

  • Link to Administration interface from self-service if the user has the necessary permissions

Corrections

  • EIDM-1295: A problem related to role invitation renotifications has been corrected

Ubisecure CustomerID 3.11.1.34322

Corrections

  • EIDM-1257: Fixed role rejection count in the user interface in case email sending fails.

  • EIDM-1262: It is now possible to add roles also to disabled users.

  • EIDM-1275: Corrected character encoding handling when reading backend responses.

  • Nothing is automatically selected to the country list anymore.

  • Added missing self.mandate.read permission to default permissions.

  • Removed erronous self.edit.read permission from default permissions.

  • Mandate delegation panel doesn't show pending users anymore.

  • Added missing Derby starting command to Linux installation scripts.

  • Corrected an erronous path in Linux uninstall script.

  • Unified uninstallation in Linux so that also the Derby service will be removed in uninstall script.

  • Now we accept ', ` and ´ characters in firstname and surname fields.

  • Minor country ordering issue has been fixed.

  • Improved out of the box authorizer support for SSO versions starting from 6.8.0.

  • Corrected country selector behavior in IE 7 and IE 8. (Note that we don't actually officially support IE 7. However in this case we did a fix for it.)

  • Removed extra HTML coding for certain characters that were included in backend request parameters.

Ubisecure CustomerID 3.11.0.34122

New Features

  • EIDM-1210: Organization creation is ignored in registration workflow if the organization definition cannot be resolved

  • EIDM-1211: Role assign is ignored in registration workflow if the role definition cannot be resolved

  • EIDM-1212: Organization attributes may be stored separately in different organizations defined in the registration workflow configuration

  • EIDM-1251: Derby DB is started in a separate service

Improvements

  • EIDM-1247: User contact information may be added to the role approval page

  • EIDM-1222: Java updated to 64bit Java 7

Corrections

  • EIDM-1142: Special characters such as "!" in the REST password value no longer cause problems (for example when updating database)

  • EIDM-1228: It is again ok to send mandates to unregistered users when the mandate receiver approval is false

  • EIDM-1266: Custom attributes for user can be updated via REST

Ubisecure CustomerID 3.10.1.33745

Corrections

  • EIDM-1241: User information on self-service now works

Ubisecure CustomerID 3.10.0.33656

New Features

  • EIDM-1100: REST operation for role invitation for existing user

  • EIDM-1116: REST operation for listing active role invitations

  • EIDM-1208: Configurable country data type

  • EIDM-1220: REST operation for creating pending user

  • EIDM-1244: New Backend call possible when registration wizard is finished

  • EIDM-1245: Optionally require printing before registration wizard can be sent.

Improvements

  • EIDM-1223: Modify role.deassign permission for configuring role spesific deassignment

Ubisecure CustomerID 3.9.1.33383