In order for a client to use the CAS Server, no changes to the CAS Server are required. You need to configure the CAS clients themselves to provide a serviceUrl and the URLs to the CAS server. The documentation for each of the CAS Client implementations (Java, PHP) should explain how and where to configure these URLs.
What happens then is that when you attempt to access the protected client application, the CAS clients will detect this and redirect to the CAS server (to present the login screen or to participate in the SSO session).
-Scott
On 11/4/06, Greg Rank <[EMAIL PROTECTED]> wrote:
I have assembled and installed a suite of 6 web applications that I'd
like SSO for.
Three web apps are java and three web apps are php.
I've come across cas and here is what I have done so far:
I have downloaded your server sample and got it working on Tomcat. I
see a login page and can login.
I have read the docs on editing a web.xml for CAS in a java
application. It looks very simple
I have read the instruction for and downloaded the php files, it
looks fairly straight forward to me.
So my question is, how do I configure the 6 application URL's in the
server component (running on Tomcat) so I can click on a link and get
logged into each application? Is there a config file where I populate
the URL's to the cas login pages inside the server war or is this
done at the client level or both?
In other words, how does the server need to be configured to
communicate with the client or vice versa(I use client here to refer
to one of my six applications mentioned above)
?
Also each php and java app has it's own authentication mechanism,
i.e. currently a seperate
username and password are required for each
Thanks
Greg Rank
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
