> Since Google SAML2 and CAS Attributes SAML1 really are quite different > animals, it probably is worth thinking about two separate modules. > Perhaps something like this: > * cas-server-support-google-saml2 > * cas-server-support-attributes-saml1
I think there's negligible value for the effort of splitting into two modules. While the features are likely separate in terms of consumption by deployers, they _should_ have exactly the same dependencies on OpenSAML. +1 for Jérôme's initial suggestion of a single cas-server-support-saml module. I'm ambivalent on pulling out the single sign-out features. I would favor it only if it makes sense in terms of dependencies and effort, not otherwise. I'm additionally ambivalent on disabling by default. I do, however, think it remains to be demonstrated with evidence (vote, folks speaking up) about the extent of use of single sign-out. Judging by amount of questions on cas-user, it's a widely used feature; percent use remains to be determined. 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
