| Previous | Next |
| SEC_I_INCOMPLETE_CREDENTIALS | SEC_I_NO_LSA_CONTEXT |
SEC_I_RENEGOTIATE
SEC_I_RENEGOTIATE tells an Schannel application that the peer requires a new security handshake, or that the local shutdown sequence has reached the renegotiation state. It is a protocol transition, not decrypted application data.
Correct handling
Return to the negotiation loop: client code calls InitializeSecurityContext, server code calls AcceptSecurityContext. If DecryptMessage returned a SECBUFFER_EXTRA buffer, preserve it and provide it as the next input token instead of dropping bytes that may already have been read from the stream.
Do not confuse it with EOF
A shutdown notification is reported separately as SEC_I_CONTEXT_EXPIRED. Closing the transport immediately on renegotiation can break valid client-certificate or protocol-driven handshakes.
Microsoft: Renegotiating an Schannel Connection · DecryptMessage
Looking for a different code? Search another status or error code.