When setting up a Dogtag system 10.0.6-1.fc18 with 3 different VM servers:-
1 - IPA 1 - CA 1 - RA
The RA Config Wizard will not allow the RA to join a Security Domain, the sdomainURL that is entered is ignored.
The web page on the RA displays properly but even though a Security Domain URL of https://CA:8443 is entered the web page instantly throws back and error to say "Security Domain HTTPS Admin URL not found".
A TCPDump shows that a query is never sent out and that the RA simply queries against port 9445 on either its own IP address or the loopback 127.0.0.1 - which obviously then fails.
Additional info:-
Both the CA and RA are VMs and are on the same LAN, the CA is 10.0.0.10 and the RA is 10.0.0.11. I have more luck with the pkisilent command but that also gives some errors, that is included in the attached logs as well.
Thanks
Carrots
A better formatted output of the errors problems with RA.txt
This has been resolved. Things done in the process of resolution:-
All the old database files were deleted on the Directory server from the slapd folder.
The pkiadmin groups etc were recreated on the RA.
The CA server was missing dogtag-pki.noarch along with pki-krb5.
Everything Dogtag related was removed from the RA server, the OCSP server was then installed first (this needed the configuration stage skipping in pkispawn - I think due to old directory server databases causing issues.
When the RA's pkicreate was run again I manually added the CA hostname and port :8443 in the file /usr/share/pki/ra/conf/CS.cfg as something was reported in the output from the above pkicreate regarding values which had not been substituted.
Metadata Update from @carrots: - Issue set to the milestone: N/A
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1364
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.