Hello all,
I finally got something working, and found something of a cause.
I replaced
policyset.serverCertSet.1.default.params.name=CN=$$request.req_subject_name.cn$$,
$SUBJECT_DN_O
with
policyset.serverCertSet.1.default.params.name=CN=$request.req_subject_name.cn$,
o=FAKEDOMAIN.LOCAL
import
Hello everybody,
Still need some help. I'm a bit further already. I'm pretty sure the error is
in the caIPAserviceCert profile. Would someone please take a look? The whole
profile is below.
I suspect something is wrong in this section:
policyset.serverCertSet.1.default.class_id=subjectNameDefa
Hallo everybody,
I think i'm getting somewhere, but i need a little bit more help.
A couple of weeks ago the caIPAserviceCert.cfg was updated to fix a subject
alternative names problem with the latest chrome browser. I've put back the
original file from the RPM now and imported it with "ipa cer
Rob,
Thank you for replying. I've enable debug and i think this is the relevant
portion of the log.
[Sat Jun 10 04:18:58.109402 2017] [:error] [pid 11081] ipa: DEBUG:
NSSConnection init freeipa.fakedomain.local
[Sat Jun 10 04:18:58.271640 2017] [:error] [pid 11081] ipa: DEBUG: Connecting:
192.
Hello all,
This i my first post here, so be gentle.
I'm running FreeIPA 4.4.0-14 (ipa-server-4.4.0-14.el7.centos.7.x86_64) on
CentOS 7.3.1611 and since a while i can't get any certificates to my hosts.
The client has installed: ipa-client-4.4.0-14.el7.centos.7.x86_64 ans is also
running CentOS
