Hi Don, You should be able to get the CAS server to behave that way you described, but how will a UA ever get authenticated if CAS server always send them back to the Service. Can you elaborate a bit on your scenario and the rationale?
Cheers, Bill -- William G. Thompson, Jr. Senior Technologist - Development Information Systems Office of Development, Princeton University voice: 609.651.0420 | [email protected] On Fri, Jun 5, 2009 at 3:56 PM, Don Rea, Web Application Developer<[email protected]> wrote: > Greetings all, > > At Bucknell we're still pretty new to CAS, and not entirely familiar with > all the jargon, so I hope I'm asking this in a way that makes sense. What > I'd like to do is have a CAS client find out if the user agent has been > previously authenticated, but have CAS not present the login form if it > hasn't. That is, if the UA is authenticated, send it back with a ticket, but > if it hasn't, just send it back. Is this possible? > > I've tried searching on this, but there are so many ways to phrase it I'm > not at all confident my lack of search results has any meaning. > > ______________________________________________________ > > Don Rea <[email protected]> (570) 577-3278 > Web Application Developer > Bucknell University Library and Information Technology > ______________________________________________________ > > 'In theory, there is no difference between theory and practice; > in practice, there is.' > --Chuck Reid > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
