> My thoughts on this is that a new guest method needs to be created in the > CAS clients that check the browser's user agent.
Ignoring John's warnings about bifurcated content, you could create a trivial servlet filter containing header examination logic that sits in front of the CAS AuthenticationFilter. The simplest implementation would simply bypass execution of downstream filters, including the AutethenticationFilter that is responsible for the CAS redirect. That might require some creative filter ordering, but should work in a large number of cases. In any case I don't think this functionality belongs in the CAS client. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
