Intranet Zone , then Ntielm will be attempted. My question is, is there a way to signal to the server that NTLM should not be sent? I currently handle this by keeping a track of the request in session, and if an NTLM message is received, this disables Kerberos and WWW-authentication for the remainder session session. Initial I think it is possible to respond to authenticity: {Base64 NTLMSSP} header sent by the customer to the header But I suspect that only you will get
WWW-certify
header only conversations
Specifies. It can not say anything else, like "NTLM not" 401 Unauthorized
and another conversation
header, which may include a reaction token, possibly a supported microsoft
which only specify Kerberos. "unauthorized"
, because it was falling back to NTLM in the first place.
Comments
Post a Comment