Home › Forums › Luminis Platform / System

CAS in Parallel Deployment

Fri, 2007-08-10 17:31 — kbell

Has anyone successfully configured CAS in Parallel Deployment?

We are trying. It is slow and painful. The current error seems to be with the secure cookie CAS needs - usidsec. We can see the cookie from the browser but the web server can't read it.

Any suggestions?

Thanks,
Karen
University of Memphis

0
No votes yet
‹ Channel Migration Role based icons in Lum IV question ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Fri, 2008-03-21 14:33 — mchildress

CAS in Parallel Deployment

Were you able to figure this out Karen? We are just getting organized to get a parallel deployment going and looking at possible CAS. - Mike

Thu, 2008-05-01 06:54 — babraa

cas install in 3.3.x in PD setup

hello
We've followed the instructions for a parallel deployment in the install.pdf doc but it doesn't seem to work.
The instructions seem to say to only install on the resource tier but this seems to be somewhat lacking when you have front end servers taking the requests?
Thanks for any pointers
Nomit

Thu, 2008-05-01 14:33 — ToddTrann

Our local docs

Yes, it may seem strange, but it is correct to only install the CAS package on the resource tier. We do have CAS up and running in 3.3.3 PD, here is a copy of our local docs:

1. Must remove any existing patch, prior to install of CAS.
# patchcp -l
luminis-3.3.3.0
luminis-3.3.3.142

# patchcp -u luminis-3.3.3.142

2. Mount the Luminis 3.3.1 iso filesystem in /tmp/luminis

3. Create /home/luminis/cas.conf installation config file containing this line:
install.packages=cas

4. Install the cas package (as root) on resource tier:

# cd /tmp/luminis
# . /opt/pipeline/.cprc
# ./setup /home/luminis/cas.conf

5. Unmount the luminis iso
# umount /tmp/luminis

6. Now login as luminis and edit $CP_ROOT/webapps/luminis/WEB-INF/web.xml.
Find the Session event notification section and change the param-value to
"remote-provider". When you're done, it will look like this:

<context-param>
<param-name>com.pipeline.cas.sessionEventNotification</param-name>
<param-value>remote-provider</param-value>
</context-param>

7. Add these two configman settings:

configman -s remotesessioneventlistener.0.url https://resourcemachine.your.edu/cp/cas/sessionEventNotify
configman -s cas.fqn resourcemachine.your.edu

8. Edit the login-cp.jsp file, since it is set up for single server not PD. Need to replace the
resource tier URL with the actual web front URL to the portal:

# cd /opt/pipeline/webapps/luminis/cas
# vi login-cp.jsp

response.sendRedirect(
/*URL*/ "https://webfront.your.edu/cp/home/displaylogin?goto=https://" +
casHost + "/cp/cas/login" + query );

9. Re-patch Luminis back up to previous level

10. Stop and start Luminis (webservers and resource tier).