Hello Rob.

Hm sorry for my ignorance, may you tell me how to use this ? Or maybe you have some links I could use to have this ?

Best regards.

Lune

Le ven. 5 juin 2020 à 21:36, Rob Crittenden <rcritten@redhat.com> a écrit :
lune voo via FreeIPA-users wrote:
> Hello !
>
> I send you this mail because I have a question with the command line of
> IPA and the high availability of IPA.
>
> I have the following setup :
>
>   * 2 IPA servers (version 4.6.6) on RHEL 7.6 : S1 and S2
>   * n IPA clients (version 3.0.0) on RHEL 6.6
>
> When I installed ipa clients with ipa-client-install, I specified both
> IPA servers.
> Yesterday, S1 crashed.
>
> On one of the client, the command line was not working anymore.
>
> ipa user-show myuser
>
> ipa: ERROR: cannot connect to 'ldapi://%2fvar%2frun%2fslapd-MYREALM.socket':
>
>
> It appears the command line use the following file to know which IPA
> server to contact :
> /etc/ipa/default.conf
>
> In this file, I saw that there was only S1 mentioned :
>
> # cat /etc/ipa/default.conf
>
> #File modified by ipa-client-install
>
>  
>
> [global]
>
> basedn = dc=myrealm
>
> realm = MYREALM
>
> domain = mydomain.com <http://mydomain.com>
>
> server = S1.mydomain.com <http://S1.mydomain.com>
>
> xmlrpc_uri = https://S1.mydomain.com/ipa/xml
>
> enable_ra = True
>
>
> Is it possible to benefit from high availability when we use IPA command
> line ?
> If yes, how ?

In order to do ipa cli fallback you have to use DNS _ldap._tcp SRV records.

rob