Bug 715275

Summary:	ipa ERROR : cert validation failed (SEC_ERROR_UNKNOWN_ISSUER) with external CA
Product:	Red Hat Enterprise Linux 6	Reporter:	Charles Leclerc <charles>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED WORKSFORME	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	benl, dpal, jgalipea
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-20 17:09:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Charles Leclerc 2011-06-22 12:02:40 UTC

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.

Comment 2 Rob Crittenden 2011-06-22 13:51:51 UTC

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.

Comment 3 Charles Leclerc 2011-06-22 14:39:59 UTC

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

Comment 4 Charles Leclerc 2011-06-22 15:13:37 UTC

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.

Comment 5 Rob Crittenden 2011-06-22 21:41:53 UTC

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

Comment 6 Rob Crittenden 2011-07-20 17:09:02 UTC

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.