# Credentials Cache API v2 Specification

### This version of the API is deprecated.
Please refer to CCAPI version 3 or later for the current API.

- Type Definitions
  - cc_int32 & cc_uint32
  - cc_time_t
  - cc_nc_flags
  - cc_cred
  - cc_data
  - V4Cred_type
  - StringToKey_Type
  - cc_cred_vers
  - cred_ptr_union
  - cred_union
  - infoNC
  - opaque types
- Error Code Definitions
- Implementation Notes
- Function Definitions
  - Main Cache Functions
    - cc_initialize
    - cc_create
    - cc_open
    - cc_close
    - cc_destroy
    - cc_shutdown
    - cc_initialize
    - cc_get_change_time
    - cc_get_NC_info
    - cc_seq_fetch_NCs_begin
    - cc_seq_fetch_NCs_next
    - cc_seq_fetch_NCs_end
  - NC Functions
    - cc_get_name
    - cc_get_cred_version
    - cc_get_principal
    - cc_get_instance
    - cc_remove_cred
    - cc_store
    - cc_get_instance
    - cc_seq_fetch_creds_begin
    - cc_seq_fetch_creds_next
    - cc_seq_fetch_creds_end
    - cc_lock_request
  - Liberation Functions
    - cc_free_principal
    - cc_free_name
    - cc_free_creds
    - cc_free_NC_info
- Revision History/Notes
  - Changes made during revsion 3
- Ideas for Future Versions
- Abstract

## Abstract

This is the specification for an API which provides Credentials Cache services for both Kerberos V5 and V4. The idea behind this API is that multiple Kerberos implementations can share a single Credentials Cache, mediated by this API specification. On the Microsoft Windows platform this will allow single-signon, even when more than one Kerberos DLL is in use on a particular system. Ideally, this problem could be solved by standardizing the Kerberos V5 API library interface. However, the Kerberos API is complicated enough that this would be hard to accomplish. Standardizing the interface for credentials cache access is much simpler. This API has also been adopted in the MIT Kerberos for the Macintosh implementation.

This specification has been revised to allow storage and manipulation of both V4 and V5 tickets. A cache contains one or more "Named Cache"s. It is assumed that V4 and V5 credentials would each be stored in separate "Named Cache"s and not mixed in a single "Named Cache".

Below, "NC" refers to "Named Cache".

## Revision History/Notes

#### Original version (Draft Version 1)

1/27/96 by Theodore Ts'o

#### Revision 2 (Draft Version 1)

970628 by Steve Rothwell for the V4Cache Team (Paul Hill, Jenny Khuon, Jean Luker, Dave Detlefs, Allan Bjorklund, & Steve Rothwell)

#### Revision 3 (Draft Version 1)

970725 by Steve Rothwell after initial implementation and alpha release. The term "credentials cache" was previously used to mean both "the main cache" and individual "named cache"s within the main cache. I have started using the term "NC" for "named cache" to make the distinction clearer and to reduce the overloading of the word "cache".

##### Changes made for revision 3 of this API:

- Added cred version type to cc_create() & cc_open()
- New functions
  - cc_get_NC_info(), returns NC_info list for all NCs
  - cc_free_NC_info(), frees NC_info list
  - cc_get_cred_version(), returns version type of NC
  - cc_get_name(), returns name of NC
  - cc_free_name(), frees name aquired via cc_get_name()
  - cc_seq_fetch_NCs(), iterate over all NCs
- New return codes
  - CC_BAD_PARM
  - CC_ERR_CACHE_ATTACH
  - CC_ERR_CACHE_RELEASE
  - CC_ERR_CACHE_FULL
  - CC_ERR_CRED_VERSION
- Modified functions
  - cc_create(), cc_open(), pass version type of NC
  - cc_store(), cc_remove(), cc_
- New & Modified typedefs & data structures
  - cc_cred_vers { CC_CRED_VUNKNOWN, CC_CRED_V4, CC_CRED_V5 }
  - cred_ptr_union : contains pointer to credentials (either V4 or V5)
  - cred_union : contains version type and cred_ptr_union
  - modified V4Cred_type
  - enum StringToKey_Type { STK_AFS or STK_DES }
  - copies of the maximum V4 string size indicators KRB_PRINCIPAL_SZ, KRB_SERVICE_SZ, KRB_INSTANCE_SZ, KRB_REALM_SZ, ADDR_SZ

#### Revision 4 (Draft Version 1)

970908 by Steve Rothwell to incorporate changes initiated by Ted Tso. Further changes are expected in the comments for cc_create() and cc_get_change_time().

#### Revision 4a (Final Version 1)

980603 by Scott McGuire to correct typographical errors, HTML errors, and minor clarifications. Final API Version 1 spec.

#### Revision 5 (Draft Version 2)

990201 by Scott McGuire.

- Increased API version number to 2.
- Added enum's defining version numbers.
- Changes to cc_initialize() to specify how to deal with different API version numbers.
- Added description of cc_int32 and cc_uint32 types.
- Change some cc_int32's to cc_uint32's.
- Changed way cc_create() will behave when called on an existing cache.
- Replaced cc_seq_fetch_NCs() with cc_seq_fetch_NCs_begin(), cc_seq_fetch_NCs_next(), and cc_seq_fetch_NCs_end();
- Replaced cc_seq_fetch_creds() with cc_seq_fetch_creds_begin(), cc_seq_fetch_creds_next(), and cc_seq_fetch_creds_end();
- Replaced enum type references in structs and function paramenters with cc_int32 references;
- Replaced int type references in function parameters with cc_int32;
- Added return type of cc_int32 to all functions;
- Removed #ifdef from cred_union structure;
- Constant definitions and changes to V4Cred_type structure;
- Removed incorrect const ccache_p * parameters from cc_store() and cc_remove_cred();
- Added CC_NOERROR and CC_BAD_PARM as possible return codes from all functions (except no CC_BAD_PARM from cc_shutdown() );
- Added CC_ERR_CRED_VERSION as possible return code from cc_open() and cc_create();
- Moved infoNC structure definition up to be with rest of structure definitions;
- Changed "struct _infoNC" to "infoNC" in parameter type references.
- cc_free_principal() and cc_free_name() now take char ** instead of char * for final parameter. (This change was made between rev 4a and rev 5, but I'm re-emphasizing it here.)
- Added Implementation Notes section with requirement that all functions must be atomic and name requirements for Windows DLL's.
- Renamed "the proposed changes to this API are" section to "Ideas for Future Versions" -- but removed all items but one because they'd all been done.
- Removed most of the notes about differences with the Win NT/95 implementation of the API -- the differences have been reconciled.
- Removed unnecessary and inconsistent italicizing.

#### Revsion 5a (Final Version 2)

990723 by Scott McGuire.

- cc_create(): Removed text about "expected" form of name. Removed note about "the alpha version does not do this."
- cc_destroy(): Clarified that you do not need to call cc_close() on the cache_pointer after calling this function.
- Removed note about Windows cc_get_instance() and cc_set_instance() functions, they are no longer part of the Windows code!

## Ideas for Future Versions

- Define Get/Set functions for all components of _cc_creds? (This will allow future changes to the data structure to be transparent to the caller. This also makes backward compatibility much easier to maintain.)

## Type definitions

    // enums for API versions used in cc_initialize()
    enum {
       CC_API_VER_1 = 1,
       CC_API_VER_2 = 2
    };

    // cc_int32 and cc_uint32 are not exactly defined in this API due
    // to a lack of standard 32-bit integer size between platforms
    // (although there is the C9X standard).
    // However, we will place the following constraints:
    //
    // cc_int32 is a signed integer that is at least 32 bits wide.
    // cc_uint32 is an unsigned integer that is at least 32 bits wide

    typedef cc_int32 cc_time_t;  //see notes below

    typedef cc_uint32 cc_nc_flags;

    typedef struct opaque_dll_control_block_type* apiCB;
    typedef struct opaque_ccache_pointer_type* ccache_p;
    typedef struct opaque_credential_iterator_type* ccache_cit;

    // These really are intended to be opaque. All implementations of the cache API must have
    // them but what they are is implementation specific. In the case of SGR's implementation,
    // the cc_ctx returned available after a call to cc_initialize, is a CCache_ctx class object. The
    // code that normally calls the cc_initialize function is straight C, which means the calling
    // application doesn't have a chance in hell of manipulating this directly. The API is designed
    // so that it does not have to. It does have to pass the pointer to the class around, one reason
    // being so that the destructor can eventually be called.

    typedef struct _cc_data {
        cc_uint32            type;
        cc_uint32            length;
        unsigned char*      data;
    } cc_data;

    typedef struct _cc_creds {
        char*       client; /* client's principal identifier */
        char*       server; /* server's principal identifier */
        cc_data     keyblock;       /* session encryption key info */
        cc_time_t   authtime;
        cc_time_t   starttime;
        cc_time_t   endtime;
        cc_time_t   renew_till;
        cc_uint32    is_skey;        /* true if ticket is encrypted in
                                       another ticket's skey */
        cc_uint32    ticket_flags;   /* flags in ticket */
        cc_data**   addresses;      /* addrs in ticket */
        cc_data     ticket;         /* ticket string itself */
        cc_data     second_ticket;  /* second ticket, if related to
                                       ticket (via DUPLICATE-SKEY or
                                       ENC-TKT-IN-SKEY) */
        cc_data**   authdata;       /* authorization data */
    } cc_creds;

    // use an enumerated type so all callers infer the same meaning
    // these values are what krbv4win uses internally.

    enum StringToKey_Type { STK_AFS = 0, STK_DES = 1 };

    enum { MAX_V4_CRED_LEN = 1250 };

    // V4 Credentials

    enum {
      KRB_NAME_SZ = 40,
      KRB_INSTANCE_SZ = 40,
      KRB_REALM_SZ = 40
    };

    typedef struct _V4credential {
        unsigned char              kversion;
        char                       principal[KRB_NAME_SZ+1];
        char                       principal_instance[KRB_INSTANCE_SZ+1];
        char                       service[KRB_NAME_SZ+1];
        char                       service_instance[KRB_INSTANCE_SZ+1];
        char                       realm[KRB_REALM_SZ+1];
        unsigned char              session_key[8];
        cc_int32                   kvno;                   // k95 used BYTE skvno
        cc_int32                   str_to_key;             // k4 infers dynamically, k95 stores; of type enum StringToKey_Type
        long                       issue_date;             // k95 called this issue_time
        cc_int32                   lifetime;               // k95 used LONG expiration_time
        cc_uint32                  address;                // IP Address of local host as an unsigned 32-bit integer
        cc_int32                   ticket_sz;              // k95 used BYTE, k4 ktext uses int to hold up to 1250
        unsigned char              ticket[MAX_V4_CRED_LEN];
        unsigned long              oops;                   // zero to catch runaways
    } V4Cred_type;

    enum cc_cred_vers {
        CC_CRED_VUNKNOWN = 0,       // For validation
        CC_CRED_V4 = 1,
        CC_CRED_V5 = 2,
        CC_CRED_VMAX = 3            // For validation
    };

    typedef union cred_ptr_union_type {
        V4Cred_type* pV4Cred;
        cc_creds*    pV5Cred;
    } cred_ptr_union;

    typedef struct cred_union_type {
        cc_int32 cred_type;  // cc_cred_vers
        cred_ptr_union cred;
    } cred_union;

    typedef struct _infoNC {
            char*   name;
            char*   principal;
            cc_int32 vers;   // cc_cred_vers
    } infoNC;

#### The cc_data structure

The cc_data structure is used to store the following elements:

- keyblock
- addresses
- ticket (and second_ticket)
- authorization data

For cc_creds.ticket and cc_creds.second_ticket, the cc_data.type field MUST be zero. For the cc_creds.addresses, cc_creds.authdata, and cc_data.keyblock, the cc_data.type field should be the address type, authorization data type, and encryption type, as defined by the Kerberos V5 protocol definition.

#### cc_time_t

The cc_time_t fields are used to represent time. The time must be stored as the number of seconds since midnight GMT on January 1, 1970.

#### Principal names

Principal names are stored as C strings in this API. The C strings may contain UTF-8 encoded strings for internationalization purposes.

## Error Codes Definition

0 | CC_NOERROR | "Successful return"
1 | CC_BADNAME | "Bad credential cache name format"
2 | CC_NOTFOUD | "Matching credential not found"
3 | CC_END | "End of credential cache reached"
4 | CC_IO | "Credentials cache I/O operation failed"
5 | CC_WRITE | "Error writing to credentials cache file"
6 | CC_NOMEM | "No memory"
7 | CC_FORMAT | "Corrupted credentials cache"
8 | CC_LOCKED | "The credentials cache or NC is locked"
9 | CC_BAD_API_VERSION | "Unsupported API version"
10 | CC_NO_EXIST | "Credentials cache or NC does not exist"
11 | CC_NOT_SUPP | "Function not supported"
12 | CC_BAD_PARM | "Bad Paramter Passed"
13 | CC_ERR_CACHE_ATTACH | "Failed to attach cache"
14 | CC_ERR_CACHE_RELEASE | "Failed to release cache"
15 | CC_ERR_CACHE_FULL | "Cache FULL"
16 | CC_ERR_CRED_VERSION | "Wrong Cred Version"

## Implementation Notes

#### All functions are atomic

All Credentials Cache API functions must be atomic.

Windows

DLLs should be named KrbCC16.dll and KrbCC32.dll.

## Function definitions

### Main Cache Functions

#### cc_initialize

    cc_int32 cc_initialize(apiCB** cc_ctx, cc_int32 api_version, cc_int32* api_supported, char** vendor)

This function performs any initialization required by the API. It must be called before any other function in the API is called. The cc_ctx returned by this function must be passed to all other API functions as the first argument.

The application must pass in the maximum version number of the API it supports in the api_version parameter.

If api_supported non-NULL, then cc_initialize will store the maximum API version number supported by the library implementing the API there.

If the version requested by api_version is not equal to the version supported by the library, CC_BAD_API_VERSION will be returned as the error code (along with the version the library does support in api_supported) and cc_initialize should not allocate any memory.

If the vendor is non-NULL, then cc_initialize will store a pointer to a read/only C string which contains a string describing the vendor which implemented the credentials cache API.

Possible error codes: CC_NOERROR, CC_NOMEM, CC_BAD_API_VERSION, CC_BAD_PARM

#### cc_shutdown

    cc_int32 cc_shutdown(apiCB** cc_ctx)

This function performs any cleanup required by the API. cc_ctx will be NULL on return. The application program must call cc_initialize() again before making any credentials cache API calls.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_get_change_time

    cc_int32 cc_get_change_time(apiCB* cc_ctx, cc_time_t* time)

This function returns the time of the most recent change for the entire cache. There is ONE timestamp maintained for the entire cache. By maintaining a local copy the caller can deduce whether "something changed" or not.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_NOMEM, CC_BAD_PARM

#### cc_get_NC_info

    cc_int32 cc_get_NC_info(apiCB* cc_ctx, infoNC*** ppNCi)

cc_get_NC_info() is a wrapper for cc_seq_fetch_NCs(), cc_get_name() cc_get_cred_version(), and cc_get_principal(). It returns all the information needed to uniquely identify each NC in the cache (name and cred_version) and the associated principal. Specifically it returns a null terminated list of pointers to infoNC structs. Each infoNC struct contain a pointer to the NC's name, a pointer to the the principal associated with the NC, and the version number (as an enumerated type) of the credentials stored in this NC.

The ppNCi (the entire data structure) aquired by this routine should be freed with cc_free_NC_info().

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_NOMEM, CC_BAD_PARM

#### cc_open

    cc_int32 cc_open(apiCB* cc_ctx, const char* name, cc_int32 cred_vers, cc_uint32 cc_flags,
                     ccache_p** ccache_pointer)

Opens an already exising NC identified by both name, and cred_vers. It fills in the parameter **ccache_pointer with a pointer to the NC.

The list of cache names, principals, and credentials versions may be retrieved via cc_seq_fetch_NCs(), cc_get_name(), cc_get_cred_version(), & cc_get_principal() OR via cc_get_NC_info().

Possible error codes: CC_NOERROR, CC_BADNAME, CC_NO_EXIST, CC_NOMEM, CC_ERR_CRED_VERSION, CC_BAD_PARM

#### cc_create

    cc_int32 cc_create(apiCB* cc_ctx, const char* name, const char* principal,
                    cc_int32 cred_vers, cc_uint32 cc_flags, ccache_p** ccache_pointer)

Create a new NC. The NC is uniquely identified by the combination of it's name and the "cc_creds_vers" (i.e. which credentials version it holds). The principal given is also associated with the NC. A NULL name is not allowed (and CC_BADNAME should be returned if one is passed in). If name is non-null and there is already a NC named name, all credentials in the cache are removed, and handle for the existing cache is returned. If there is already a NC named name, all existing handles for this cache remain valid. The NC is created with a primary principal specified by principal.

(Removed text about the "expected" form of the NC name.)

An NC is intended to hold credentials for a single principal in a single realm, and for a single credentials version (i.e. V4 or V5). The cache can contain credentials for other credential versions, other realms, and even other principals, but each in a separate NC. This rule will allow callers that can only handle a single principal in a single realm to continue to work by dealing with only one NC. Callers that can deal with multiple principals, multiple realms, and/or multiple credentials versions can do so by dealing with multiple NCs. By doing it this way, the callers that are able to handle multiple principals, realms, and/or versions can do so without interfering with "differently abled" code.

The list of cache names, principals, & cred_versions may be retrieved via cc_get_NC_info().

Possible error codes: CC_NOERROR, CC_BADNAME, CC_BAD_PARM, CC_NO_EXIST, CC_NOMEM, CC_ERR_CRED_VERSION

#### cc_close

    cc_int32 cc_close(apiCB* cc_ctx, ccache_p** ccache_pointer)

Close the NC. The ccache_pointer related memory is deallocated, and ccache_pointer is set to NULL before being returned to caller.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_destroy

    cc_int32 cc_destroy(apiCB* cc_ctx, ccache_p** ccache_pointer)

Destroy the NC pointed to by ccache_pointer. The ccache_pointer related memory is deallocated, and ccache_pointer is set to NULL before being returned to caller. The caller does not need to call cc_close() on the cache_pointer afterwards.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_seq_fetch_NCs_begin

    cc_int32 cc_seq_fetch_NCs_begin(apiCB* cc_ctx, ccache_cit** itNCs)

Used to allocate memory and initialize the iterator *itNCs. Use cc_seq_fetch_NCs_end() to deallocate the memory used by *itNCs.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM, CC_NOMEM

####

#### cc_seq_fetch_NCs_next

    cc_int32 cc_seq_fetch_NCs_next(apiCB* cc_ctx, ccache_p** ccache_pointer, ccache_cit* itNCs)

Used to sequentially open every NC in the cache.

Ccache_pointer must be a pointer to a ccache_p*. The ccache_pointer returned may be used to get information about the NC by calling cc_get_name(), cc_get_cred_version(), and cc_get_principal(). Ccache_pointer's returned must be freed via cc_close() between calls to cc_seq_fetch_NCs_next().

itNCs must be a pointer to a ccache_cit* variable provided by the calling application and which is used by cc_seq_fetch_NCs_next() to determine the next NC to return. It must have been initialized by cc_seq_fetch_NCs_begin().

If changes are made to the credentials cache while it iterator is being used, it must return at least the intersection, and at most the union, of the set of NC's that were in the cache when the iteration began and the set of NC's that are in the cache when it ends.

When the last NC in the sequence is returned, the return code from cc_seq_fetch_NCs_next() will be CC_END.

Possible error codes: CC_NOERROR, CC_END, CC_NO_EXIST. CC_BAD_PARM, CC_NOMEM

####

####

#### cc_seq_fetch_NCs_end

    cc_int32 cc_seq_fetch_NCs_end(apiCB* cc_ctx, ccache_cit** itNCs)

Deallocates the memory used by *itNCs, and sets *itNCs to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

### NC Functions

#### cc_get_name

    cc_int32 cc_get_name(apiCB* cc_ctx, const ccache_p* ccache_pointer, char** name)

cc_get_name() returns the name of the NC indicated by ccache_pointer. The name can be used in cc_open() or cc_create(). The combination of the name and the credentials version uniqeuly identify an NC. The returned name should be freed via cc_free_name().

Possible error codes: CC_NOERROR, CC_NOMEM, CC_NO_EXIST, CC_BAD_PARM

#### cc_get_cred_version

    cc_int32 cc_get_cred_version(apiCB* cc_ctx, const ccache_p* ccache_pointer, cc_int32* cred_vers)

cc_get_cred_version() returns one of the enumerated type cc_cred_vers in cred_vers. The expected values are CC_CRED_V4, or CC_CRED_V5. The combination of the name and the credentials version uniquely identify an NC.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_set_principal

    cc_int32 cc_set_principal(apiCB* cc_ctx, const ccache_p* ccache_pointer, const cc_int32 cred_vers,
                              const char* principal)

Set the primary principal for the NC indicated by ccache_pointer. This is the complement to cc_get_principal().

cred_vers is used as a double check.

principal points to a null terminated string that will be copied into the NC. This new principal will be returned if you call cc_get_principal() for this NC.

Possible error codes: CC_NOERROR, CC_NOMEM, CC_NO_EXIST, CC_ERR_CRED_VERSION, CC_BAD_PARM

#### cc_get_principal

    cc_int32 cc_get_principal(apiCB* cc_ctx, const ccache_p* ccache_pointer, char** principal)

Return the primary principal for the NC that was set via cc_create() or cc_set_principal(). The returned principal should be freed via cc_free_principal() .

Possible error codes: CC_NOERROR, CC_NOMEM, CC_NO_EXIST, CC_BAD_PARM

#### cc_store

    cc_int32 cc_store(apiCB* cc_ctx, ccache_p* ccache_pointer, const cred_union cred)

Store (make a copy of) cred in the NC indicated by ccache_pointer.

A cred_union contains a cred_type indicator and a cred_ptr_union. A cred_ptr_union can contain either a V4Cred_type pointer or a cc_creds (V5 creds) pointer. Cred_type indicates which type of pointer is in the cred_ptr_union. This also allows the API to enforce the credentials version declared in cc_create() or cc_open().

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_ERR_CACHE_FULL, CC_ERR_CRED_VERSION, CC_BAD_PARM

#### cc_remove_cred

    cc_int32 cc_remove_cred(apiCB* cc_ctx, ccache_p* ccache_pointer, const cred_union cred)

Removes the credential cred from ccache_pointer. The credentials in the NC indicated by ccache_pointer are searched to find a matching credential. If found, that credential is removed from the NC. The cred parameter is not modified and should be freed via cc_free_creds(). It is legitimate to call this function during a sequential fetch, and the deletion of a credential already returned by cc_seq_fetch_creds() should not disturb sequence of credentials returned by cc_seq_fetch_creds().

Use of cred_union is the same as is explained in cc_store().

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_NOTFOUND, CC_ERR_CRED_VERSION, CC_BAD_PARM

#### cc_seq_fetch_creds_begin

    cc_int32 cc_seq_fetch_creds_begin(apiCB* cc_ctx, const ccache_p* ccache_pointer, ccache_cit** itCreds)

Allocates memory for and initializes *itCreds. This memory must be deallocated using cc_seq_fetch_creds_end().

Ccache_pointer must be a valid pointer to the NC containing the creds to be returned by the iterator.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM, CC_NOMEM

#### cc_seq_fetch_creds_next

    cc_int32 cc_seq_fetch_creds_next(apiCB* cc_ctx, cred_union** cred, ccache_cit* itCreds)

cc_seq_fetch_creds_next() is used to sequentially read every set of credentials in an NC. The NC has been indicated in the call to cc_seq_fetch_creds_begin().

itCreds must be a pointer to a ccache_cit* variable provided by the calling application and which is used by cc_seq_fetch_creds_next() to determine the next cached credential to return. The ccache_cit* variable must be initialized by calling cc_seq_fetch_creds_begin().

The credentials are filled into the cred_union pointed to by creds. Note that the cred_union contains elements which are dynamically allocated, so must be freed using cc_free_creds() between calls to cc_seq_fetch_creds_next().

If changes are made to the NC while it iterator is being used, it must return at least the intersection, and at most the union, of the set of credentials that were in the NC when the iteration began and the set of credentials that are in the NC when it ends.

When the last credential in the sequence is returned, the return code from cc_seq_fetch_creds_next() will be CC_END.

Possible error codes: CC_NOERROR, CC_END, CC_NO_EXIST, CC_BAD_PARM, CC_NOMEM

#### cc_seq_fetch_creds_end

    cc_int32 cc_seq_fetch_creds_end(apiCB* cc_ctx, ccache_cit** itCreds)

Deallocates memory used by *itCreds and sets *itCreds to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_lock_request

    cc_int32 cc_lock_request(apiCB* cc_ctx, const ccache_p* ccache_pointer, cc_int32 lock_type)

  99/02/11 - smcguire
  As of this date there is no locking in the Win NT/95 or Machintosh implementations. The description below may not be completely accurate as to how this function should be implemented.

This function is currently NOT IMPLEMENTED. All functions attach to the cache, take action, and detach from the cache before returning to the caller.

This function will lock or unlock the NC based on the argument value of lock_type:

            CC_LOCK_UNLOCK  1       Unlock the NC
            CC_LOCK_READER  2       Lock the NC for reading
            CC_LOCK_WRITER  3       Lock the NC for writing

            CC_LOCK_NOBLOCK 16      Don't block, but return an error code if
                                    the request cannot be satisfied.

Locking is done on a per-thread basis. At most one thread may have the credentials locked for writing; if so, there must not be any threads that have the credentials locked for reading.

Multiple threads may have the cache locked for reading, as long as there is not a writer lock asserted on the cache.

If a thread has a cache locked for reading, that lock may be upgraded to a writer lock by calling cc_lock_request() with a lock_type of CC_LOCK_WRITER. If a thread has the cache locked for reading or writing, a request to cc_lock_request() for a reader or writer lock, respectively, is a no-op. If a thread does not have the cache locked, and calls cc_lock_request() with a lock_type of CC_LOCK_UNLOCK, this is also a no-op.

A request for CC_LOCK_READER and CC_LOCK_WRITER may be made non-blocking by logical or'ing the value CC_LOCK_NOBLOCK. In that case, if it is not possible to satisfy the lock request, the error CC_LOCKED will be returned.

### Liberation Functions

#### cc_free_principal

    cc_int32 cc_free_principal(apiCB* cc_ctx, char** principal)

This function frees the principal returned by cc_get_principal() and sets *principal to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_free_name

    cc_int32 cc_free_name(apiCB* cc_ctx, char** name)

This function frees the name returned by cc_get_name() and sets *name to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_free_creds

    cc_int32 cc_free_creds(apiCB* cc_ctx, cred_union** creds)

This function frees all storage associated with creds returned by cc_seq_fetch_creds() and sets the creds pointer to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM

#### cc_free_NC_info

    cc_int32 cc_free_NC_info(apiCB* cc_ctx, infoNC*** ppNCi)

This routine frees all storage aquired by cc_get_NC_info() and sets ppNCi to NULL.

Possible error codes: CC_NOERROR, CC_NO_EXIST, CC_BAD_PARM