tids takes gss_id

[devwiki.git] / trustrouterinfo.mdwn

diff --git a/trustrouterinfo.mdwn b/trustrouterinfo.mdwn
index 40d7c1f..0ddacc3 100644 (file)
--- a/trustrouterinfo.mdwn
+++ b/trustrouterinfo.mdwn
@@ -1,4 +1,4 @@
-BUILDING/INSTALLING A TRUST ROUTER:
+<h2>BUILDING/INSTALLING A TRUST ROUTER</h2>
 
 (Assumes you already have a Moonshot DVD installed.)
 
@@ -10,7 +10,7 @@ The Trust Router depends on MIT Kerberos, OpenSSL, jansson and SQLite Version 3.
 
 To build and install a Trust Router, you need to separately 'make' and 'make install' in both the moonshot/trust_router and moonshot/freeradius-server directories, in that order.
 
-CONFIGURING A TRUST ROUTER:
+<h2>CONFIGURING A TRUST ROUTER</h2>
 
 In addition to having a valid freeradius TLS/PSK configuration, a set of Trust Router and TID-specific configuration is required in order to use the Trust Router.
 
@@ -21,15 +21,15 @@ The TIDC also requires specific configuration in the freeradius raddb/mods-avail
 
 For example:
 
-realm suffix {
-        format = suffix
-        delimiter = "@"
-        default_community = "testing.communities.ja.net"
-        rp_realm = "painless-security.com"
-        trust_router = "10.0.2.15"
+realm suffix {<br/>
+        format = suffix<br/>
+        delimiter = "@"<br/>
+        default_community = "testing.communities.ja.net"<br/>
+        rp_realm = "painless-security.com"<br/>
+        trust_router = "10.0.2.15"<br/>
 }
 
-BRINGING UP/VERIFYING A TRUST ROUTER:
+<h2>BRINGING UP/VERIFYING A TRUST ROUTER</h2>
 
 To run all of the components needed to test the Trust Router, you will need to have at least two different nodes (or VMs) at different IP addresses.
 
@@ -37,36 +37,44 @@ On one node, you will run the IDP AAA Server and the TIDS.  The TIDS must run on
 
 Before running the IDP AAA Server, you will need to configure freeradius to use the SQL key database that will be shared with the TIDS.  This can be done by adding a file called 'psk' to the /etc/freeradius/mods-enabled directory with the following contents:
 
-sql psksql {
-driver = "rlm_sql_sqlite"
-filename = "/var/tmp/keys"
+sql psksql {<br/>
+driver = "rlm_sql_sqlite"<br/>
+filename = "/var/tmp/keys"<br/>
 }
 
 You will also need to add 'psksql' to the existing 'instantiate' section in etc/freeradius/radiusd.conf.
 
 Before running TIDS for the first time, create the SQL database using the following commands:
 
-sqlite3 /var/tmp/keys
-sqlite3>  create table psk_keys (keyid text primary key, key blob);
+sqlite3 /var/tmp/keys<br/>
+sqlite3>  create table psk_keys (keyid text primary key, key blob);<br/>
 ^D
 
-Start the freeradius server (on Node-2, as root):
+Start the freeradius server (on Node-2, as root):>
+
 root@debian:/opt/moonshot/sbin# ./radiusd -fxx -l stdout
 
 Start the TID Server (on Node-2, as root):
-root@debian:/opt/moonshot/bin# ./tids 10.1.10.90 /var/tmp/keys
+
+root@debian:/opt/moonshot/bin# ./tids 10.1.10.90 gss_id /var/tmp/keys
+
+The gss_id is the GSS name that will be used by the trustrouter to connect to the TIDS.  For example if trustrouter@apc.painless-security.com is provisioned as the identity, then enter trustrouter@apc.painless-security.com.
 
 On the second virtual machine, you will run the freeradius RP AAA Proxy (with built-in TIDC), the Trust Router, the GSS Server and the GSS Client.  For example:
 
 Starting the freeradius RP AAA Proxy (on Node-1, as root):
+
 root@moonshot-proxy:/usr/local/sbin# ./radiusd -fxx -l stdout
 
 Starting the Trust Router (on Node-1, as root):
+
 root@moonshot-proxy:/home/margaret/moonshot/trust_router/tr# ./tr 
 
 Starting the GSS server (on Node-1, as root):
+
 root@moonshot-proxy:/home/margaret# gss-server host@localhost
 
 Starting the GSS client (on Node-1, any user):
+
 margaret@moonshot-proxy:~$ gss-client -spnego 127.0.0.1 host@localhost "test message"