mod_auth_cas and phpCAS don't mix. You can't run them both on the same context. mod_auth_cas will intercept the tickets etc. before they reach phpCAS. This is why phpCAS sends you in a loop..

To get the info from the apache in front you simply use the REMOTE_USER variable. You can also get more information from the CASAuthNHeader directive.

Cheers,

Joachim


Am 11.08.2010 14:47, schrieb Andrus Suitsu:

The moment I sent my question, I knew the answer. I needed to turn off
certificate checks. SIlly me!

My real problem though is not solved yet. The real problem is that while
Apache/mod_auth_cas authentication works now, I don't know how to use that
authentication information (or really the user attributes) in a JSP
application in Tomcat, which connects to the front-end Apache through AJP
protocol. To make things easier, I have tried to do this first in a phpCAS
application in Apache itself. This is my test file


<?php
include_once('CAS.php');

phpCAS::setDebug();
phpCAS::client(CAS_VERSION_2_0,'admin.prx',8443,'cas',false);
phpCAS::setNoCasServerValidation();

//phpCAS::forceAuthentication();
phpCAS::isAuthenticated();

?>
<html>
   <head>
     <title>phpCAS simple client</title>
   </head>
   <body>
     <p>the user's login is<?php echo phpCAS::getUser(); ?>.</p>
     <p>phpCAS version is<?php echo phpCAS::getVersion(); ?>.</p>
     <p>  ?logout= Logout</p>
   </body>
</html>


And what I get is this



the user's login is
phpCAS error: phpCAS::getUser(): authentication was checked (by
phpCAS::isAuthenticated() at /usr/share/php/CAS.php:1042) but the method
returned FALSE in /var/www/php/example.php on line 17

When I use forceAuthetnication it goes into redirect loop. Besides, I don't
want phpCAS to do authentication, because Apache's mod_auth_cas is already
doing that.

Is it something simple I am missing or maybe it is not possible to do what I
want?



--
Joachim Fritschi
Hochschulrechenzentrum (HRZ)
L1|01 Raum 248
Petersenstr. 30
64287 Darmstadt

Tel. +49 6151 16-5638
Fax. +49 6151 16-3050
E-Mail: [email protected]

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to