Version Affected: 9.2 - 19.07.01
The provided anti-forgery token was meant for user "", but the current user is "Username"
Browsing to the realm using an IP address or NETBIOS name, particularly when redirected via a Service Provider in an SPInit integration.
In order to work correctly the anti-forgery logic requires that the IdP realm should be reached via a FQDN (Fully Qualified Domain Name) not IP address or NETBIOS.
Check that the Service Provider is not redirecting users back using IP address or NETBIOS name.
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.