SugarIdentity Release Notes
This document describes any new features, enhancements to existing features, fixed issues, and known issues for the 8.0 release of SugarIdentity on January 25, 2022. Please refer to the SugarIdentity Archived Release Notes page for previous releases. For more information on accessing and using the SugarIdentity service, refer to the SugarIdentity Guide. For information on supported platforms, refer to the SugarCloud Services Supported Platforms page.
Note: Only some SugarCloud instances use SugarIdentity. Refer to the SugarIdentity Guide to determine if yours is configured to do so. Existing customers will be notified before their instances begin using the service.
The following feature enhancement is included in the 8.0 release of SugarIdentity:
- User license assignment in SugarCloud Settings console: For certain SugarIdentity-enabled instances, administrators can manage the License Type field in the SugarCloud Settings console to assign licenses to users. The ability to manage user licenses in the SugarCloud Settings console will be rolled out to all SugarCloud customers over the course of this year.
The following issue has been resolved in the 8.0 release of SugarIdentity. Case portal users can use the following links for more details:
- 88711: A validation check is not performed on the Email field during the user import process causing invalid email addresses to be entered in the user's record potentially.
The following issue identified in the Sugar application has been resolved in the 11.3.0 release of Sugar. Case portal users can use the following links for more details:
- 87960: For Sugar versions 11.1.0 and higher, having the Administration page open in Sugar when initiating the impersonation session in SugarCloud Settings may cause the impersonation to fail with an error.
The following known issue is present in the 8.0 release of SugarIdentity. Case Portal users can use the following links for more details:
- 84844: More active users can be added in SugarIdentity than is allowed by the instance's license limit causing a mismatch between SugarIdentity and Sugar. As a workaround, create the user with an Inactive status so that it syncs to the Sugar application, then make the necessary adjustments to the license types or statuses in Sugar to activate the new user and stay within the license limit.
The following issues identified in the Sugar application may affect instances using SugarIdentity. Case Portal users can use the following links for more details:
- 87908: The Reset Multi-Factor Auth option improperly appears during a user impersonation session.
- 87698: For Sugar versions 11.1.0 and higher, if an admin impersonates a user and the access token expires, the admin user improperly begins to impersonate their own Sugar account once the user's impersonation session ends.
Last modified: 2022-01-25 17:07:43