# Way to find out missing root-CA

**URL:** https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126
**Category:** Gateway
**Created:** [June 28, 2010, 12:58pm UTC](https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126 "2010-06-28T12:58:04Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![lst\_hoe021](https://avatars.discourse-cdn.com/v4/letter/l/58956e/32.png) [@lst\_hoe021](https://community.ciphermail.com/u/lst_hoe021)
#### Post date: [June 28, 2010, 12:58pm UTC](https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126/1 "2010-06-28T12:58:04Z")

</div>

Hello

is there a easy way to find out which root-CA is missing if a user  
certificate is stated as invalid because of missing root?

Many Thanks

Andreas

---

<div class="post-metadata">

### Author: ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [June 28, 2010, 8:38pm UTC](https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126/2 "2010-06-28T20:38:42Z")

</div>

> is there a easy way to find out which root-CA is missing if a user  
> certificate is stated as invalid because of missing root?

The way to do it currently is to copy the issuer field of the  
certificate (open the certificate info by clicking the cert) then search  
for the issuer field in the certificate store by clicking the filter,  
select "Filter by: Subject" and paste the issuer.

You should normally get at max one result which should normally be the  
issuer.

Perhaps I might add a path builder result page which shows the possible  
cert path.

Kind regards,

Martijn

> **···**
>
> --  
> Djigzo open source email encryption

---

<div class="post-metadata">

### Author: ![lst\_hoe021](https://avatars.discourse-cdn.com/v4/letter/l/58956e/32.png) [@lst\_hoe021](https://community.ciphermail.com/u/lst_hoe021)
#### Post date: [July 6, 2010, 8:49am UTC](https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126/3 "2010-07-06T08:49:20Z")

</div>

Zitat von Martijn Brinkers \<martijn(a)djigzo.com\>:

> > is there a easy way to find out which root-CA is missing if a user  
> > certificate is stated as invalid because of missing root?
> 
> The way to do it currently is to copy the issuer field of the  
> certificate (open the certificate info by clicking the cert) then search  
> for the issuer field in the certificate store by clicking the filter,  
> select "Filter by: Subject" and paste the issuer.
> 
> You should normally get at max one result which should normally be the  
> issuer.
> 
> Perhaps I might add a path builder result page which shows the possible  
> cert path.

This would require the root CA already in the store?  
I was looking for a way to find out where to look for a download for  
example if a certificate arrives with no matching root CA until now.  
Is there some URL included in the cert data which contain a path to  
the issuer CAs.

Regards

Andreas

---

<div class="post-metadata">

### Author: ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [July 6, 2010, 8:57am UTC](https://community.ciphermail.com/t/way-to-find-out-missing-root-ca/126/4 "2010-07-06T08:57:10Z")

</div>

> This would require the root CA already in the store?

Yes

> I was looking for a way to find out where to look for a download for  
> example if a certificate arrives with no matching root CA until now.  
> Is there some URL included in the cert data which contain a path to  
> the issuer CAs.

Unfortunately afaik there is not standard way to provide a URL to the  
issuer. With the well known CAs in most cases it's easy to find out but  
with company generated CAs it's not always clear where to get the CA  
from. Djigzo will always include to root certificate to make sure that  
the receiving end always gets the root as well (not that this helps in  
your case because the sender was probably not using Djigzo).

Kind regards,

Martijn

> **···**
>
> --  
> Djigzo open source email encryption
