Resolved issues

1246098: Previously, the session revocation process for cloud-managed applications like Microsoft 365 did not work properly using Object GUID. When a device became non-compliant and the revocation by User Principal Name (UPN) failed, the system also failed to revoke the session by Object GUID. This issue has been fixed.

1295668: Previously, the location was not displayed accurately in the Push notifications of Access Reports and in the Geolocation data in Dashboard. This issue is now fixed.

CN-20180: Previously, 'Mobileiron Core' and 'MobileIron UEM' were displayed in the Ivanti Access administrative portal. This issue is now fixed and rebranding is complete.

CN-20203: Previously, after adding IP addresses to the Advanced Network Rule in Ivanti Access conditional policy, 404 errors were displayed while accessing the sites in the environment. This issue is now fixed.

CN-20159: Support to update Sentry version to 9.17.0 and 9.18.0 in the Ivanti Access portal is available. Previously, this was not available.

CN-18090: Session Revocation Service (SRS) does not fail for GCCH Office 365 accounts when users are part of Azure Active Directory and when the users are not part of Azure Active Directory. Previously, the SRS used to fail as UEM could not send custom attributes for Azure Active Directory users back to Ivanti Access. For more information, see https://microsoft.com

CN-20039: Previously, Access failed to accept domain name with more than six letters in the email. This issue is now fixed.

CN-20010: Previously, the Assertion Consumer Service URL required to be well formed and start with https while uploading the mextadata.xml. This issue is now fixed.

CN-19817: Support to update Sentry version in Access portal to 9.16.0.

CN-19765: Previously, the Assertion Consumer Service URL required to be well formed and start with https while uploading the mextadata.xml.
This issue is now fixed.

CN-19785: Previously on Windows, uninstalling the Authenticator application removed the entire Registry entries instead of removing only the Authenticator specific registry entries.
This issue is now fixed.