Scott Evans wrote:
I wonder if you might consider putting the current release's javadocs
up on the project's home page?
I'd like to place a link directly to it in the javadocs for the
application that I am using acegi in.
--
Ben wrote:-snip-
Ive made isPasswordCorrect protected (see CVS). You should be able to subclass DaoAuthenticationProvider, override this method, and achieve the desired functionality. -snip-Thanks for doing this but I had problems with the Authentication object that DaoAuthenticationProvider retur
Hi,
I wonder if you might consider putting the current release's javadocs up on the project's home page?
I'd like to place a link directly to it in the javadocs for the application that I am using acegi in.
Thanks,
Scott
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
Randy Thornton wrote:
That is the best answer. Thanks.
If nobody has any concerns or objections, I'll make this change later
today. I'll leave User as the concrete implementation so nobody's
existing code breaks, whilst creating a UserDetails interface.
Just checked it the refactoring of U
Karel Miarka wrote:
I have downloaded and built the current CVS version and run all my
application test agains it. Everything is OK except one little backward
incompatibility:
when my old code (custom AccessDecisionVoter or Tapestry Engine) needs to
get the username of logged in user it calls auth.
Ben,
I have downloaded and built the current CVS version and run all my
application test agains it. Everything is OK except one little backward
incompatibility:
when my old code (custom AccessDecisionVoter or Tapestry Engine) needs to
get the username of logged in user it calls auth.getPrincipal()
