Troubleshooting: 404 Error During URL Enrollment (Vanity URL or Alias)

Version Affected: All
 
 

Overview

When a user tries to use URL enrollment in the Authenticate app or the Passcode app, enrollment can fail with a 404 - File or directory not found error.

Cause

The Authenticate app and the Passcode app are hardcoded to add SecureAuth998 to the end of the fully qualified domain name (FQDN) whenever the URL entered doesn't already include a SecureAuth realm number. This happens whenever a vanity URL or alias is used for the realm instead of its FQDN.

For example, if a user types a vanity URL or alias instead of the FQDN, the app tries to redirect to https://<FQDN>/Enroll/SecureAuth998 -- which 404s if that realm number doesn't exist at that address.

Resolution:

Do not use the alias or vanity URL for URL enrollment -- have users type the realm's actual FQDN instead. This redirects to SecureAuth998, which is set to use URL enrollment by default.
 
 

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.