Clearpass is currently disabled by default, in the sense that if you attempt to obtain the user's password using the default config, you'll simply receive a blank. The change is designed in such a way to facilitate the maven overlay process as much as possible, in that all components that are required for the clearpass integration are enabled and configured, except the metdadata populator element in the deployConfigContext.xml file [1]. (Around line 32)
So in order to truly turn on clearpass, an adopter using the overlay process would have to obtain a local copy of the xml file (which he/she already would have to, anyway, to do anything interesting), uncomment the appropriate section and rebuild. Regards, -Misagh [1] https://github.com/mmoayyed/cas/blob/master/cas-server-webapp/src/main/web app/WEB-INF/deployerConfigContext.xml From: Frederic Esnault [mailto:esnault.frede...@gmail.com] Sent: Monday, April 16, 2012 7:44 AM To: cas-dev@lists.jasig.org Subject: Re: [cas-dev] Recommend Clearpass Components NOT Enabled by Default +1 I was thinking it would be much easier for people to add a specific support just by moving a config file from unused to used. Or even better, just by adding the dependency to the webapp pom. It would require of course some wildcarded context imports, plus some dynamic configuration tricks (mapping handlers order for example). But it would be a nice to have. And would remove features activated by default. (For example an openid controller activated by default, looks weird at first glance :) ) Frederic On Mon, Apr 16, 2012 at 4:38 PM, Scott Battaglia <scott.battag...@gmail.com> wrote: +1 for disabling by default though we should make any configuration changes required to make integration easier for features like this going forward (i.e. instead of registering specific urls in web.xml, should we switch to using wildcards? <-- if we haven't already, I can't remember :-))) On Mon, Apr 16, 2012 at 10:32 AM, Marvin S. Addison <marvin.addi...@gmail.com> wrote: Clearpass components are presently enabled in the default CAS webapp in master: https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp /WEB-INF/web.xml https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp /WEB-INF/spring-configuration/clearpass-configuration.xml https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp /WEB-INF/spring-configuration/securityContext.xml (There may be others; these were readily apparent.) While we agreed to bring clearpass integration into core, I thought we were in agreement that it should be disabled by default. I'm strongly +1 in disabling those by default. Keeping with previous convention, all clearpass integration should live in unused-spring-configuration/clearpass-configuration.xml so it's available to be enabled in an overlay but disabled by default. In places where it cannot be divested into separate configuration, it should be commented out (e.g. web.xml). M -- You are currently subscribed to cas-dev@lists.jasig.org as: scott.battag...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: esnault.frede...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: mmoay...@unicon.net To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@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-dev
