> I appreciate the alternative work that Marvin put forth and agree with > the goal of supporting password expiration with a broader view than > just LDAP.
That's good to hear. > However, the proposed alternative is too sweeping a change > for 3.5 based on the release strategy. That's too bad, but it's easy to admit that it was a stretch. My motivation for this work relied on leveraging the needs and interest for LDAP password expiration to drive some big API changes. I'm concerned that the API changes that I've sketched out will _never_ happen without some strong driving force, and that will be a big loss. 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
