Manual Reference Pages - GSS_ACQUIRE_CRED (3)
- Obtain a GSS-API credential handle for pre-existing credentials
const gss_name_t desired_name
const gss_OID_set desired_mechs
Allows an application to acquire a handle for a pre-existing
credential by name.
GSS-API implementations must impose a local
access-control policy on callers of this routine to prevent
unauthorized callers from acquiring credentials to which they are not
This routine is not intended to provide a "login to the
network" function, as such a function would involve the creation of
new credentials rather than merely acquiring a handle to existing
Such functions, if required, should be defined in
implementation-specific extensions to the API.
If desired_name is
the call is interpreted as a
request for a credential handle that will invoke default behavior
when passed to
(if cred_usage is
(if cred_usage is
Mechanisms should honor the
and return a credential that is suitable to use only with the
An exception to this is the case where one underlying credential
element can be shared by multiple mechanisms;
in this case it is permissible for an implementation to indicate all
mechanisms with which the credential element may be used.
is an empty set, behavior is undefined.
This routine is expected to be used primarily by context acceptors,
since implementations are likely to provide mechanism-specific ways
of obtaining GSS-API initiator credentials from the system login
Some implementations may therefore not support the acquisition of
for any name other than
or a name produced by applying either
to a valid credential, or
to an active context.
If credential acquisition is time-consuming for a mechanism,
the mechanism may choose to delay the actual acquisition until the
credential is required
Such mechanism-specific implementation
decisions should be invisible to the calling application;
thus a call of
immediately following the call of
must return valid credential data,
and may therefore incur the overhead of a deferred credential acquisition.
Name of principal whose credential should be acquired.
Number of seconds that credentials should remain valid.
to request that the credentials have the maximum
Set of underlying security mechanisms that may be used.
may be used to obtain an implementation-specific default.
Credentials may be used either to initiate or accept security
Credentials will only be used to initiate security contexts.
Credentials will only be used to accept security contexts.
The returned credential handle.
associated with this credential handle must be released by
the application after use with a call to
The set of mechanisms for which the credential is valid.
Storage associated with the returned OID-set must be released by the
application after use with a call to
NULL if not required.
Actual number of seconds for which the returned credentials will
If the implementation does not support expiration of credentials,
will be returned.
Specify NULL if not required.
Mechanism specific status code.
Unavailable mechanism requested.
Type contained within desired_name parameter is not supported.
Value supplied for desired_name parameter is ill formed.
The credentials could not be acquired because they have expired.
No credentials were found for the specified name.
| RFC 2743
Generic Security Service Application Program Interface Version 2, Update 1
| RFC 2744
Generic Security Service API Version 2 : C-bindings
function first appeared in
.Fx 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
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.
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.