| Previous | Next |
| WINBIO_I_EXTENDED_STATUS_INFORMATION | SEC_I_COMPLETE_NEEDED |
SEC_I_CONTINUE_NEEDED
SEC_I_CONTINUE_NEEDED is a successful intermediate SSPI result: the security context is not ready for protected application data, but the handshake must continue with another token exchange.
What the caller must do
Send the output token to the peer, receive the peer response, and call InitializeSecurityContext or AcceptSecurityContext again with the same context. With Schannel, the output token can be empty, so the state transition must be driven by the status rather than by token length.
Common implementation error
- Starting to send encrypted application data before the final successful status.
- Discarding the returned context between handshake rounds.
- Calling the same context concurrently from multiple threads.
Microsoft: InitializeSecurityContext (Schannel) · AcceptSecurityContext (General)
Looking for a different code? Search another status or error code.