So our status pages require authentication (and have an additional authorization layer that uses cas's saml attributes). I don't understand how the gateway feature would help in this case.
-- Curtis Ruck Anytime: 210-857-1126 On Mon, Jan 14, 2013 at 4:03 PM, Marvin Addison <[email protected]>wrote: > > Has anyone setup a monitoring solution (i.e. Nagios, Zabbix, Icinga, > etc...) to monitor page content for CAS secured applications? We've got a > few CASified web applications that have their own status pages, that we'd > like to start monitoring, but most solutions can't authenticate to CAS > enabled urls. > > A couple options: > > - Most status pages don't require a user authentication context, so > can be protected outside of the scope of CAS. Simply don't put the > status endpoints behind CAS. > - Leverage the gateway feature of CAS to access the status page. > > M > > -- > 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
