Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur if the service is configured for security and the client is not using security.
Security policy export failed. The binding contains both a SymmetricSecurityBindingElement and a secure transport binding ...
Security policy export failed. The binding contains both an AsymmetricSecurityBindingElement and a secure transport binding ...
Security policy import failed. The security policy contains supporting token requirements at the operation scope. The contract ...
Security policy is configured using a hierarchy of code groups at every policy level. Default security policy consists of ...
Security processor was unable to find a security header in the message. This might be because the message is an unsecured ...
Security processor was unable to find a security header with actor '{0}' in the message. This might be because the message ...
Security settings for this service require '{0}' Authentication but it is not enabled for the IIS application that hosts ...
Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts ...
Security Support Provider Interface (SSPI) authentication failed. The server may not be running in an account with identity ...