The wsdl schema that was used to create this configuration file contained a 'RequireIssuerSerialReference' assertion for a X509Token. This can not be represented in configuration, you will need to programatically adjust the appropriate X509SecurityTokenParameters.X509KeyIdentifierClauseType to X509KeyIdentifierClauseType.IssuerSerial. The default of X509KeyIdentifierClauseType.Thumbprint will be used, which may cause interop issues.
The WSDL binding named {0} is not valid because no match for operation {1} was found in the corresponding portType definition. ...
The wsdl operation input {0} in portType {1} does not reference a message. This is either because the message attribute is ...
The wsdl operation output {0} in portType {1} does not reference a message. This is either because the message attribute ...
The wsdl operation {0} in portType {1} contains a fault that does not reference a message. This is either because the message ...
The wsdl schema that was used to create this configuration file contained a 'RequireIssuerSerialReference' assertion for ...
The wsdl:binding element in a DESCRIPTION MUST be constructed so that its soapbind:binding child element specifies the transport ...
The WSHttpBinding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported ...
The wsrm:{0} request message's wsa:ReplyTo address containing a URI which is not equivalent to the remote address. This is ...
The X.509 certificate ({0}) usage time is invalid. The usage time '{1}' does not fall between NotBefore time '{2}' and NotAfter ...