Unable to access WS-Trust metadata / MEX endpoint

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

    Description:  

    Unable to access WS-Trust metadata / MEX endpoint.

    Error Message: The authentication schemes configured on the host ('Anonymous') do not allow those configured on the binding 'CustomBinding' ('Negotiate'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this application through the IIS management tool, through the ServiceHost.Authentication.AuthenticationSchemes property, in the application configuration file at the <serviceAuthenticationManager> element, by updating the ClientCredentialType property on the binding, or by adjusting the AuthenticationScheme property on the HttpTransportBindingElement.

    Cause:  

    The problem occurs due to Windows Authentication set to False in D:\SecureAuth\SecureAuthXX\webservice\web.config file.

    Resolution:  

    Take a backup of D:\SecureAuth\SecureAuthXX\webservice\web.config file and update the content as mentioned below:

    <?xml version="1.0" encoding="UTF-8"?>
    <configuration>
    <location path="WSTrust.svc">
    <system.webServer>
    <security>
    <authentication>
    <anonymousAuthentication enabled="true" />
    <windowsAuthentication enabled="true" />
    </authentication>
    </security>
    </system.webServer>
    </location>
    </configuration>

    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.