Security Support Provider Interface (SSPI) authentication failed. The server may not be running in an account with identity '{0}'. If the server is running in a service account (Network Service for example), specify the account's ServicePrincipalName as the identity in the EndpointAddress for the server. If the server is running in a user account, specify the account's UserPrincipalName as the identity in the EndpointAddress for the server.
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 ...
Security transparent code should not be responsible for verifying the security of an operation, and therefore should not ...
Security transparent code should not be responsible for verifying the security of an operation, and therefore should not ...
Security transparent method {0} calls {1} which is in non-APTCA assembly {2}. Non-APTCA assemblies have implicit LinkDemands ...
Security transparent method {0} satisfies a LinkDemand for {2} on method {1}. {0} should become critical or safe-critical ...