Great, thanks. I am almost done and have written the basic components, adapting from my previous pull request on LPPE plus a number of test cases. I'll do a bit more clean up tomorrow and will do the first push. Other than exhaust testing LPPE to a reasonable degree, I see the following pending on the ldap todo list:
1. Removing spring ldap dependencies 2. Removing now-deprecated ldap classes that will no longer be in use. 3. Aligning the current ldap authentication handler with the current authentication hierarchy I have got a few extra questions on the mapping of exceptions to the flow, and will post them in a separate thread. Also, once the pending pull on the recent set of CS rules is pulled into master I'd like to merge and apply the same fixes to the authn api topic branch to reduce future maintenance. This might of course be the last item on the list, in the interest of time. Misagh > -----Original Message----- > From: Marvin S. Addison [mailto:[email protected]] > Sent: Monday, May 13, 2013 1:13 PM > To: [email protected] > Subject: Re: [cas-dev] Authn API Status > > > Just to clarify: are we pushing directly to the topic branch? > > In-progress code reviews as commits appear? > > Good question. I was thinking we'd follow the typical process of committing > to a personal repository and submitting pull requests, but in the interest of > time we may want to do that only for "big" changes or ones where the design > is less clear. Otherwise just push first and ask questions later. If we start > stepping on each other, we can reconsider. > > 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 -- 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
