Re: AcquireCredentialsHandle direction
From: Alun Jones [MSFT] (alunj_at_online.microsoft.com)
Date: 01/28/05
- Next message: Alun Jones [MSFT]: "Re: InitializeSecurityContext() returns SEC_E_INVALID_TOKEN on first c"
- Previous message: OShah: "Re: SE_DACL_AUTO_INHERITED and Security Descriptor Control Flags"
- In reply to: sherry: "AcquireCredentialsHandle direction"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 28 Jan 2005 11:34:38 -0800
Simple - acquire two credential handles, one with INBOUND, and the other
with OUTBOUND - use one handle when acting as an SSL client, and the other
handle when acting as an SSL server.
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:69807B87-338F-4368-922D-A9550E128B5D@microsoft.com... > When I call AcquireCredentialsHandle() I could specify > fCredentialUse be Inbound, Outbound or Both. > > If I want to use the same credential for both outbound(client) and > inbound(server). But in MSDN it says: > SECPKG_CRED_BOTH - Validate an incoming credential or use a local > credential to prepare an outgoing token. This flag enables both other > flags. > This flag is not valid with the Digest and Schannel SSPs. > > I'm using Schannel SSP. what should I use in this case? > > Thanks, > > Sherry
- Next message: Alun Jones [MSFT]: "Re: InitializeSecurityContext() returns SEC_E_INVALID_TOKEN on first c"
- Previous message: OShah: "Re: SE_DACL_AUTO_INHERITED and Security Descriptor Control Flags"
- In reply to: sherry: "AcquireCredentialsHandle direction"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
