The following tables lists calling errors returned by the GSS-API; that is, errors that are specific to a particular language-binding (C, in this case).
Table B–2 Calling Errors
Error |
Value in Field |
Meaning |
---|---|---|
GSS_S_CALL_INACCESSIBLE_READ |
1 |
A required input parameter could not be read |
GSS_S_CALL_INACCESSIBLE_WRITE |
2 |
A required output parameter could not be written |
GSS_S_CALL_BAD_STRUCTURE |
3 |
A parameter was malformed |
The following table lists the routine errors (that is, generic errors returned by GSS-API functions).
Table B–3 Routine Errors
Error |
Value in Field |
Meaning |
---|---|---|
GSS_S_BAD_MECH |
1 |
An unsupported mechanism was requested |
GSS_S_BAD_NAME |
2 |
An invalid name was supplied |
GSS_S_BAD_NAMETYPE |
3 |
A supplied name was of an unsupported type |
GSS_S_BAD_BINDINGS |
4 |
Incorrect channel bindings were supplied |
GSS_S_BAD_STATUS |
5 |
An invalid status code was supplied |
GSS_S_BAD_MIC, GSS_S_BAD_SIG |
6 |
A token had an invalid MIC |
GSS_S_NO_CRED |
7 |
No credentials were supplied, or the credentials were unavailable or inaccessible |
GSS_S_NO_CONTEXT |
8 |
No context has been established |
GSS_S_DEFECTIVE_TOKEN |
9 |
A token was invalid |
GSS_S_DEFECTIVE_CREDENTIAL |
10 |
A credential was invalid |
GSS_S_CREDENTIALS_EXPIRED |
11 |
The referenced credentials have expired |
GSS_S_CONTEXT_EXPIRED |
12 |
The context has expired |
GSS_S_FAILURE |
13 |
Miscellaneous failure. The underlying mechanism detected an error for which no specific GSS–API status code is defined. The mechanism-specific status code (minor-status code) provides more details about the error. |
GSS_S_BAD_QOP |
14 |
The quality-of-protection requested could not be provided |
GSS_S_UNAUTHORIZED |
15 |
The operation is forbidden by local security policy |
GSS_S_UNAVAILABLE |
16 |
The operation or option is unavailable |
GSS_S_DUPLICATE_ELEMENT |
17 |
The requested credential element already exists |
GSS_S_NAME_NOT_MN |
18 |
The provided name was not a Mechanism Name (MN) |
The routine documentation also uses the name GSS_S_COMPLETE, which is a zero value, to indicate an absence of any API errors or supplementary information bits.
The following table lists the supplementary information values returned by GSS-API functions.
Table B–4 Supplementary Information Codes
Code |
Bit Number |
Meaning |
---|---|---|
GSS_S_CONTINUE_NEEDED |
0 (LSB) |
Returned only by gss_init_sec_context() or gss_accept_sec_context(). The routine must be called again to complete its function |
GSS_S_DUPLICATE_TOKEN |
1 |
The token was a duplicate of an earlier token |
GSS_S_OLD_TOKEN |
2 |
The token's validity period has expired |
GSS_S_UNSEQ_TOKEN |
3 |
A later token has already been processed |
GSS_S_GAP_TOKEN |
4 |
An expected per-message token was not received |
For more on status codes, see Status Codes.