On this page you will find instructions on how to create a static connection to a Moonshot Identity Provider (IdP) without the need to access the Trust Router infrastructure for realm information.

Contents

In the example configuration information that follows, we shall refer to the organisation that owns the Moonshot IdP as Camford University and the IdP itself by its IP address, 192.168.213.24.

RadSec

Because this connection continues to use RadSec, we still have to request several files from Camford University, namely the Certificate Authority (CA) file for Camford (ca.pem), and the Client Certificate (client.pem) and private key (client.key) for use with their Moonshot IdP.

Preparing the certificates

If Camford University used our instructions to create an Identity Provider, the Client Certificate and its private key are in the same file, client.pem

If Camford University sent us three files, we'll create a combined file of the Client Certificate and its private key:

$ cat client.key >> client.pem

Verify that the client.pem file starts with "-----BEGIN CERTIFICATE-----" and ends with "-----END ENCRYPTED PRIVATE KEY-----".

Storing the certificates

Because the certificates are only used by FreeRADIUS, it is best if you store the certificates in FreeRADIUS' certs directory.

Be aware that running the make destroycerts command in the FreeRADIUS certs directory will also erase these certificates!

Rename the files from ca.pem and client.pem to an easily-recognisable name, such as camford_moonshot_ca.pem and camford_moonshot_client.pem.

FreeRADIUS configuration

In the FreeRADIUS configuration, we can define a single file that contains everything about the RadSec connection to the Moonshot IdP:

Create a new file in the FreeRADIUS sites-available directory (/etc/raddb/sites-available on RedHat/CentOS/Scientific Linux, /etc/freeradius/sites-available on Debian/Ubuntu) called camford_moonshotidp with the below contents:

If you stored the certificates for the Moonshot IdP somewhere else, you must adjust the private_key, certificate_file and ca_file entries with appropriate paths. The ${certdir} and ${ca_dir} directives refer to the FreeRADIUS certs directory. You should not need to change those directives.

To enable this configuration, it needs to be linked into the FreeRADIUS sites-enabled directory: