Auth2ECDSAP384CAName: %1!s! Auth2ECDSAP384CertMapping: %2!s! Auth2ECDSAP384CertType: %3!s! Auth2ECDSAP384HealthCert: %4!s!
Auth1ECDSAP384CAName: %1!s! Auth1ECDSAP384CertMapping: %2!s! Auth1ECDSAP384ExcludeCAName: %3!s! Auth1ECDSAP384CertType: %4!s! ...
auth1ecdsap384healthcert=yes|no (default=no) auth2=computercert|computercertecdsap256|computercertecdsap384| userkerb|us ...
auth2ecdsap256ca=" certmapping:yes|no catype:root|intermediate (default=root) certhash: followrenewal:yes|no (default=no) ...
Auth2ECDSAP256CAName: %1!s! Auth2ECDSAP256CertMapping: %2!s! Auth2ECDSAP256CertType: %3!s! Auth2ECDSAP256HealthCert: %4!s! ...
Auth2ECDSAP384CAName: %1!s! Auth2ECDSAP384CertMapping: %2!s! Auth2ECDSAP384CertType: %3!s! Auth2ECDSAP384HealthCert: %4!s! ...
Authenticate messages if authentication level for calls (on Security Property Page) is not NONE. This is Windows 2000 behavior. ...
Authentication failed because the client can't support any of the authentication protocol versions received from the server. ...
Authentication failed because the client found that a stronger authentication protocol is available. Try connecting again. ...
Authentication failed because the server is requesting the client's real identity, but the client can only provide a pseudonym. ...