Re: Schannel client authentication problem with optional client certificate

On nov. 19, 17:15, DaveMo <david.mow...@xxxxxxxxx> wrote:

From MSDN: InitializeSecurityContext

ISC_REQ_USE_SUPPLIED_CREDS
 Schannel must not attempt to supply credentials for the client
automatically.

HTH,
Dave

Thanks for the help, it solved my problem!
(It seems I was to tired today, when I read the docs :) )
.

Relevant Pages

  • Re: Enabling "DCOM Callback"
    ... I might take a look at the MSDN sample at some point. ... server object class is not creatable on the client. ... Default Authentication Level: Connect ...
    (microsoft.public.win32.programmer.ole)
  • Re: Extra Round trip while using SSPI Api.
    ... your setspn output implies that there is no SPN associated with your ... InitializeSecurityContext() is domain\hostname.One more point here is ... and the client selects the wrong domain. ... Setup consists of a client and a server, ...
    (microsoft.public.win32.programmer.kernel)
  • New Bug in AcceptSecurityContext in Kerberos SSPI?
    ... passed in, SSPI returns SEC_I_CONTINUE_NEEDED. ... AcquireCredentialsHandle (client side) - SEC_E_OK ... InitializeSecurityContext - SEC_E_WRONG_PRINCIPAL ...
    (microsoft.public.platformsdk.security)
  • Re: 70-305 question
    ... but according to mentioned MSDN link: ... cacheable by clients and shared caches. ... because according to books I read "Any" means absolutly all - client, ... AND host server - I do not see host server option in MSDN article for ...
    (microsoft.public.cert.exam.mcsd)
  • RE: InitializeSecurityContext () throws SEC_E_WRONG_PRINCIPLE.
    ... Subject: InitializeSecurityContext throws SEC_E_WRONG_PRINCIPLE. ... We are facing very strange issues on some of our installations. ... 3)Kerberos is used for authenticating the client with the server. ...
    (comp.protocols.kerberos)
Quantcast