| Previous | Next |
| SEC_E_CANNOT_INSTALL | SEC_E_CANNOT_PACK |
SEC_E_INVALID_TOKEN
SEC_E_INVALID_TOKEN means that SSPI cannot accept the supplied security token or token buffer. The cause depends on the operation: a handshake token can be malformed, truncated, corrupted in transit, or sent to the wrong package; a Schannel data call can also fail when the required buffer types are missing.
Separate the two stages
- During context setup, log the handshake round, token length, selected package and peer endpoint.
- During message decryption, verify that the input contains the required
SECBUFFER_DATAand token buffers. - Never reuse bytes from a previous connection or from a different protocol layer.
Security note
Do not turn off validation or accept the data as plaintext after this status. It means the security boundary has not been established or cannot verify the record.
Microsoft: InitializeSecurityContext (Schannel) · DecryptMessage
Looking for a different code? Search another status or error code.