This appendix includes the following sections:
GSS-API Functions provides a table of GSS-API functions.
GSS-API Status Codes discusses status codes returned by GSS-API functions, and provides a list of those status codes.
GSS-API Data Types and Values discusses the various data types used by GSS-API.
Implementation-Specific Features in GSS-API covers features that are unique to the Oracle Solaris implementation of GSS-API.
Kerberos v5 Status Codes lists the status codes that can be returned by the Kerberos v5 mechanism.
Additional GSS-API definitions can be found in the file gssapi.h.
The Oracle Solaris software implements the GSS-API functions. For more information on each function, see its man page. See also Functions From Previous Versions of GSS-API.
Assume a global identity by obtaining a GSS-API credential handle for preexisting credentials
Process a token on a security context from a peer application
Calculate a cryptographic message integrity code (MIC) for a message
Check a MIC against a message to verify integrity of a received message
Attach a MIC to a message, and optionally encrypt the message content
Verify a message with attached MIC. Decrypt message content if necessary
This section explains functions that were included in previous versions of the GSS-API.
The Oracle Solaris implementation of GSS-API provides the following functions for convenience and for backward compatibility. However, these functions might not be supported by other implementations of GSS-API.
Although a mechanism's name can be converted from a string to an OID, programmers should use the default GSS-API mechanism if at all possible.
The following functions have been supplanted by newer functions. In each case, the new function is the functional equivalent of the older function. Although the old functions are supported, developers should replace these functions with the newer functions whenever possible.