[35823] in Kerberos
Re: On credential cache separation between service ticket and TGT
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Mar 5 11:42:48 2014
Message-ID: <531753FE.4020302@mit.edu>
Date: Wed, 05 Mar 2014 11:42:38 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Arpit Srivastava <arpit.orb@gmail.com>
In-Reply-To: <CAEvOXU6oY5_7uMAvPTsmY501j01SN2aXHrtmyE-Ha0kmncVGCA@mail.gmail.com>
Cc: kerberos <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 03/05/2014 10:55 AM, Arpit Srivastava wrote:
> That is the problem now. How to separate service tickets from the TGT so
> as to copy it (only) to the different cache ? It would be great if you
> can give some pointers.
1. Open the original ccache with krb5_cc_resolve.
2. Retrieve the service cred with krb5_cc_retrieve_cred.
3. Close the original ccache with krb5_cc_close.
4. Open the new ccache with krb5_cc_resolve.
5. Initialize the new ccache with krb5_cc_initialize.
6. Store the previously obtained cred with krb5_cc_store_cred.
7. Close the new ccache with krb5_cc_close.
8. Release the service cred with krb5_free_cred_contents.
Documentation for these functions is at:
http://web.mit.edu/kerberos/krb5-latest/doc/appdev/refs/api/index.html
If you have to iterate over the source ccache to find the service ticket
because krb5_cc_retrieve_cred won't work for you, use
krb5_cc_start_seq_get, krb5_cc_next_cred, and krb5_cc_end_seq_get.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
