[Freeipa-users] Re: Broken WebUI

I checked on the certificates as you suggested and none show they are expired. Any other suggestions? sudo getcert list | grep expires expires: 2019-08-25 20:51:47 UTC expires: 2019-08-25 20:50:38 UTC expires: 2019-08-25 20:50:58 UTC expires: 2035-10-13 20:50:26 UTC

[Freeipa-users] Re: Broken WebUI

Here is the last user_show I did: [Mon Oct 16 10:27:25.164027 2017] [:error] [pid 24937] ipa: INFO: nesre...@chem.byu.edu: batch: user_show(u'aaburton', rights=True, all=True): SUCCESS [Mon Oct 16 10:27:25.216336 2017] [:error] [pid 24937] ipa: INFO: nesre...@chem.byu.edu: batch:

[Freeipa-users] Re: unexpected upgrade to 4.5

On ma, 16 loka 2017, Charles Hedrick via FreeIPA-users wrote: I just installed a new replica on Centos 7.3. Our existing servers are also on Centos 7.3, and use IPA 4.4, which comes with Centos 7.3. I was somewhat surprised to find that my new replica was IPA 4.5 with a newer version of sssd as

[Freeipa-users] Re: unexpected upgrade to 4.5

Hello, to prevent such situation is to prevent installing new packages. FreeIPA cannot prevent it but yum can. You can use `yum version-lock` in package yum-plugin-versionlock HTH On Mon, Oct 16, 2017 at 5:15 PM, Charles Hedrick via FreeIPA-users wrote: >

[Freeipa-users] unexpected upgrade to 4.5

I just installed a new replica on Centos 7.3. Our existing servers are also on Centos 7.3, and use IPA 4.4, which comes with Centos 7.3. I was somewhat surprised to find that my new replica was IPA 4.5 with a newer version of sssd as well. It appears that the replica install process did the

[Freeipa-users] Re: several IPA CA certificate entries

Bhavin Vaidya via FreeIPA-users wrote: Thank you. your help is appreciated. We are still out of luck and this is becoming very critical for us. Please help. We did remove all but 1 certificate, restarted master (ds01) but clientinstallation, connection check and replica installation still