Off the top of my head, the simplest way would be if they were chained, but then you would be limited to only looking up the chain (i.e. C -> B -> A). If you try and look at more than one it becomes too complicated.
On Nov 29, 2007 11:25 AM, Christopher Brooks <[EMAIL PROTECTED]> wrote: > Scott, > > > They don't need proxying. Let's suppose the following exists: > > > > Application A -> Utilizes CAS A > > Application B -> Utilizes CAS B > > > > If a user attempts to access Application A, he (or she) will be > > redirected > > to CAS A to authenticate and then (assuming success) sent back to > > Application A. > > Ok, this sounds good, and clarifies things up a bit. My current dilemma > is > that I actually have several other CAS systems they might have signed on > to. > I have an institutional one (CAS A), a departmental one (CAS B), and a > special applications one (CAS C). > > Now, the person may have used an application (A, B, or C) and been > authenticated against any of these. They now come to use application D > which uses my CAS D implementation - what's the best way of querying these > other services to see if they are already authenticated with them? > > Wrt to the gateway feature - if I enable this I should be able to > interrogate the list of cas gateway cookies this browser has, then > identify > which CAS server I should forward to (with return to my service)? > > Chris > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
