[Freeipa-devel] Announcing FreeIPA 4.6.2

2017-12-12 Thread Tibor Dudlák via FreeIPA-devel
The FreeIPA team would like to announce FreeIPA 4.6.2 release! It can be downloaded from http://www.freeipa.org/page/Downloads. Builds for Fedora 26 and 27 will be available in the official [https://copr.fedorainfracloud.org/coprs/g/freeipa/freeipa-4-6/ COPR repository]. == Highlights in 4.6.2

[Freeipa-devel] GitHub assignee labels

2018-01-15 Thread Tibor Dudlák via FreeIPA-devel
Hi people! I could not miss that we stopped using github's assignee label and I have got used to it. Is there possibility to bring this habit back on track? I find it very useful when i am trying to find PR which I want to look into it. Thanks! -- Tibor Dudlák Identity management - freeIPA

[Freeipa-devel] Re: IPA's NTP service

2018-01-29 Thread Tibor Dudlák via FreeIPA-devel
On Mon, Jan 29, 2018 at 3:09 PM, Simo Sorce wrote: > On Mon, 2018-01-29 at 14:54 +0100, Tibor Dudlák wrote: > > [...] > > > > > > So given the above we initially decided to make IPA servers also > ntp > > > > > servers and configure client to use IPA server as time sources. >

[Freeipa-devel] Re: IPA's NTP service

2018-02-06 Thread Tibor Dudlák via FreeIPA-devel
Hi! To be more clear about what i do want to achieve, there is bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1456863 I want to replace ntp configuration with script provided by Miroslav Lichvar. And if any administrator would like to have another time synchronization service up and

[Freeipa-devel] How do replication should work?

2018-07-25 Thread Tibor Dudlák via FreeIPA-devel
Hello! I am trying to resolve a [1] issue and I just bumped into questions that grinds my gears. First of all after some effort spent by Christian, we had some patches that helped parallel replication, but the PR2048 [2] brought to life a regression on DL0 mentioned in issue [1] . I think that

[Freeipa-devel] IPA's NTP service

2018-01-24 Thread Tibor Dudlák via FreeIPA-devel
Hello FreeIPA-devel list fellow beings! I would like to continue the discussion started in [1], and find its solution. While using the Single-Sign-on authentication provided via an MIT Kerberos KDC there must not be any significant clock skew between server and clients so a time synchronization