Release Notes
25 October 2022, 09:20
These release notes provide information about the changes, enhancements, and known or resolved issues of Active Roles 7.6.2. For the most recent documents and product information, and for the release notes and documentation of earlier product releases, see the online Active Roles technical documentation on the One Identity Support Portal.
Active Roles 7.6.2 is a patch release resolving a potential breaking change in the Active Roles Console, related to the Exchange Web Services mail settings and caused by the deprecation of Microsoft Basic authentication, effective from 2023. For more information, see Enhancements.
For more information on the enhancements, see Enhancements.
For more information on the list of resolved issues, see Resolved issues.
For more information on the list of known issues, see Known issues.
The following is a list of enhancements implemented in Active Roles 7.6.2.
| Enhancement | Issue ID |
|---|---|
|
In preparation to the deprecation of Microsoft Exchange Online Basic authentication, the Exchange Web Services mail settings in the Active Roles Console now support Modern authentication. The affected settings are located in the following locations:
NOTE: Although Basic authentication is deprecated effective from 2023, the Exchange Web Services mail settings of the Active Roles Console will continue supporting Basic authentication for on-premises Exchange Servers. |
323131 |
The following is a list of issues addressed in this release.
|
Resolved issue |
Issue ID |
|---|---|
|
Previously, when adding Azure object types, for example, Azure user objects to the Owners list of an Azure distribution group or security group, or adding Azure user objects to the Send as list of a shared mailbox, then reopening the properties of the distribution group, security group or shared mailbox, the Owners of these groups or the objects that were added to the Send as list of a shared mailbox disappeared on the Active Roles Web Interface. The cause of this issue was that the cache-updating mechanism did not work properly, and the Web Interface could not detect Azure objects that had been previously set. However, when checking the settings on the Microsoft Azure portal or the Microsoft 365 admin center, they were properly set. The issue is resolved by implementing cache updates when they are necessary, so now Azure object types set as Owners or granted the Send as permission are always displayed correctly in the Web Interface. |
358491 |
|
Previously, when adding Azure hybrid user objects to the Owners list or adding them to the Send on behalf list of a distribution group, then reopening the Owners or Send on behalf list, the added user objects were not displayed, and after clicking Save, they were removed from these lists. The issue is resolved: adding hybrid Azure user objects to the Owners or Send on behalf lists works properly. |
384473 |
|
Previously, when attempting to change the owner or the members of an on-premises synced Azure distribution or security group, the following error message did not appear in case of modifying security groups: Error. Can't execute custom entry method Get_AzureO365GroupManagedBy due following error: "Exception type 'ActiveRoles.Web.ScriptServices.ScriptServiceException' was thrown." This error message must appear because security and distribution groups can only be changed in an on-premises environment. However, in case of modifying a security group, instead of the error message, the Operation was successfully completed message appeared, which was misleading, as the operation was not successful. The issue is resolved: when modifying a security group in a cloud environment, the error message appears as expected. |
384447 |
|
Previously, in the list of Azure Users, Azure user and group objects synced from an on-premises environment did not appear. Specifically, the list of Azure Users was populated from the cache, which filtered out on-premises users, but when selecting the owner of an Azure distribution or security group, the Select Object from Azure list was populated using a direct Graph API call, and so it contained both on-premises and Azure cloud users. Due to this caching issue, setting an on-premises user as the owner of an on-premises synced Azure distribution or security group appeared to be successful in the Microsoft 365 admin center, but in the Web Interface, in Distribution Group Properties or Security Group Properties, opening the list of Owners did not display the on-premises user set as owner, clicking Save modified the list from the cache, and the Web Interface removed the owner. The issue is resolved: the Web Interface now loads on-premises users from the cache and so both on-premises and cloud users appear correctly in the list of Azure Users and Owners. |
384446 |
|
Previously, creating a customized Web Interface configuration in Active Roles 7.5.3, then upgrading to Active Roles 7.6.2 and importing the custom Web Interface configuration caused the following IIS error message to appear: Index was outside the bounds of the array. The issue is fixed and now the customized Active Roles Web Interface loads successfully. |
325484 |
|
Previously, in the WebAdmin or ARWebHelpDesk site, if Active Directory > <domain name> > users > <user name> > Reset Password > Customize > Password > Edit > Read only was enabled, resetting the password of an Active Directory user and clicking Finish did not prompt an error message to appear. The issue is fixed and now if Read only is enabled for Password, clicking Finish in the reset password form prompts the following error message to appear: Administrative Policy returned an error. Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. (Exception from HRESULT: 0x8007052D) |
288131 |
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
