RA:
(1) Security Domain panel contained: NOTE: Since a Security Domain MUST be a CA (although all CAs are NOT necessarily Security Domains), an appropriate value for this URL may be obtained by logging into the machine which hosts the desired Security Domain CA as 'root' and running the command "/sbin/service pki-cadstatus <security_domain_instance_name> " from the command-line. which refers to a CA that has been configured via 'pkicreate'. (2) Security Domain (usersys.redhat.com Security Domain) Login panel contained: RED ! $errorString (3) Final panel contained: "/sbin/service pki-rad restart pki-ra" statement which did not work; had to issue "systemctl restart pki-rad@pki-ra.service".
TPS:
(1) Security Domain panel contained: NOTE: Since a Security Domain MUST be a CA (although all CAs are NOT necessarily Security Domains), an appropriate value for this URL may be obtained by logging into the machine which hosts the desired Security Domain CA as 'root' and running the command "/sbin/service pki-cadstatus <security_domain_instance_name> " from the command-line. which refers to a CA that has been configured via 'pkicreate'. (2) Security Domain (usersys.redhat.com Security Domain) Login panel contained: RED ! $errorString (3) Final panel contained: "/sbin/service pki-tpsd restart pki-tps" statement which did not work; had to issue "systemctl restart pki-tpsd@pki-tps.service".
Fixed and pushed to master in 40378f5a796227db137de932b143801cd17ad9e3
Metadata Update from @mharmsen: - Issue assigned to kaskahn - Issue set to the milestone: 10.0.2
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/1023
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.