Application sessions are typically independent of CAS WebSSO Session (i.e. TGT expiration policy), so you can configure them to be anything you want.
If you want to force an authentication challenge, have webApp2 opt-out of WebSSO by using renew=true. Bill On Wed, Aug 15, 2012 at 12:12 AM, Roberto Carlos González Flores < iscrobertogonza...@gmail.com> wrote: > Hi guys, > > I was wondering if its doable to implement a dynamic ticket expiration > policy according to the serviceClient. > > I mean, > > for webApp1 , I want to configure 2 hours for the timeout > for webApp2, I want to configure 1 minute because is on the same portal > but the information is more confidential. > for webApp3, a different value. > > Does cas support a similar behavior, out of the box? > > Does someone knows of a good example? > > If not, It is doable?, maybe with a CustomTimeoutExpirationPolicy that > reads the timeout value for each service from X repository ( e.g. a custom > webservice REST) and assign that value with the ticket > > -- > Carlos > > -- > You are currently subscribed to cas-user@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to cas-user@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-user
