Release Date
8th April 2020
Purpose
This is a minor maintenance release that carries a number of fixes and minor enhancements, mainly to the Microsoft Online Services components.
Features
REF |
Description |
|
This release contains a fix for the 12.6.3 release. |
Fixes
REF |
Type |
Description |
1416 |
Defect
|
Exchange online management features fail when Security Defaults are enabled Atria uses a different method to authenticate with Exchange Online, following new best security practices. As part of this the AtriaAdmin user is no longer required, and additional partner center connection setup is required. |
1434 |
Defect
|
Resetting Federated users password causes request to fail When a user has an ADFS federated account then changing passwords through Atria fails. It is not possible to reset a password in Azure when a user is federated. Necessary changes have been made to the code to handle the case. Atria now checks the UPN domain and then decides whether or not it should attempt to reset the password in Azure. |
1418 |
Enhancement |
Additional logging around Immutable ID To make immutable ID more traceable, additional logging has been added around immutable ID to shed a light on when and why user has changed. |
1419 |
Defect |
Immutable ID issue This error occurred in some environments where the ADFS user could not be put in the onmicrosoft.com domain to be edited. We have removed the need for these users to be put in the onmicrosoft.com domain while making changes, resulting in this error to be resolved. |
1410 |
Defect |
Index Out of Bounds issue for email addresses without @ symbol Email addresses without @ symbol in it causes sync failure. Sync process has been improved to handle and manage address without @ symbol. |
1438 |
Defect |
Sync All failure due to type conversion Error occurs and provisioning request fails when sync all kicks off. Sync process has changed to handle MsGraphAccessToken type change. Code has changed to get graph access token in a different way. |
Deployment/Update Checklist
The following Atria components need to be updated, follow the recommended order of update.
Components to deploy:
Step |
Component |
Command line |
Service |
Completed |
1 |
AtriaDatabase 12.6.4.66 |
Choco upgrade atriadatabase |
Platform |
|
2 |
AtriaWeb 12.6.4.96 |
Choco upgrade atriaweb |
Platform |
|
3 |
AtriaAzureAD 12.6.4.96 |
Choco upgrade atriaazuread |
Azure AD |
|
4 |
AtriaMSOL 12.6.4.96 |
Choco upgrade atriamsol |
MSOL |
|
5 |
AtriaMsolWS 12.6.4.96 |
Choco upgrade atriamsolws |
MSOL |
|
6 |
AtriaProvisioning 12.6.4.96 |
Choco upgrade atriaprovisioning |
Platform |
|
Note: ensure the correct order is followed and that Azure AD is updated before Microsoft Online.
Recent Comments