Troubleshooting: Credential Provider Login Fails With 'This Collection Already Contains an Address With Scheme https' Error

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

    Overview

    Users can fail to log in through the SecureAuth Credential Provider when Multiple Site Bindings is enabled in IIS, with the following error in the Credential Provider realm's logs:

    This collection already contains an address with scheme https. There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'.

     

    Cause

    Multiple Site Bindings is enabled in Internet Information Services (IIS) for the site, but the corresponding setting is not enabled in the Credential Provider realm's web.config.

     

    Resolution:

    1. In the Admin Console, open the realm that serves the Credential Provider (SecureAuth998) and go to the System Info tab.
    2. Click Decrypt.
    3. Open File Explorer and browse to D:\SecureAuth\SecureAuth998.
    4. Open web.config in a text editor and search for:
      <serviceHostingEnvironment multipleSiteBindingsEnabled="False"/>
    5. Change False to True:
      <serviceHostingEnvironment multipleSiteBindingsEnabled="True"/>
    6. Save the file and test.

    The same underlying cause can also affect a realm configured for Web Service (Multi-Datastore) -- see Troubleshooting: Multi-Datastore Web Service Realm Issues (Cause 1) if a Multi-Datastore realm is showing this same error.


     

    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.