1. System Preparation

1.1. Install Debian 7

The first thing that is required is a Debian 7 machine - this can be physical or virtual.

1. Install Debian 7 (Wheezy) via usual mechanism (e.g netboot CD, ISO in VMware/VirtualBox or the DVD image.
2. Choose the following server install options: "Debian desktop, SSH server, Standard system utilities”.
3. Create/choose a secure root password and an initial system user account.
4. Once installed, make sure you run an apt-get update and apt-get upgrade to ensure your system is fully up to date.

1.2. Configure Debian 7

Next, there are a few Debian configuration options that need to be set in advance.

1.2.1. Networking configuration

For production deployments, it is recommended that the Moonshot APC be assigned a static IP address.

1.2.2. Firewall configuration

The following ports are required to be accessible from the outside world, both in local firewall and in any external firewalls:

• 2083/tcp (for RadSec connections to other Moonshot entities)
• 12309/tcp (for Trust Router client connections - if using the Trust Router to broker trust relationships between entities)

1.3. Add the Moonshot Repository

1. Add the Moonshot Debian Wheezy repository to your system. To do this, run the following command (as root, or using sudo):

   $ echo "deb http://repository.project-moonshot.org/debian-moonshot wheezy main" > /etc/apt/sources.list.d/moonshot.list

2. Install the Moonshot GPG key:

   $ wget -O - http://repository.project-moonshot.org/key.gpg | apt-key add -

3. Update the apt cache with the new repository information:

   $ apt-get update

2. Install the Software

We’re now ready to install the Moonshot software and its required dependencies. Install the software by running the following command:

$ apt-get install freeradius-abfab freeradius moonshot-gss-eap moonshot-ui moonshot-trust-router dbus-x11

3. Configure the Moonshot APC

Next, we need to configure the Moonshot APC.

3.1. Configure FreeRADIUS

3.1.1. Certificates

We need to get FreeRADIUS to create some private and public keys to use for its RadSec connections. Create and install the certificates by doing the following (as root).

1. Change into the /etc/freeradius/certs directory

   $ cd /etc/freeradius/certs

2. Edit the certificate generation properties in client.cnf, server.cnf, and ca.cnf as following:
   1. In the ca.cnf file:
      1. In the [ req ] section, add encrypt_key = no

      2. In the [CA_default] section, change the default_days from 60 to a higher number (this is how long the certificates you create will be valid for). When the certificates expire, you will have to recreate them.

      3. in the [ certificate_authority ] section, change all of the parameters to match those of your organisation. e.g.

         [certificate_authority]
         countryName             = GB
         stateOrProvinceName     = England
         localityName            = Camford
         organizationName        = Camford University
         emailAddress            = support@camford.ac.uk
         commonName              = "Camford University FR Certificate Authority"

   2. In the server.cnf file:

      1. In the [ req ] section, add encrypt_key = no
      2. In the [CA_default] section, change the default_days from 60 to a higher number (this is how long the certificates you create will be valid for). When the certificates expire, you will have to recreate them.

      3. in the [ server ] section, change all of the parameters to match those of your organisation. e.g.

         [server]
         countryName             = GB
         stateOrProvinceName     = England
         localityName            = Camford
         organizationName        = Camford University
         emailAddress            = support@camford.ac.uk
         commonName              = "Camford University FR Server Certificate"

   3. In the client.cnf file:

      1. In the [ req ] section, add encrypt_key = no
      2. In the [CA_default] section, change the default_days from 60 to a higher number (this is how long the certificates you create will be valid for). When the certificates expire, you will have to recreate them.

      3. in the [ client ] section, change all of the parameters to match those of your organisation. e.g.

         [client]
         countryName             = GB
         stateOrProvinceName     = England
         localityName            = Camford
         organizationName        = Camford University
         emailAddress            = support@camford.ac.uk
         commonName              = "Camford University FR Client Certificate"

         All of the organisation parameters (countryName, localityName, etc) need to match in the three .cnf files but the commonName must be unique in each file)

3. Clear out any old certificates in the directory

   $ make destroycerts

4. Run the bootstrap script to generate the certificates

   $ ./bootstrap

5. Create a file that is the concatenation of the certificate and private key of the client.

   1. Create the file

      $ openssl x509 -in client.crt > client.pem ; cat client.key >> client.pem

   2. Cerify that the client.pem file starts with "-----BEGIN CERTIFICATE-----".

3.1.2. Moonshot UI credential store

We need to enable the freeradius user to use the Moonshot UI flatstore:

$ echo "freerad" >> /etc/moonshot/flatstore-users

3.1.3. RadSec

Next we need to configure RadSec. We do this by creating a file at /etc/radsec.conf with the following:

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

3.1.4. Realm

We next need to configure your realm in the FreeRADIUS server so that it knows not to send any requests for your own users off to another server.

1. Configure your realm in /etc/freeradius/proxy.conf
   1. Open the file for editing and fine the line “realm example.com {“

   2. Above this, add the following, where YOUR_REALM should be substituted for the realm you intend to use for your APC:

      realm YOUR_REALM {
      	# Intentionally left blank
      }

3.1.5. EAP Type

1. Set the EAP type in use by moonshot (EAP-TTLS) by editing /etc/freeradius/mods-enabled/eap. Find the first instance of default_eap_type = md5 and change it to TTLS, i.e.:

default_eap_type = ttls

3.1.6. Resource Provider Authentication

4. Configure the Trust Router connection

The APC is fundamental to a Trust Router network, so the next step involves configuring the Trust Router client software and configuring its connection to a Trust Router.

4.1. Set up the FreeRADIUS and Trust Router users

We need to place the FreeRADIUS user and the Trust Router users into each other's groups to allow them to read each other's shared files.

$ adduser freerad trustrouter
$ adduser trustrouter freerad

4.2. Configure TIDS

The APC also runs the Temporary ID Server (TIDS).

1. Open the /etc/default/trust_router file for editing. If necessary, create it.

   ipaddr="[your server IP]"
   hostname="[your server hostname]"
   gssname="trustrouter@apc.moonshot.ja.net"
   
   TIDS_USER="trustrouter"
   TIDS_GROUP="trustrouter"

5. Testing

Now that we have the Moonshot IdP installed and configured, we're now ready to test!

5.1. Testing FreeRADIUS locally

The first test is to check whether FreeRADIUS is working in its most basic manner.

1. In window 1, run (as root user)

   $ freeradius -fxx -l stdout

2. In window 2, run (as root user)

   $ radtest testuser@YOUR-APC-REALM testing localhost 2222 testing123

   This uses the "radtest" utility which is used in the following way - radtest username password servername port shared-secret

3. If this is working correctly you should see something like the following:

   In window 1 - FreeRADIUS server output

   Sending Access-Accept of id 57 from 127.0.0.1 port 1812 to 127.0.0.1 port 33363
        Reply-Message = 'Hello test user. You have authenticated!'
   (1) Finished request 1.
   Waking up in 0.3 seconds.
   Waking up in 4.6 seconds.
   (1) Cleaning up request packet ID 57 with timestamp +94
   Ready to process requests.

   In window 2 - radtest client output

   Sending Access-Request of id 57 from 0.0.0.0 port 33363 to 127.0.0.1 port 1812
        User-Name = 'testuser'
        User-Password = 'testing'
        NAS-IP-Address = 127.0.1.1
        NAS-Port = 2222
        Message-Authenticator = 0x00
   rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=57, length=61
        Reply-Message = 'Hello test user. You have authenticated!'

5.2. Testing the Trust Router connection

To test the connection to Trust Router, we need to make sure the Temporary Identity Server (TIDS) software is running, then use the Temporary Identity Client (TIDC) software to simulate a connection to the Trust Router.

5.2.1. Starting the Temporary Identity Server (TIDS)

In window 3 (window 1 should still be still running the FreeRADIUS server and window 2 the radtest command), run the TIDS software:

$ tids [your server IP] testuser@YOUR-APC-REALM [your server hostname] /var/lib/trust_router/keys

trustrouter@apc.moonshot.ja.net is the identity that the trust router will use when provisioning keys - this makes it easy to spot in your own log files.
Specifying your server's IP and hostname may seem redundant (and for single server deployments, it is!). You'll need to set the hostname and IP arguments a little differently if you want to enable some more advanced configurations (such as load balancing and key sharing).

5.2.2. Run an APC authentication test

At this point, you must configure your trust router to use testuser@YOUR-APC-REALM as authentication.

1. The trust router configuration must be updated with the test user associated with your trust router's rp_realm filter lines.
2. The trust router configuration must be updated with your new APC designated as the APC for your trust router.
3. The trust router must have its Moonshot credential store updated with the test user and its password.
4. The trust router must be restarted. At this point, the trust router will attempt to authenticate itself to the APC.
5. In the FreeRADIUS console, you should see an Access-Accept response.

6. Next Steps

At this point, you now have a Moonshot APC that is working. Now for the next steps:

6.1. Automatically start the software

6.1.1. FreeRADIUS

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

$ sudo update-rc.d freeradius defaults

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

6.1.2. TIDS

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

$ sudo update-rc.d tids defaults
$ sudo service tids start 

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

6.2. Configure a real source of Authentication

Your FreeRADIUS server can currently only authenticate a single user - "testuser". At this point, you will want to connect to your management database. The FreeRADIUS site has information and instructions for how to do this.