|
cc_context_release(): Release memory associated with a cc_context_t.
|
|
cc_context_get_change_time(): Get the last time the cache collection changed.
The time returned by cc_context_get_changed_time() increases whenever:
|
|
cc_context_get_default_ccache_name(): Get the name of the default ccache.
If there is no default ccache, and the client is creating a new ccache, it should be created with the default name. If there already is a default ccache, and the client wants to create a new ccache (as opposed to reusing an existing ccache), it should be created with any unique name; create_new_ccache() can be used to accomplish that more easily. If the first ccache is created with a name other than the default name, then the processes already running will not notice the credentials stored in the new ccache, which is normally undesirable. |
|
cc_context_open_ccache(): Open a ccache.
The list of all ccache names, principals, and credentials versions may be retrieved by calling cc_context_new_cache_iterator(), cc_ccache_get_name(), cc_ccache_get_principal(), and cc_ccache_get_cred_version(). |
|
cc_context_open_default_ccache(): Open the default ccache.
This function performs the same function as calling cc_context_get_default_ccache_name followed by cc_context_open_ccache, but it performs it atomically. |
|
cc_context_create_ccache(): Create a new ccache.
If you want to create a new ccache (with a unique name), you should use cc_context_create_new_ccache() instead. If you want to create or reinitialize the default cache, you should use cc_context_create_default_ccache(). If name is non-NULL and there is already a ccache named name:
If the created ccache is the first ccache in the collection, it is made the default ccache. Note that normally it is undesirable to create the first ccache with a name different from the default ccache name (as returned by cc_context_get_default_ccache_name()); see the description of cc_context_get_default_ccache_name() for details. The principal should be a C string containing an unparsed Kerberos principal in the format of the appropriate Kerberos version, i.e. foo.bar/@BAZ * foo/bar/@BAZ |
|
cc_context_create_default_ccache(): Create a new default ccache.
|
|
cc_context_create_new_ccache(): Create a new uniquely named ccache.
|
|
cc_context_new_ccache_iterator(): Get an iterator for the cache collection.
If changes are made to the collection while an iterator is being used on it, the iterator must return at least the intersection, and at most the union, of the set of ccaches that were present when the iteration began and the set of ccaches that are present when it ends. |
|
cc_context_lock(): Lock the cache collection.
Locks apply only to the list of ccaches, not the contents of those ccaches. To prevent callers participating in the advisory locking from changing the credentials in a cache you must also lock that ccache with cc_ccache_lock(). This is so that you can get the list of ccaches without preventing applications from simultaneously obtaining service tickets. To avoid having to deal with differences between thread semantics on different platforms, locks are granted per context, rather than per thread or per process. That means that different threads of execution have to acquire separate contexts in order to be able to synchronize with each other. The lock should be unlocked by using cc_context_unlock().
|
|
cc_context_unlock(): Unlock the cache collection.
|
|
cc_context_compare(): Compare two context objects.
|
|
cc_context_wait_for_change(): Wait for the next change in the cache collection.
cc_context_wait_for_change() will return whenever:
|