Issues signing into realm. Several attempts required.

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All


    Several strange issues can occur when signing into a Realm.  For example, the Submit button appears to do nothing for but hitting it several times works.

    Or, after selecting a second factor method, you end up back at the Username prompt again. 



    Incorrect AppPool Worker process settings means the Session cookie doesn't always match the worker process so the login attempt has to start again. 



    1. Open IIS

    2. Navigate to the AppPool section

    3. Open up the AppPool (Normally .Net 4.5)  Advanced Settings

    4. Make sure the Maximum Worker Processes is set to 1



    Special Considerations:  

    If you wish to spread the load across more CPU, instead of increasing the Max Worker Processes, simply add an extra AppPool and move some of your realms to that AppPool. Just make sure the settings are exactly the same.



    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.

    0 out of 0 found this helpful



    Please sign in to leave a comment.