Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This is a follow-up from bug 707009 . After a successful server install with external-ca option, the ipa command fails with the following error :

# ipa user-show admin
ipa: ERROR: cert validation failed for "CN=ns1.<domain>,O=<REALM>" ((SEC_ERROR_UNKNOWN_ISSUER) Peer's Certificate issuer is not recognized.)
ipa: ERROR: cannot connect to u'https://ns1.<domain>/ipa/xml': [Errno -8179] (SEC_ERROR_UNKNOWN_ISSUER) Peer's Certificate issuer is not recognized.

Likewise, firefox complains about the certificates too, because the browser configuration only imports the external CA certificate ; I suppose it should import both external CA and IPA certificate.

I use ipa version 2.0.1 with the patch from attachment 503774 [details] , on a redhat 6.1 server.

Can you look at /etc/ipa/ca.crt and confirm that there are 2 encoded certificates there? It should have the external CA and the IPA CA certs.

I have looked to the file and it contains the two certificates.

I tried to add the IPA certificate into the system-wide certificate database (in /etc/pki/nssdb), and the ipa command worked. This database contained only the external CA, with the nickname "IPA CA", which is a bit confusing.

Besides, I think that /usr/share/ipa/html/ca.crt should contain the IPA certificate and not the external CA ; clients which are configuring firefox are supposed to know about the external CA, but not about the IPA CA.

I'll try to duplicate this.

The entire cert chain is in ca.crt to make it easier for new clients to communicate with IPA, one-stop shopping as it were.

https://fedorahosted.org/freeipa/ticket/1376

I've been unable to duplicate this. In all cases the CA certificate in ca.crt and in the public NSS database is the local IPA CA.

I'm testing with the current IPA master branch. Quite a lot has changed when loading certificates and how they are named, it is possible that this was fixed during those changes.