Hide Forgot
The IdM web UI shows certificates issued by sub-CAs as expected To display the certificates issued by a certificate authority (CA), the IdM web UI uses the "ipa cert-find" command to query the CA name, and then the "ipa cert-show" command. Previously, "ipa cert-show" did not use the CA name. As a consequence, attempting to display the details page for a certificate issued by a sub-CA failed with an error in the web UI. This bug has been fixed, and the web UI now displays the details pages for certificates as expected.
Created attachment 1192103 [details] cert_details.png Description of problem: Web UI fails to show certificates issued by Sub-CA Version-Release number of selected component (if applicable): ipa-server-4.4.0-8.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Generate CSR 2. ipa cert-request --ca=SampleSubCA1 with CSR and Principal 3. Goto web ui 'cert/details/' Actual results: IPA Web UI fails to show certificates issued by Sub-CA Expected results: IPA Web UI should show certificates issued by Sub-CA
Upstream ticket: https://fedorahosted.org/freeipa/ticket/6238
Fixed upstream master: https://fedorahosted.org/freeipa/changeset/40f923f56b4777e3e18c9f76ba1a745ed69ef0a6 https://fedorahosted.org/freeipa/changeset/64ac981dddcecf1176585b6e7b729cf38b24bcea ipa-4-4: https://fedorahosted.org/freeipa/changeset/0b76ba8723d7ba6f7657d0f7c17f2fc2a7356752 https://fedorahosted.org/freeipa/changeset/29af03aa4283883612bdc8cbd299f5caa6adee2b
Created attachment 1199287 [details] subca_issuer.png Verified using IPA version :: ipa-server-4.4.0-10.el7.x86_64 Steps used for verification :: 1. Generate CSR 2. ipa cert-request --ca=SampleSubCA1 with CSR and Principal 3. Goto web ui 'cert/details/' and verify if Certificate generated is issued by Sub CA
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2404.html