https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/part-networking

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/index

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:

yum install trust_router moonshot-noshib

[...]
OpenGPGCheck = yes

# Blacklisted packages
#
BlackList = nspluginwrapper, valgrind, strace, mono-core, trust_router

# Process crashes in executables which do not belong to any package?
#
ProcessUnpackaged = no
[...]

2. Configure Trust Router

Next, we need to configure the Trust Router.

2.1. RadSec

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.

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:

realm gss-eap {
	type = "TLS"
	cacertfile = "/etc/pki/certs/tr-ca.pem"
	certfile = "/etc/pki/certs/tr-client.pem"
	certkeyfile = "/etc/pki/private/tr-client.key"
	disable_hostname_check = yes
	server {
		hostname = "YOUR_APC_HOSTNAME"
		service = "2083"
		secret = "radsec"
	}
}

Then check the file and the certificates can be read by the Trust Router user:

sudo su - --shell=/bin/bash trustrouter
cat /etc/radsec.conf
cat /etc/pki/certs/tr-*.*
cat /etc/pki/private/tr-*.*

2.2. Trust Router

2.2.1. Daemon Configuration

Your Trust Router will need to have a few core configuration items set. To do this:

1. Open the default instance's main configuration file at /etc/trust_router/conf.d/default/main.cfg for editing.
   
   1. Change the hostname to the (fully qualified) hostname of your Trust Router.
2. Open the /etc/sysconfig/trust_router file for editing. Make sure the configuration items are correct. Items you will most likely have to change are:

   • TR_DEFAULT_TEST_ACCEPTOR - this will need to be set to the (fully qualified) hostname of your Trust Router.

   • TR_DEFAULT_TEST_RPREALM - this will need to be set to the (fully qualified) hostname for your APC.

   • TR_DEFAULT_TEST_COMMUNITY - this will need to be set to the (fully qualified) hostname for your APC.

   • TR_DEFAULT_TEST_REALM - this will need to be set to the (fully qualified) hostname for your APC.

2.2.2. 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.

1. Import it using the moonshot-webp command (as the trustrouter user):

   su - --shell=/bin/bash trustrouter
   moonshot-webp -f [path to credential file]

   The credentials file will be given to you by the administrator of the APC.

2.2.3. Shibboleth

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:

1. Open /etc/shibboleth/console.logger for editing.

2. Change WARN to NONE on the first line, i.e.

   log4j.rootCategory=NONE, console

2.2.4. Default Peer

If your Trust Router 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:

1. Open /etc/trust_router/conf.d/default/peering.cfg for editing. Change the content as follows:

   {
   "default_servers": [
    "[hostname of trust router]"
    ]
   }

   If the /etc/trust_router directory does not exist, you may need to create it yourself, along with the subdirectories mentioned.

   Example

   If you were configuring your default Trust Router peer to be Janet's Trust Router at tr.moonshot.ja.net, its peering.cfg file would look like this:

   {
   "default_servers": [
    "tr.moonshot.ja.net"
    ]
   }

2.2.5. Configure your Trust Router

A trust router requires a trust configuration to function correctly. See the trust configuration file for more information.

Place an appropriate trusts.cfg file info the /etc/trust_router directory and symbolically link it into the default configuration directory:

cd /etc/trust_router/conf.d/default
ln -s ../../trusts.cfg

2.2.6. Start your Trust Router

You are now ready to restart your Trust Router and test it. To do this:

1. As root, start the Trust Router daemon:

   service trust_router start

3. Testing

To test your trust router, you should attempt a TIDC request on a Moonshot service connected to your trust router. If you have defined a default peer, the TIDC request may take a little longer, but it should succeed.

If it fails, please contact us.

4. Next Steps

At this point, you now have a Trust Router.

4.1. Automatically start the software

4.1.1. Trust Router

To automatically start Trust Router, issue the following command (as root):

chkconfig trust_router on
service trust_router restart 

If this is working correctly, you should see trust_router running as a daemon process.