Aurora Multi-Tenant Console fixed issues

When managing multiple tenants and switching from one to another, the console cannot load any device information for the other tenant because the token was not valid. (EPCL-5914)

The “Monitor installed applications” option was not available in the linked policy template. (MSSP-7652)

The quarantine and safe lists were limited to displaying a maximum of 100 records. (MSSP-7627)

When provisioning more than 100 tenants at once using the Aurora Multi-Tenant Console API, only some of the tenants were successfully created and the rest were stuck in the retry state. (MSSP-7512)

If you tried to create a policy template with a name that contained only spaces, a "400 - Bad Request" error message appeared. (MSSP-7490)

The list of device policy templates did not display even though the user had the "View policy template list" permission enabled. (MSSP-7489)

Email notifications were not sent to tenants that were unlinked from the linked policy template. (MSSP-7459)

When saving a policy template, if a memory protection exclusion used backslashes (\) with wild cards (*), the template wasn’t saved. (MSSP-7417)

When a user clicked the link in the activation email to set up their account, the login page loaded momentarily before they were redirected to a "Reset Your Password" screen where they needed to set their password. (MSSP-7384)

In the Tenant Conversion tab, if you searched for a tenant with accent marks in the name, no search results were returned. (MSSP-7135)

If a partner user was assigned a custom role that did not have Roles permission and tried to edit a user, the input fields did not load, and a spinner spun indefinitely beside each field. (MSSP-7024)

When you edit a tenant's name in the Aurora Multi-Tenant Console, you could not save your changes. (MSSP-6584)

When importing a file for external device exclusion to an existing linked policy template, an error message was displayed. (EPCL-1632)