From abe4a613c727c85611c4171d95ec70513822db85 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmF293QIINb35puIE44kcDsoUHIhUGyq84" Date: Tue, 1 Nov 2011 07:29:01 -0400 Subject: [PATCH] --- ConfiguringRHEL.mdwn | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/ConfiguringRHEL.mdwn b/ConfiguringRHEL.mdwn index 96c5f30..07b648f 100644 --- a/ConfiguringRHEL.mdwn +++ b/ConfiguringRHEL.mdwn @@ -168,19 +168,17 @@ In the demo we just use a very simple example – mapping the _Chargeable-User-I Delete _/etc/shibboleth/attribute-map.xml_ and replace it with: - In this case, 89 corresponds to _Chargeable-User-Identity_, which is mapped to _local-login-user_, which sets the local account that the user will be given access to. -To load the moonshot extensions, under the root node in /etc/shibboleth/shibboleth2.xml, add: +To load the moonshot extensions, under the root node in _/etc/shibboleth/shibboleth2.xml_, add: - Further down the same file, find this line: @@ -207,15 +205,15 @@ This file tells moonshot what encryption options are valid for use with GSS. ##Testing Functionality As mentioned earlier, we will be using the Kerberos test tools to make sure that things are working.
-To start the gss-server, run: +To start the _gss-server_, run: /opt/moonshot/sbin/gss-server host@localhost & -There are two ways to start gss-client – the first specifies an encryption method to use by its OID 1.3.6.1.4.1.5322.22.1.18 (as seen in /etc/gss/mech): +There are two ways to start _gss-client_ – the first specifies an encryption method to use by its OID 1.3.6.1.4.1.5322.22.1.18 (as seen in /etc/gss/mech): /opt/moonshot/bin/gss-client -mech "{1 3 6 1 4 1 5322 22 1 18}" 127.0.0.1 host@localhost bar -The second uses Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)
-This chooses the "best" mutually-agreeable encryption method for between client and server. To invoke the client using SPNEGO, use: +The second uses __Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)__
+This chooses the "best" mutually-agreeable encryption method for between client and server. To invoke the client using __SPNEGO__, use: /opt/moonshot/bin/gss-client -spnego 127.0.0.1 host@localhost bar ##Sample Output @@ -246,7 +244,7 @@ This chooses the "best" mutually-agreeable encryption method for between client Signature verified. NOOP token -Running _gss- client produces_ a massive amount of output.
+Running _gss-client_ produces a massive amount of output.
The important part is at the end – you should see output similar to what is on the previous slide.
If you do not see the line: Attribute local-login-user Authenticated Complete -- 2.1.4