I would like to hear more from IPA people. It is not a problem to replace authconfig related code with something else.
My questions are more about what we will get after the change and whether this will be what we actually want.


On Wed, Feb 21, 2018 at 10:25 AM, Pavel Březina <pbrezina@redhat.com> wrote:
On 02/21/2018 10:17 AM, Alexander Koksharov wrote:
let me put
​ ​
​ ​
couple of scenarious here:
- install server
  install it and configure with authselect. there is no --no-sssd option
for the server installation
- upgrade server
  bakup authselect configuration. apply authselect sssd profile
overwriting what was there before.

Why do you call authselect during server update? Shouldn't the system be already configured?

- upgrade client
  not applicable. only new binaries are copied onto the system
- install client
  a) if we replace rpm dependancy on authconfig with aushselect we can
go only this way: new installations done with authselect. if --no-sssd
option is provided, then fail.
  b) if we add authselect as a new dependancy, then we can apply a logic
like authselect by default but if no-sssd then do authconfig.

The people did talk to are kind of think that a) will bi implemented. I
want to finish this task this week. Can we finally agree on a or b ?

A. Authconfig will not be available. Only though compat tool, but that provides only a minimum level of compatibility and translates calls to authselect.


On Mon, Feb 19, 2018 at 10:47 AM, Pavel Březina <pbrezina@redhat.com
<mailto:pbrezina@redhat.com>> wrote:

    On 02/14/2018 09:15 AM, Alexander Koksharov via FreeIPA-devel wrote:


        Please take a look on a design page here:
        I would like to

    You will also need to write krb5.conf and ldap.conf. You can see the
    following man page or compat tool for inspiration.


        ​ ​
        hear you critics and suggessions.

        Thank you


        FreeIPA-devel mailing list --
        To unsubscribe send an email to