asp.net - Windows authentication - Kerberos or NTLM (Negotiate oYICO...) -


i have problems single user in intranet application. client side wpf application communicates asp.net web api web service.

the client sends https , post requests using

httpclienthandler handler = new httpclienthandler() {   automaticdecompression = decompressionmethods.deflate | decompressionmethods.gzip,   usedefaultcredentials = true,   preauthenticate = true }; 

on iis windows authentication enabled ntlm , negotiate providers.

the system works users except 1 gets 401.1 post requests.

i'm currenty trying figure out what's different user. thing noticed different kind of authorization header.

from here (and many other resources) read:

if header starts "t" (example: http: authorization = negotiate tlrmtvntu...) you're using ntlm. if starts "y" (example: authorization: negotiate yiiljgygkwyb...) you're using kerberos.

i can see headers working requests seems use kerberos:

authorization: negotiate yiit4qygkwybbqucoiit1tcc... 

the header sent user fails post looks like

authorization: negotiate oyicotccajwgawobaakcahg... 

it starts o. so ntlm or kerberos? authentication fails post request, succeeds on get!

why don't use wireshark that?

wireshark inspect traffic. break down ticket asn.1 displayable tree structure. you'll see mechanism used in case. additionally, you'll see kerberos traffic, e.g., tgs-req.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -