SecureAuth IdP Version affected: All
Description: Users cannot login - after MFA, they are returned to the login screen and the process starts again. Sometimes Users can login, especially if they move through the login process very quickly.
Cause: Filesync 4.x needs the Service running on the Primary and Secondary servers. If not, the Manifest file gets out of date and this causes the web.config to appear to be newer on the secondary servers. This causes filesync to keep copying the web.config from the primary to secondary every minute.
The end result is anyone who is attempting to login when the web.config is copied again, will have their session terminated and the login process will start again.
1. Login to the Primary Server.
2. Open Services.msc
3. Set the SecureAuth Filesync Service to Automatic start type
4. Start the SecureAuth Filesync Service.
5. Make sure the Manifest file now updates
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.