For me I think it comes down to expectations. I was surprise, and confused for a bit, when I set the Can't Proxy option, yet was still getting proxy tickets.
If you setting this option against a live services, I imagine that folks would expect the user experience to get interrupted. I suppose there could be and option for a hard/soft set. Bill On Mon, Aug 1, 2011 at 9:28 PM, Scott Battaglia <[email protected]> wrote: > I'm on the fence on this. On the one hand, you'll interrupt the user's > experience. On the other hand, its probably technically more correct to > disable it (or at least put a note that says that these items take affect > going forward and do not affect existing sessions) > > On Mon, Aug 1, 2011 at 5:16 PM, William G. Thompson, Jr. <[email protected]> > wrote: >> >> Folks, >> >> Ran into what may be an edge case, but likely easy to fix. Would >> like to get your thoughts prior to filing a jira. >> >> I'm using a sample CasApp that can get a PGT and PT for targetService. >> Everything working fine. >> >> * enable Services Management with proper config, everything still working >> fine. >> >> Test Case (edge case?): >> * Login in to CasApp (get PGT), then disallow proxy on CasApp via >> Services Management. >> * (haven't logged out of CasApp yet), still fetching PTs with the >> previously received PGT. >> >> Should CAS stop issuing PTs for a PGT from a service that has been >> marked as not allowed to proxy in Services Management? >> >> Bill >> >> -- >> 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-dev > > -- > 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-dev -- 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-dev
