Troubleshooting: Login Fails with CloudMembershipManager.GetUser DeadlineExceeded Error (Stale Connector Config)

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All (Cloud only)
     
     

    Overview

    A user with a valid user ID fails to log in to a realm. The Debug log shows an entry similar to:

    Message="CloudMembershipManager.GetUser exception: Status(StatusCode=DeadlineExceeded, Detail="Deadline Exceeded")"

     

    Cause

    The SecureAuth Connector does not have a current, correct configuration. If the Connector was not installed, not running, or otherwise unreachable at the time the Datastore was created or updated, it never received that Datastore's latest configuration.

     

    Resolution:

    To resolve this:

    1. Confirm the Connector service is running.
    2. In the Admin Console, re-type the password for each Datastore. This forces the configuration down to the Connector.
    3. Confirm the Connector's configuration actually updated by checking the modified date on C:\Program Files\SecureAuth Corporation\SecureAuth Connector\SecureAuth.Agent.Service.exe.Config.
    4. If it still hasn't updated, check for errors in C:\ProgramData\SecureAuth Corporation\SecureAuth Connector\logs.
    5. If the configuration has updated but the user still cannot log in, check the same log location for details on why the user lookup is failing.


     

    Special Considerations

    The default permissions on C:\Program Files\SecureAuth Corporation\SecureAuth Connector\ have been seen changed in the field, removing the Modify permission required by Network Service. This also prevents the configuration file from updating, with the same symptoms as above.


     

    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

    Comments

    0 comments

    Please sign in to leave a comment.