Version Affected: All
After an Authentication for something like a SAML realm, the user would reach the Authorized page which will either promptly have them land on a 404 error or throw the error while sending them back to the beginning of Authentication on the SecureAuth.aspx page.
This is caused by the Token not being valid immediately after hitting the Authorized page.
1. Go to Admin Console > Admin Realm > SecureAuth# > Workflow > Custom Identity Consumer > Token Settings.
2. Check to see if the Domain section is filled out under the Forms Authentication section.
3. If it is filled out with anything other than the company domain, remove it. A good test would be to just try removing it anyways to see if it could be issue. It will likely not break the integration if removed as it is a restriction on the token.
This settings forces to token to only be allowed to be used by pages that contain the domain name. If it were set to the wrong domain or the application name, it would not be usable by SecureAuth after Authentication.
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.