Orion Poplawski wrote:
On 01/16/2013 06:50 PM, Rob Crittenden wrote:
We really need to put a big fat warning on this too: there be dragons.
It is really meant for v1 servers where we didn't have a full CA. The
really integrated into IPA v2+ such that replacing certs is going to
some amount of grief (as you've seen).
I didn't think we blew away the existing NSS database using the tool,
it certainly sounds like we are.
What you're missing in the ipaCert in /etc/httpd/alias. This is used to
authenticate to dogtag. Can you poke around in /etc/httpd to see if a
was made, or use certutil to get a list of the nicknames in there?
I'm guessing it is trying to issue an SSL cert for the CA 389-ds
There are no cli options for providing that. Even if you did manage to
prepared file you'd likely run into a whole new batch of install
Sorry about that. We really need to decide whether this tool is worth
supporting at all and fix it (or make it safer) or simply do away with
Right now it's just a really sharp tool waiting to cut someone.
Well, it looks like it move all of the existing files in
/etc/httpd/alias to .orig extensions. I moved those over to an
alias.orig directory and imported the ipaCert key. That allowed
ipa-replica-prepare to run.
Preparing replica for ipapub.cora.nwra.com from ipa.cora.nwra.com
Copying SSL certificate for the Directory Server from
Creating SSL certificate for the dogtag Directory Server
Copying SSL certificate for the Web Server from STAR_cora_nwra_com.p12
Copying additional files
Packaging replica information into
But then on ipa-replica-install, problems as predicted:
[16/30]: configuring ssl for ds instance
creation of replica failed: Could not find a CA cert in
Ok, I think what I would recommend is preparing a replica w/o replacing
the certs (e.g. let the CA issue certs for all the services).
Install the replica.
Then replace with the wildcard certs once the install is up and functioning.
Freeipa-users mailing list