[16486] in Kerberos_V5_Development
Re: X-CACHECONF in cache type 0504
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Nov 19 11:43:22 2010
From: Greg Hudson <ghudson@mit.edu>
To: Tim Alsop <Tim@cybersafe.com>
In-Reply-To: <C90C5533.27A21%Tim.Alsop@CyberSafe.com>
Date: Fri, 19 Nov 2010 11:43:18 -0500
Message-ID: <1290184998.2633.1275.camel@ray>
Mime-Version: 1.0
Cc: "krbdev@MIT.EDU" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Fri, 2010-11-19 at 11:27 -0500, Tim Alsop wrote:
> Ok, so we can use krb5_ccache_conf_data at the start with the X-CACHECONF:
> as realm, but the data between these two elements can be anything we want.
>
> e.g. This is valid and acceptable if found in a cache:
> krb5_ccache_conf_data/foo/bar/hello/world@X-CACHECONF:
Well, any service principal is valid and acceptable according to the
cache format.
To work with the Heimdal/MIT krb5_cc_get_config API, the principal must
have three components: "krb5_ccache_conf_data", the config key, and the
unparsed name of the cache's default client principal.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
