Troubleshooting: Saving a Realm Fails With 'An Error in the Authentication Has Occurred' in the Admin Console – SecureAuth Support

Version Affected: All

Overview

Saving a realm in the Admin Console -- even without making any actual changes to it -- can fail with the following error:

An error in the authentication has occurred. Please Try Again. If the error persists, please contact your administrator.

A browser showing the WebAdminUI.aspx page with the error 'An error in the authentication has occurred. Please Try Again. If the error persists, please contact your Administrator.'

Cause

The realm's folder is missing the correct permissions for IIS AppPool\SecureAuth0Pool -- the identity SecureAuth0 (the admin realm) uses to make changes to other realms.

Resolution:

Add IIS AppPool\SecureAuth0Pool back to the affected realm's folder permissions, using either of the following methods.

Automatically, using the Reset File Perms and Shares tool:

Follow Using the Reset File Permissions and Shares Tool to run the tool against the affected realm.

The Reset File Permissions and Shares Tool's opening legal terms screen in an administrator command prompt.

Manually, using IIS:

In IIS Manager on the IdP server, right-click the affected realm and select Edit Permissions.

Right-clicking a realm in IIS Manager, showing Edit Permissions in the context menu.

Go to the Security tab and click Edit.
Click Add, change the location to the local appliance, and enter the object name IIS AppPool\SecureAuth0Pool.
Click Check Names to confirm it resolves, then click OK.
Confirm SecureAuth0Pool has Write and Modify permissions allowed, then click OK to save.

$The realm folder's Security tab and the Select Users or Groups dialog, adding IIS AppPool\SecureAuth0Pool as an object name.$

After either method, saving the realm in the Admin Console should succeed.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.