CAS Behind Apache HTTPD

[Smith, Matt]

Bill-
  Most of my CAS protected apps are tucked away behind Apache.  I've been using the stock Yale Java client for a while, and have recently tried out the JA-SIG client, both with success in this configuration.  I have not (yet) tried the Acegi client.  Essentially, the mod_jk or mod_proxy_ajp that you are using to forward the requests from Apache to Tomcat's AJP port (generally 8009) just does the *Right Thing* for you as far as URL mapping goes.

HTH,
-Matt



-----Original Message-----
From: cas-bounces at tp.its.yale.edu on behalf of Bill Bailey
Sent: Thu 2007-08-16 16:06
To: Yale CAS mailing list
Subject: CAS Behind Apache HTTPD
 
Hi,

 

I have CAS configured and running under Tomcat and so far all is well.
However, in production we will be introducing Apache HTTPD in between
the users and Tomcat. All requests will come in on port 80 or 443 to
Apache HTTPD which will forward the requests to Tomcat where necessary.
I should also note that we are using ACEGI security as well.

 

In theory, this doesn't seem like it should cause any problems, but
since CAS is heavily reliant on HTTPS and ACEGI requires URL's to be
configured in numerous places, I sense at least the potential for
problems in getting the setup right. Is anyone else running in a similar
configuration? Does anyone have any experiences to report or warnings or
suggestions?

 

Thanks.


Bill Bailey

Senior Developer / DBA
Northland, A Church Distributed