Marvin, thanks for you answers.
In the mean time I managed to get it working with the LDAP examples, but instead of my calling LDAP I call our PostgreSQL database. May be I am just simple minded, but wouldn't a good interface solve this problem? Then you inject a bean of some sort that can return the right information back instead of just true/false (may be a bean of some sort). Anyways, I think I will get it going now. The other samples in the LDAP also shows nicely how to handle off-hours and this seems to work just fine… Need to do more testing ofcourse… When 3.5 is out, I will just merge my code Ries On Feb 3, 2012, at 9:59 AM, Marvin Addison wrote: >>> https://github.com/Jasig/cas/tree/feature-lppe >> >> I will take a look there, is the lppe branch going to be the new 3.5 version, > > Strictly speaking, no. The plan at present is to merge the LDAP > password policy support in that branch into master so it's included in > the 3.5 release. > >> in other words… Would I have to change (a lot??) of code when I use lppe >> now and want to change to 3.5? > > You'd need to _add_ and likely change a lot of things to support a > database backend. It's simply not designed with anything but LDAP > (and Active Directory in particular) in mind. I think that's a loss, > but I've been out-voted. The thinking is that it's better to ship > something now with limited functionality and build out later. > > 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-user > -- 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-user
