1. Install Trust Router
We’re now ready to install the Trust Router software and its required dependencies. Install the software by running the following command:
2. Configure Trust Router
Next, we need to configure the Trust Router.
2.1.1. APC TLS
First, you will need a copy of a client key and certificate (and appropriate CA) from the APC(s) that your Trust Router serves. Copy them onto the filesystem of your Trust Router.
You can put these files anywhere on the file system, but this guide assumes you put them in /etc/pki/tls. If you place them in a different location you will need to change the locations below as appropriate.
2.1.2. Connection to APC
Next, we need to configure the RadSec configuration for the APC. We do this by creating a file at
/etc/radsec.conf with the following:
2.2. Trust Router
2.2.1. Moonshot Configuration
Moonshot, you say? Yes, Trust Router uses Moonshot to authenticate and secure all communications between Trust Router clients and servers. So, you will need to configure the trust router user to make use of the Moonshot flatstore (i.e. telling Moonshot that this is a special system account, not a regular user account), and you will need to import a set of credentials for your Trust Router to use.
Enable the trustrouter user to use the Moonshot UI flatstore:
Import it using the moonshot-webp command (as the trustrouter user):
The credentials file will be given to you by the administrator of the APC.
Shibboleth, you say? Yes, Shibboleth is used by the Moonshot components to be able to deal with incoming SAML. However, this feature typically isn't used in Trust Router, but its logging will appear in your Trust Router's log files. So, to simplify your log files, it is recommended that you silence the Shibboleth logging. To do this:
Change WARN to NONE on the first line, i.e.
2.2.3. Default Peer
If your Trust Router is going to run in its own, standalone, trust network, then you can skip this step. If it is going to run in a wider trust network, then you can configure your Trust Router's default peer - i.e. the Trust Router it sends its clients to when they ask it to locate a Moonshot entity that your Trust Router doesn't know about. To do this:
/etc/trust_router/conf.d/default/peering.cfgfor editing. Change the content as follows:
/etc/trust_routerdirectory does not exist, you may need to create it yourself, along with the subdirectories mentioned.
If you were configuring your default Trust Router peer to be Janet's Trust Router at tr1.moonshot.ja.net, its
peering.cfgfile would look like this:
Place an appropriate
trusts.cfgfile info the /etc/trust_router/ and symbolically link it into the default configuration directory:
- Place an appropriate
main.cfgfile into /etc/trust_router/conf.d/default/
main.cfgsets up a few internal variables, including the hostname that the trust router is running on.
2.2.4. Start your Trust Router
You are now ready to start your Trust Router and test it. To do this:
As trustrouter user, change to the constart the Trust Router :
Debian currently has no initscript for trust_router so it needs to be run manually. We hope to fix this in the near future.
Default should work, tr-test shouldn't.
4. Next Steps
At this point, you now have a Trust Router. Blimey.
/etc/trust_router/trusts.cfg with trust config