Winfried de Heiden wrote:
> Hi all,
>
> Yes, there was a discrepancy in de certificates and was fixed by using
> https://floblanc.wordpress.com/2017/09/11/troubleshooting-freeipa-pki-tomcatd-fails-to-start/.
>
> Thanks for that!
>
> Now, getcert ist still shows errors. The certmonger logs
Hi all,
Yes, there was a discrepancy in de certificates and was fixed by
using https://floblanc.wordpress.com/2017/09/11/troubleshooting-freeipa-pki-tomcatd-fails-to-start/.
Thanks for that!
Now, getcert ist still shows errors. The certmonger
On 09/12/2017 09:10 AM, Winfried de Heiden via FreeIPA-users wrote:
Hi all,
I'll try my using the link provided. However: what is causing
"CA_UNREACHABLE"?
Request ID '20170129002017':
status: CA_UNREACHABLE
ca-error: Server at https://ipa.blabla.bla/ipa/xml failed request,
will
Hi all,
I'll try my using the link provided. However: what is causing
"CA_UNREACHABLE"?
Request ID '20170129002017':
status: CA_UNREACHABLE
ca-error: Server at https://ipa.blabla.bla/ipa/xml failed
request, will retry: 4035 (RPC
On ti, 12 syys 2017, Igor Sever via FreeIPA-users wrote:
Unfortunately, I cannot upgrade systems and packages as I want because of
legacy applications.
Is there somewhere information how would I approach to configure SSSD
to use FreeIPA as Kerberos and LDAP provider and for policies to work?
I
Unfortunately, I cannot upgrade systems and packages as I want because of
legacy applications.
Is there somewhere information how would I approach to configure SSSD to use
FreeIPA as Kerberos and LDAP provider and for policies to work? I can only find
where access is enforced with LDAP filter
