[32261] in Kerberos
Re: no renewable flag in krb5.conf ?
daemon@ATHENA.MIT.EDU (=?ISO-8859-1?Q?Mark_Pr=F6hl?=)
Tue Apr 13 13:48:35 2010
Message-ID: <4BC4AE62.80500@mproehl.net>
Date: Tue, 13 Apr 2010 19:48:18 +0200
From: =?ISO-8859-1?Q?Mark_Pr=F6hl?= <mark@mproehl.net>
MIME-Version: 1.0
To: Guillaume Rousse <Guillaume.Rousse@inria.fr>
In-Reply-To: <4BC45C3E.8010708@inria.fr>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Hi,
you probably want to use the parameter renew_lifetime in [libdefaults].
Mark
Guillaume Rousse wrote:
> Hello.
>
> I just realized than it was possible to force forwardable tickets
> through krb5.conf, but not renewable ones. Is it intentional ?
>
> For instance, the following doesn't work as expected:
> [appdefaults]
> pam = {
> forwardable = true
> renewable = true
> }
>
>
> ------------------------------------------------------------------------
>
> ________________________________________________
> Kerberos mailing list Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
