Manual Pages  — GSS_PROCESS_CONTEXT_TOKEN

gss_process_context_token – Process a token on a security context from a peer application

SYNOPSIS DESCRIPTION PARAMETERS RETURN VALUES SEE ALSO STANDARDS HISTORY AUTHORS COPYRIGHT

#include <gssapi/gssapi.h>

OM_uint32
gss_process_context_token(OM_uint32 *minor_status, const gss_ctx_id_t context_handle, const gss_buffer_t token_buffer);

Provides a way to pass an asynchronous token to the security service. Most context-level tokens are emitted and processed synchronously by gss_init_sec_context() and gss_accept_sec_context(), and the application is informed as to whether further tokens are expected by the GSS_C_CONTINUE_NEEDED major status bit. Occasionally, a mechanism may need to emit a context-level token at a point when the peer entity is not expecting a token. For example, the initiator's final call to gss_init_sec_context() may emit a token and return a status of GSS_S_COMPLETE, but the acceptor's call to gss_accept_sec_context() may fail. The acceptor's mechanism may wish to send a token containing an error indication to the initiator, but the initiator is not expecting a token at this point, believing that the context is fully established. gss_process_context_token() provides a way to pass such a token to the mechanism at any time.

minor_status	Mechanism specific status code.
context_handle
	Context handle of context on which token is to be processed.
token_buffer	Token to process.

GSS_S_COMPLETE	Successful completion
GSS_S_DEFECTIVE_TOKEN
	Indicates that consistency checks performed on the token failed
GSS_S_NO_CONTEXT	The context_handle did not refer to a valid context

RFC 2743
	Generic Security Service Application Program Interface Version 2, Update 1
RFC 2744
	Generic Security Service API Version 2 : C-bindings

The gss_process_context_token function first appeared in FreeBSD 7.0 .

John Wray, Iris Associates

Copyright (C) The Internet Society (2000). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.