AcceptSecurityContext (Negotiate) function
The AcceptSecurityContext (Negotiate) function enables the server component of a transport application to establish a security context between the server and a remote client. The remote client uses the InitializeSecurityContext (Negotiate) function to start the process of establishing a security context. The server can require one or more reply tokens from the remote client to complete establishing the security context.
SECURITY_STATUS SEC_Entry AcceptSecurityContext( _In_opt_ PCredHandle phCredential, _Inout_opt_ PCtxtHandle phContext, _In_opt_ PSecBufferDesc pInput, _In_ ULONG fContextReq, _In_ ULONG TargetDataRep, _Inout_opt_ PCtxtHandle phNewContext, _Inout_opt_ PSecBufferDesc pOutput, _Out_ PULONG pfContextAttr, _Out_opt_ PTimeStamp ptsTimeStamp );
A handle to the credentials of the server. The server calls the AcquireCredentialsHandle (Negotiate) function with either the SECPKG_CRED_INBOUND or SECPKG_CRED_BOTH flag set to retrieve this handle.
[in, out, optional]
A pointer to a CtxtHandle structure. On the first call to AcceptSecurityContext (Negotiate), this pointer is
NULL. On subsequent calls, phContext is the handle to the partially formed context that was returned in the phNewContext parameter by the first call.
Do not use the same context handle in concurrent calls to AcceptSecurityContext (Negotiate). The API implementation in the security service providers is not thread-safe.
Channel binding information can be specified by passing in a SecBuffer structure of type SECBUFFER_CHANNEL_BINDINGS in addition to the buffers generated by the call to the InitializeSecurityContext (General) function. The channel binding information for the channel binding buffer can be obtained by calling the QueryContextAttributes (Schannel) function on the Schannel context the client used to authenticate.
Bit flags that specify the attributes required by the server to establish the context. Bit flags can be combined by using bitwise-OR operations. This parameter can be one or more of the following values.
|ASC_REQ_CONFIDENTIALITY||Encrypt and decrypt messages.|
|ASC_REQ_CONNECTION||The security context will not handle formatting messages.|
|ASC_REQ_DELEGATE||The server is allowed to impersonate the client. Valid for Kerberos. Ignore this flag for constrained delegation.|
|ASC_REQ_EXTENDED_ERROR||When errors occur, the remote party will be notified.|
|ASC_REQ_INTEGRITY||Sign messages and verify signatures.|
|ASC_REQ_REPLAY_DETECT||Detect replayed packets.|
|ASC_REQ_SEQUENCE_DETECT||Detect messages received out of sequence.|
For possible attribute flags and their meanings, see Context Requirements. Flags used for this parameter are prefixed with ASC_REQ, for example, ASC_REQ_DELEGATE.
The requested attributes may not be supported by the client. For more information, see the pfContextAttr parameter.
The data representation, such as byte ordering, on the target. This parameter can be either SECURITY_NATIVE_DREP or SECURITY_NETWORK_DREP.
[in, out, optional]
A pointer to a CtxtHandle structure. On the first call to AcceptSecurityContext (Negotiate), this pointer receives the new context handle. On subsequent calls, phNewContext can be the same as the handle specified in the phContext parameter. phNewContext should never be
[in, out, optional]
A pointer to a SecBufferDesc structure that contains the output buffer descriptor. This buffer is sent to the client for input into additional calls to InitializeSecurityContext (Negotiate). An output buffer may be generated even if the function returns SEC_E_OK. Any buffer generated must be sent back to the client application.
A pointer to a variable that receives a set of bit flags that indicate the attributes of the established context. For a description of the various attributes, see Context Requirements. Flags used for this parameter are prefixed with ASC_RET, for example, ASC_RET_DELEGATE.
Do not check for security-related attributes until the final function call returns successfully. Attribute flags not related to security, such as the ASC_RET_ALLOCATED_MEMORY flag, can be checked before the final return.
Until the last call of the authentication process, the expiration time for the context can be incorrect because more information will be provided during later stages of the negotiation. Therefore, ptsTimeStamp must be
NULL until the last call to the function.
This function returns one of the following values.
|The function failed. There is not enough memory available to complete the requested action.|
|The function failed. An error occurred that did not map to an SSPI error code.|
|The function failed. The handle passed to the function is not valid.|
|The function failed. The token passed to the function is not valid.|
|The logon failed.|
|The function failed. No authority could be contacted for authentication. This could be due to the following conditions:|
|The function succeeded. The [*security context*](../secgloss/s-gly.md) received from the client was accepted. If an output token was generated by the function, it must be sent to the client process.|
|The function succeeded. The server must call [CompleteAuthToken](/windows/win32/api/sspi/nf-sspi-completeauthtoken) and pass the output token to the client. The server then waits for a return token from the client and then makes another call to [AcceptSecurityContext (Negotiate)](acceptsecuritycontext--negotiate.md).|
|The function succeeded. The server must finish building the message from the client and then call the [CompleteAuthToken](/windows/win32/api/sspi/nf-sspi-completeauthtoken) function.|
|The function succeeded. The server must send the output token to the client and wait for a returned token. The returned token should be passed in pInput for another call to [AcceptSecurityContext (Negotiate)](acceptsecuritycontext--negotiate.md).|
The AcceptSecurityContext (Negotiate) function is the server counterpart to the InitializeSecurityContext (Negotiate) function.
When the server receives a request from a client, the server uses the fContextReq parameter to specify what it requires of the session. In this fashion, a server can specify that clients must be capable of using a confidential or integrity-checked session, and it can reject clients that cannot meet that demand. Alternatively, a server can require nothing, and whatever the client can provide or requires is returned in the pfContextAttr parameter.
For a package that supports multiple-leg authentication, such as mutual authentication, the calling sequence is as follows:
- The client transmits a token to the server.
- The server calls AcceptSecurityContext (Negotiate) the first time, which generates a reply token that is then sent to the client.
- The client receives the token and passes it to InitializeSecurityContext (Negotiate). If InitializeSecurityContext (Negotiate) returns SEC_E_OK, mutual authentication has been completed and a secure session can begin. If InitializeSecurityContext (Negotiate) returns an error code, the mutual authentication negotiation ends. Otherwise, the security token returned by InitializeSecurityContext (Negotiate) is sent to the client, and steps 2 and 3 are repeated.
- Do not use the phContext value in concurrent calls to AcceptSecurityContext (Negotiate). The implementation in the security providers is not thread-safe.
The fContextReq and pfContextAttr parameters are bitmasks that represent various context attributes. For a description of the various attributes, see Context Requirements.
The pfContextAttr parameter is valid on any successful return, but only on the final successful return should you examine the flags pertaining to security aspects of the context. Intermediate returns can set, for example, the ISC_RET_ALLOCATED_MEMORY flag.
The caller is responsible for determining whether the final context attributes are sufficient. If, for example, confidentiality (encryption) was requested, but could not be established, some applications may choose to shut down the connection immediately. If the security context cannot be established, the server must free the partially created context by calling the DeleteSecurityContext function. For information about when to call the DeleteSecurityContext function, see DeleteSecurityContext.
After the security context has been established, the server application can use the QuerySecurityContextToken function to retrieve a handle to the user account to which the client certificate was mapped. Also, the server can use the ImpersonateSecurityContext function to impersonate the user.
|Minimum supported client||Windows XP [desktop apps only]|
|Minimum supported server||Windows Server 2003 [desktop apps only]|
|Header||Sspi.h (include Security.h)|