Collapse the table of content
Expand the table of content

SpAcceptLsaModeContext function

Server dispatch function used to create a security context shared by a server and client.

The SpAcceptLsaModeContext function is called when the server calls the AcceptSecurityContext (General) function of the Security Support Provider Interface.


NTSTATUS SpAcceptLsaModeContext(
  _In_  LSA_SEC_HANDLE  CredentialHandle,
  _In_  LSA_SEC_HANDLE  ContextHandle,
  _In_  PSecBufferDesc  InputBuffer,
  _In_  ULONG           ContextRequirements,
  _In_  ULONG           TargetDataRep,
  _Out_ PLSA_SEC_HANDLE NewContextHandle,
  _Out_ PSecBufferDesc  OutputBuffer,
  _Out_ PULONG          ContextAttributes,
  _Out_ PTimeStamp      ExpirationTime,
  _Out_ PBOOLEAN        MappedContext,
  _Out_ PSecBuffer      ContextData


CredentialHandle [in]

Optional. Handle to the credentials to use for the context.

ContextHandle [in]

Optional. Handle to the current context.

InputBuffer [in]

Pointer to a SecBufferDesc structure containing information from the client.

ContextRequirements [in]

Flags indicating the context requirements. The following table lists the valid values.


The server is allowed to impersonate the client.


Both the client and the server are required to prove their identity.


The security context will support the detection of replayed packets.


The security context will support the detection of out-of-order messages.


A new session key must be negotiated.


If the client is an interactive user, the package must, if possible, prompt the user for the appropriate credentials.


The input buffer contains package-specific credential information which should be used to authenticate the connection.


The package must allocate memory. The caller must eventually call the FreeContextBuffer function to free memory allocated by the security package.


The caller expects a three-leg mutual authentication transaction.


A datagram-type communications channel should be used. For more information, see Datagram Contexts.


A connection-type communications channel should be used. For more information see Connection-Oriented Contexts.


If the context fails, generate an error reply message to send back to the client.


A stream-type communications channel should be used. For more information, see Stream Contexts.


Buffer integrity can be verified; however, replayed and out-of-sequence messages will not be detected.


TargetDataRep [in]

Flag indicating the data representation, such as byte ordering, to use. Contains SECURITY_NATIVE_DREP or SECURITY_NETWORK_DREP.

NewContextHandle [out]

Pointer to an LSA_SEC_HANDLE. On the first call to AcceptSecurityContext, this pointer receives the new context handle. On subsequent calls, NewContextHandle can be the same as the handle specified in the ContextHandle parameter.

OutputBuffer [out]

Pointer to a SecBufferDesc structure that receives information to be sent to the client.

ContextAttributes [out]

Pointer to flags specifying the context attributes that the server supports. For a list of valid values, see the ContextRequirements parameter.

ExpirationTime [out]

Pointer to a TimeStamp that receives the expiration time for the context.

MappedContext [out]

Pointer to a Boolean value. Set MappedContext to TRUE if the security package implements the user-mode SSP/AP functions.

ContextData [out]

Optional. Pointer to a SecBuffer structure that receives context-specific data to copy when creating the user-mode security context. Memory for ContextData must be allocated using the AllocateLsaHeap function. The Local Security Authority (LSA) will free the memory.

Return value

If the SpAcceptLsaModeContext function succeeds and no more processing is required to establish the security context, return STATUS_SUCCESS. If additional processing is required, the function should return SEC_I_CONTINUE_NEEDED.

If the function fails to create the security context for any other reason, return an NTSTATUS code indicating the reason.


SpInitLsaModeContext is the client-side function for creating a security context.

SSP/APs must implement the SpAcceptLsaModeContext function. The actual name given to the implementation is up to the developer.

A pointer to the SpAcceptLsaModeContext function is available in the SECPKG_FUNCTION_TABLE structure received from the SpLsaModeInitialize function.


Minimum supported client

Windows XP [desktop apps only]

Minimum supported server

Windows Server 2003 [desktop apps only]



See also




Community Additions

© 2015 Microsoft