[cvs] [Wiki] changed: CASAuthHowTo

[Wiki Guest]

guest [134.58.253.114]  Tue, 20 Jun 2006 23:55:35 -0700

Modified page: http://wiki.horde.org/CASAuthHowTo
New Revision:  1.2
Change log:  typo

@@ -1,7 +1,5 @@
 + CAS Authentication !HowTo
-
-++ WORK IN PROGRESS
 
    Jan Van der Velpen aka Velpi (who did all the work)
    Peter Arien aka Kaos99 (who just likes playing around with Horde)
   Thanks go to the [http://www.ja-sig.org/products/cas/ Ja-Sig] and the [http://esup-portail.org/consortium/espace/SSO_1B/tech/cas/cas_install.html ESUP] people!!
@@ -9,9 +7,9 @@
 [http://www.kuleuven.be/ Our university] is working towards a complete AAI (Authentication and Authorization Infrastructure) implementation. For web applications we are using the [http://shibboleth.internet2.edu/ Shibboleth architecture]. But as you can read in [ShibbolethAuthHowTo the Shibboleth Authentication HowTo],  a big problem with AAI and webapplications is authentication on the backend (with Horde/IMP that would be the mailservers). What we needed was a way to prevent the password passing the webmail servers AND the mailservers.
 
 Enter CAS. 
 
-We chose to use CAS (http://www.ja-sig.org/products/cas/index.html) as an authentication mechanism on top of Shibboleth. Because both Shibboleth and CAS do the initial authentication at the CAS server, users will see it is one integrated SSO system.
+We chose to use CAS (http://www.ja-sig.org/products/cas/index.html) as an authentication mechanism on top of Shibboleth. Because both Shibboleth and CAS do the initial authentication at the CAS server, users will see it as one integrated SSO system.
 
 First we used the ESUP pam module (referenced [http://www.ja-sig.org/wiki/display/CAS/PAM+Module here]) to let our mailservers use the CAS server as a possible authentication service. Here's how the cas lines in our mailserver pam-config looks like:
 {{/etc/pam.conf:}}
 <code> imap    auth    sufficient      /usr/lib/security/pam_cas.so -simap://127.0.0.1 -f/etc/pam_cas.conf