On Wed, 2017-04-05 at 21:02 +0200, Jakub Hrozek wrote:
> On Tue, Nov 22, 2016 at 08:51:10AM +0100, Jakub Hrozek wrote:
> > Hi,
> >
> > I was working on a KCM server for SSSD for some time already in parallel
> > with the files provider and had some discussions with Simo as well. Of
> > course my
On Tue, Nov 22, 2016 at 08:51:10AM +0100, Jakub Hrozek wrote:
> Hi,
>
> I was working on a KCM server for SSSD for some time already in parallel
> with the files provider and had some discussions with Simo as well. Of
> course my intent wasn't to implement a feature secretly without a design
>
On Tue, Nov 22, 2016 at 09:49:52AM -0500, Stephen Gallagher wrote:
> On 11/22/2016 09:38 AM, Simo Sorce wrote:
> > On Tue, 2016-11-22 at 09:23 -0500, Stephen Gallagher wrote:
>
> >> OK, so the service is only semi-socket-activated? If we're keeping tevent
> >> timers
> >> around for renewals and
On 11/22/2016 09:38 AM, Simo Sorce wrote:
> On Tue, 2016-11-22 at 09:23 -0500, Stephen Gallagher wrote:
>> OK, so the service is only semi-socket-activated? If we're keeping tevent
>> timers
>> around for renewals and reaping, the service won't be exiting unless all
>> tickets
>> have expired
On Tue, Nov 22, 2016 at 09:23:22AM -0500, Stephen Gallagher wrote:
> Some thoughts inline:
>
> On 11/22/2016 02:51 AM, Jakub Hrozek wrote:
>
> ...
>
> > === Implementation details ===
> > A new SSSD responder will be added. Since accessing the Kerberos credentials
> > is quite an infrequent
On Tue, 2016-11-22 at 09:23 -0500, Stephen Gallagher wrote:
> Some thoughts inline:
>
> On 11/22/2016 02:51 AM, Jakub Hrozek wrote:
>
> ...
>
> > === Implementation details ===
> > A new SSSD responder will be added. Since accessing the Kerberos credentials
> > is quite an infrequent operation,
