Not able to log in via "Admin Console"

Follow
    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • Issue: When trying to log into the Admin Console from your browser, you get the following page:

    There are multiple issues for this cause.  One of the more common reasons is because the proper bindings are not set in IIS.  

    Solution: Go to your IIS manager console, Start Page-->IDP-->Sites-->Default Web Site.  On the right side of the screen go to "Bindings"

    There should be three bindings on this page.  One for net.tcp, which is the transport security protocol, second for the http, which is the required 80 port, and a third for https, which is the required 443 port.  If you are missing one of these three bindings, add the missing binding with the "Add..." button.  For the "type" dropdown menu select which one you are missing(http,https,net.tcp).  Leave the host name blank and make sure the proper port number is entered for the desired binding.  The IP address can be left unassigned.  If you follow these steps, your bindings should look like the picture above.  Go ahead and try to see if this fixes your issue, if not, you can at least eliminate binding as your problem for this issue.  

     

     

    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.