[RADIATOR] Certificate Not Trusted - InCommon?

Ullfig, Roberto Alfredo rullfig at uic.edu
Wed Jun 2 15:38:10 UTC 2021

We are using these options:


So we should use:


with all certs in it? There are two intermediate certs - does their order matter?

Roberto Ullfig - rullfig at uic.edu
Systems Administrator
Enterprise Applications & Services | Technology Solutions
University of Illinois - Chicago
From: radiator <radiator-bounces at lists.open.com.au> on behalf of Heikki Vatiainen <hvn at open.com.au>
Sent: Wednesday, June 2, 2021 10:17 AM
To: radiator at lists.open.com.au <radiator at lists.open.com.au>
Subject: Re: [RADIATOR] Certificate Not Trusted - InCommon?

On 1.6.2021 18.35, Ullfig, Roberto Alfredo wrote:

> This has always been an issue for us. Whenever a user connects for the
> first time they get "certificate not trusted". Is this because the
> certificate is issued by:
>          Issuer: C=US, ST=MI, L=Ann Arbor, O=Internet2, OU=InCommon,
> CN=InCommon RSA Server CA
> So, most (maybe all) devices do not install the InCommon CA? What's the
> best solution for this? Should users manually install the InCommon CA
> first before connecting?

Martin already replied about the importance of server chain, so I'll
just one more thing we have seen also happening:

See the document below and look for 'Trust-On-First-Use' or 'TOFU':


The devices may still prompt the user even if the certificate chain is
correct. For example, even if the certificate chain is correct, the user
is required to accept that the name in certificate is something that's
expected. When this is done, the dialog doesn't re-appear until the
certificate changes.

I think the exact wording in the dialog is different when the
certificate chain is not complete as opposed to the case where the chain
is good but the certificate is now yet known.

To configure Radiator to send intermediate CA certificates, use
EAPTLS_CertificateChainFile parameter instead of
EAPTLS_CertificateFile parameter. The difference is that
EAPTLS_CertificateFile contains only the server's certificate. The chain
file starts with the server's certificate followed by one or more
intermediate CA certficates. These all need to be in PEM format.


You may already have the configuration set correctly and it's just the
TOFU prompts the clients display, but it might be useful to check that
the chain is correctly configured too.


Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.
radiator mailing list
radiator at lists.open.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20210602/f1ca1b03/attachment-0001.html>

More information about the radiator mailing list