You should just use the Validation Filter (and Request Wrapper) in this instance. You'll need a way to "trigger" when to redirect to CAS.
On Mon, Aug 30, 2010 at 9:36 AM, Bryan Wooten <[email protected]> wrote: > We have several applications that allow both public and authenticated > access. > > > > For example our Class Schedule application is open to the world (http), but > if you are an authenticated student (https) you get some additional > features. Aside from http vs. https all the URLs are the same. > > > > I can’t seem figure out a way to make this work if I CASify the > application. It doesn’t seem to be possible to add protocol (http vs. https) > in the filter mappings which was my first idea. > > > > So my next idea was to add a filter before the CAS filters that would > simply fool CAS by adding a CasAssertion to the session if the protocol was > http. > > > > Does anyone have any other ideas on how to accomplish this? > > > > Bryan Wooten > > > > [email protected] > > Work: 801.585.9323 > > Cell: 801.414.3593 > > > > -- > 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
