Re: InitializeSecurityContext() returns SEC_E_INVALID_TOKEN on first c
From: Alun Jones [MSFT] (alunj_at_online.microsoft.com)
Date: 01/28/05
- Next message: engp5567_at_yahoo.com: "How to use CertDuplicateCertificateContext and CertFreeCertificateContext"
- Previous message: Alun Jones [MSFT]: "Re: AcquireCredentialsHandle direction"
- In reply to: sherry: "InitializeSecurityContext() returns SEC_E_INVALID_TOKEN on first c"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 28 Jan 2005 11:37:55 -0800
What value are you passing as the pInput parameter? On the first call, it
should be NULL.
Perhaps you could post a small code snippet.
Alun.
~~~~
-- Software Design Engineer, Internet Information Server (FTP) This posting is provided "AS IS" with no warranties, and confers no rights. "sherry" <yangcooper@hotmail.com> wrote in message news:D4E3E5B2-1EB8-408D-8066-1B6CA0CFBFCB@microsoft.com... > Based on the InitializeSecurityContext, the first time hContext is passed > at > NULL, it should return a token in newhContext to be used for future > InitializeSecurityContext calls. > > The description in MSDN says: > SEC_E_INVALID_TOKEN The error is due to a malformed input token, such as a > token corrupted in transit, a token of incorrect size, or a token passed > into > the wrong security package. Passing a token to the wrong package can > happen > if the client and server did not negotiate the proper security package. > > I have not even got a token yet when I first time calls it. > > Any other possibility here? > > Thanks, > > Sherry
- Next message: engp5567_at_yahoo.com: "How to use CertDuplicateCertificateContext and CertFreeCertificateContext"
- Previous message: Alun Jones [MSFT]: "Re: AcquireCredentialsHandle direction"
- In reply to: sherry: "InitializeSecurityContext() returns SEC_E_INVALID_TOKEN on first c"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|