On Wed, 2017-05-31 at 10:59 +0200, Jakub Hrozek wrote:
> On Wed, May 31, 2017 at 10:31:38AM +0200, Lukas Slebodnik wrote:
> > ehlo,
> >
> > I had a discussion with QEs and realized that sssd need to be
> > restarted
> > if default_ccache_name is changed in krb5 configuration files.
> >
> > The
On Wed, May 31, 2017 at 02:21:42PM +0200, Lukas Slebodnik wrote:
> On (31/05/17 10:59), Jakub Hrozek wrote:
> >We could do one thing that Simo proposed some time ago which is to not
> >cache the KRB5CCNAME at all if it only contains 'predictable'
> >components.
> >
> >For example, KEYRING:$uid or
On (31/05/17 10:59), Jakub Hrozek wrote:
>We could do one thing that Simo proposed some time ago which is to not
>cache the KRB5CCNAME at all if it only contains 'predictable'
>components.
>
>For example, KEYRING:$uid or KCM: don't need to be cached at all.
>FILE:krb5ccname_X does.
That would
On Wed, May 31, 2017 at 10:31:38AM +0200, Lukas Slebodnik wrote:
> ehlo,
>
> I had a discussion with QEs and realized that sssd need to be restarted
> if default_ccache_name is changed in krb5 configuration files.
>
> The reason is that we cache the value but do not refresh it.
>
On Wed, May 31, 2017 at 10:31:38AM +0200, Lukas Slebodnik wrote:
> ehlo,
>
> I had a discussion with QEs and realized that sssd need to be restarted
> if default_ccache_name is changed in krb5 configuration files.
>
> The reason is that we cache the value but do not refresh it.
>
