I agree with Scott. Configuring a support module should be a no-brainer. This is something i'm currently working on (for which version that's another story :) ) Deployment would be made only by adding a maven dependency to the cas server webapp pom.xml. All the configuration would be discovered in support module and plugged into the webapp configuration.
Frederic On Tue, Apr 24, 2012 at 4:40 PM, Scott Battaglia <[email protected]>wrote: > Does it make sense to reference the proxy chain in its own file so that > deployers don't actually have to modify the clearpass file (just copy it > over) ? > > i.e. they put the proxy chain in their deployer config ? > > On Tue, Apr 24, 2012 at 10:30 AM, Marvin S. Addison < > [email protected]> wrote: > >> The patch looks reasonable. I'd like to verify the deployer steps. >>> To deploy clearpass a deployer would: >>> >>> 1) add cas-server-extension-clearpass jar dep to the maven overlay >>> 2) move unused-spring-configuration/**clearpass-configuration.xml to >>> spring-configuration/**clearpass-configuration.xml >>> 3) configure allowedProxyChains for services authZ to use clearpass >>> 4) overlay web.xml with clearpass endpoints enabled >>> >>> Does that sound right? >>> >> >> That's correct. I'll address the dependency and allowedProxyChains >> issues, then issue a pull and assign to you. >> >> 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-dev<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
