Initializing ClientContext while impersonating about nsspi HOT 3 CLOSED

The problem was the InitIdentify flag. I'm not sure what exact purpose should that flag serve, but I noticed in the code (https://github.com/antiduh/nsspi/blob/master/NSspi/Contexts/ContextAttrib.cs#L119) that the enum has the same value as AcceptIntegrity. Since this was for client-side token initialization I just assumed that AcceptIntegrity was shadowing it, so I removed InitIdentify and used InitIntegrity instead and it worked.

Could you maybe explain (or point me to something) why are there "aliases" for the same value and what do the Identify ones mean ?

from nsspi.

What is the reply back from the KDC? Run a network trace on your server and watch the Kerberosv5 traffic between your server and the KDC. Is there any unexpected answer back from the KDC?

from nsspi.

Hi @valorl - that enumeration is an aggregation of the flags that can be sent to SSPI functions AcceptSecurityContext and InitializeSecurityContext.

Take a look at the documentation about the flags that can be sent.

from nsspi.