Version History
Identity Service 2.0-65
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
IDP-119 UX1 Marketpalce sign-up and sign-in pages did not have Google Analytics conversion tracking.
IDP-115 An IDP call during reseller creation sometimes failed, which caused resubmitting of the creation order failure.
Identity Service 1.8-294
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
IDP-104 User password could not be updated.
IDP-105 There was the UX1 logout issue when using external IDP in ARM.
Identity Service 1.8-287
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
IDP-96 For some installations, mapping by Okta ID was not possible.
Identity Service 1.8-279
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
IDP-91 On some installations, login using Okta did not work.
Identity Service 1.7-235
This version of the service brings the following additions and enhancements:
-
The cookie notice on the login page and in the Public Marketplace. Learn more.
-
The support for customer onboarding through the Public Marketplace. Learn more.
Identity Service 1.6-26
The Keycloak version has been updated to 9.0.2 in this version.
Resolved Issues
IDP-52 The IDP APS instance could not be updated.
Identity Service 1.5-23
Identity Service overall performance and stability has been improved in this version. Also, the product name in the IDP log-in form has been renamed to CloudBlue Commerce.
Resolved Issues
IDP-14 A command-line client is missing in some brands.
IDP-22 A brand configuration is not complete after upgrade.
Identity Service 1.4-255
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
IDP-2 More detailed logging is required: login operations, password changes, and user status changes.
Identity Service 1.4-221
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
OA-10919 Impossible to upgrade IDP version to 1.4.197 if approx. 300 brands exists.
Identity Service 1.4-197
Identity Service overall performance, stability, and security has been improved in this version. The Keycloak version has been updated to 8.0.1.
Resolved Issues
OA-10045 Incomplete brand deletion from IDP database blocks re-enabling IDP.
Note: For instructions on how to clean up orphaned brands from the IDP database, refer to this KB article.
Release Notes for Identity Service 1.4-139
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
OA-9936 A user is searched by email address instead of login name during password reset.
Release Notes for Identity Service 1.4-122
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
OA-9812 The IDP database schema differs between clean installation and upgrade.
Release Notes for Identity Service 1.4-104
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
CMP-6959. Unexpected page reload in Native Integrations when an authorization token need to be refreshed.
OA-9590. A user is searched by login name and email address during password reset.
OA-9404. Non-existing scripts are referenced from the IDP login form
Release Notes for Identity Service 1.4-67
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
OA-9106. Brand creation in IDP takes 1.5 minutes
OA-9084. A warning about unrecognized password hash type is required
OA-9147. IDP startup timeout error if more than 200 brands exist
Release Notes for Identity Service 1.4-37
Identity Service overall performance and stability has been improved in this version.
Resolved Issues
OA-8991. Incomplete user migration during IDP enabling.
OA-8749. Impossible to return an OSS user_id in a token.
OA-9001. User authentication by email address must be disabled.
Release Notes for Identity Service 1.3-271
Identity Service stability has been improved in this version. Also, a script to register new IDP clients has been added.
Release Notes for Identity Service 1.3-146
Identity Service overall performance and stability has been improved in this version.
Release Notes for Identity Service 1.2-71
The Identity Service functionality has been extended with the ability of a brand integration with Azure AD.
Now, if a user exists in CloudBlue Commerce and a brand is integrated with Azure AD using the SAML protocol, this user can authenticate through Azure AD.
Resolved Issues
OA-5510
Issue Summary: Impossible to log in to the RCP after changing a password.
Fix Description: The problem when a new password was not applied and an error displayed has been fixed.
OA-5516
Issue Summary: A message is not sent after clicking "Forgot Password" in the RCP login form.
Fix Description: The password reset functionality has been fixed.
OA-3340
Issue Summary: No error message when a user tries to log in to an inappropriate brand.
Fix Description: The proper error message is displayed now in this case.
OA-4420
Issue Summary: A vendor's password policy is used to generate password during account creation.
Fix Description: A reseller's password policy is now applied during account creation in UX1.
Release Notes for Identity Service 1.0
This document introduces a new component – Identity Service – which represents a single point for user authentication. Keycloak (www.keycloak.org) is used as a solution for the Identity Service. The Identity Service is based on micro-service architecture and is not included in the CloudBlue Commerce distribution package. To start using the new Identity Service, you must enable it in the PCP manually. You can always roll back the new Identity Service by disabling it and returning to the previous CloudBlue Commerce mechanism.
The Identity Service provides:
- A single log-in form
- Extended password policies
- Improved password generator and validator
- Two-factor authentication
New Log-in Form
The Identity Service uses a single login form.
Extended Password Policies
Now, password policies are extended and managed by the Identity Service. You can find all the related settings in PCP >> Services > Identity Service > Password Policy.
We recommend that
- Passwords are at least 10 characters in length and have two different types of characters
- Passwords do not have an expiration date
- Passwords are checked against known bad passwords, banned lists and so on
- Passwords are changed only when forgotten
For more information about the default configuration, refer to Password Policy Configuration.
In the upcoming releases, we will restrict using Password Quality Policies which do not meet basic requirements.
Improved Password Generator and Validator
The password generator and validator are better than before and can operate with the reworked password policies.
Two-factor Authentication
A new feature has been added to Identity Service. In addition to an account password, two-factor authentication prompts a user to enter a one-time password, usually from a separate device such as a smartphone. By enabling this feature, you maximize your customers' protection against unauthorized access.
This is a highly effective way to protect your customers because even if a password is stolen, it will not be enough for an intruder to gain access to a system.
For more information about the two-factor authentication configuration, refer to Two-Factor Authentication.