Re: AcceptSecurityContext returning SEC_I_CONTINUE_NEEDED with empty SecBuffer

From: Vishal Mishra [MSFT] (vishalmishra_at_online.microsoft.com)
Date: 04/17/04 

Date: Fri, 16 Apr 2004 16:41:04 -0700

What platform are you seeing this on?

Is there anything in the SECBUFFER_EXTRA buffer? 

-- 
------------------------------------------
Regards,
Vishal Mishra [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"PRR" <anonymous@discussions.microsoft.com> wrote in message 
news:B5FC1A17-E8C8-4DC5-A5BA-3C79DBC028C8@microsoft.com...
> Hello Gurus,
>
> I am encountering a strange problem during the SSL handshake.
>
> Client sends the generated token obtained from the first call to 
> InitializeSecurityContext to the server. Server passes this token to the 
> AcceptSecurityContext, which in turn succesfully generates and 
> communicates the token conatining the cert to the client. The new token 
> the client now generates when given to the AcceptSecurityContext returns 
> SEC_I_CONTINUE_NEEDED  but the ouptut SecBuffer contains empty or null 
> pvBuffer.
>
> I am not sure whatz going on? I donot know what to pass to the client. I 
> am sure the handshake is not yet over. Can somebody please help?
>
> Thanks
> PRR

Relevant Pages

  • Does both authentication parties say SEC_E_OK?
    ... is a bit vague on InitializeSecurityContext and AcceptSecurityContext ... Does both sides (client and server) end with SEC_E_OK until ... I send the generated token to client. ...
    (microsoft.public.platformsdk.security)
  • Re: ImpersonateSecurityContext fails with kerberos
    ... > client thinks the server is running as someone ... running as a service as LocalSystem; and AcceptSecurityContext returns ... something with the authentication data i can specify in the call to ...
    (microsoft.public.platformsdk.security)
  • AcceptSecurityContext returns SEC_E_INVALID_HANDLE
    ... First the client sends af negotiation token to the server. ... The server validates og accepts the token and AcceptSecurityContext ... The server send the AuthenticationContext back to the client. ...
    (microsoft.public.win32.programmer.kernel)
  • AcceptSecurityContext returns SEC_E_INVALID_HANDLE
    ... First the client sends af negotiation token to the server. ... The server validates og accepts the token and AcceptSecurityContext ... The server send the AuthenticationContext back to the client. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: SSL and a CA
    ... Description of the Server Authentication Process During the SSL Handshake ... ensure client has the CA root installed ...
    (microsoft.public.inetserver.iis.security)