I previously sent download statistics to CAS steering committee when we were considering pulling the source files for ClearPass into core.
These may or may not be the best numbers to determine usage, but they are unfortunately the only ones I have: (cas-server-support-ldap included for comparison purposes as allegedly a "popular" features): Last Month: cas-server-core: 961 cas-clearpass-webapp: 96 cas-server-support-ldap: 317 Last Year: cas-server-core: 10,810 cas-clearpass-webapp: 835 cas-server-support-ldap: 4776 Cheers, Scott On Wed, Apr 18, 2012 at 10:51 AM, Marvin S. Addison < marvin.addi...@gmail.com> wrote: > The driver for including ClearPass is experience with many enterprise >> deployments of CAS where more often than not the feature is required >> > > You'll need to back up that point with data. Until then it's simply a > feature of value to some deployers, while most don't need or want it. > Virginia Tech is squarely in that camp; we don't want any trace of this > feature in our deployed version of CAS. > > > (even for the venerable Rutgers deployment), coupled with the extra >> headaches derived from maintaining an external extension and the added >> maven overlay complexity. >> > > Simply including it in the CAS server codebase alleviates the first > headache, and the second is a fixed cost for anyone deploying CAS via maven > WAR overlay. So it's really a matter of whether we want to put the onus on > deployers to do more to enable this feature or disable it. > > The data I requested above should help make the case. If it turns out > there really are more deployers that use this in practice than those that > do not, then I'm willing to put the burden on those of us who want to yank > it out. May I suggest we develop a poll for this issue, in addition to > whatever data you may have from other sources, where we solicit feedback > from deployers via cas-user. > > I should point out that shipping with Clearpass enabled weakens one of the > value propositions in favor of CAS: it is a central, trusted authority for > handling primary credentials. That's stated implicitly on > http://www.jasig.org/cas/about and explicitly in Andrew's widely > circulated presentation on CAS, http://www.youtube.com/watch?** > v=Ik_11Y17ASg <http://www.youtube.com/watch?v=Ik_11Y17ASg>. We should > take this into consideration in our decision. > > > 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<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
