Thank you.
/M
Am 27/05/2010 20:28, schrieb Todd Orr:
I exported all the data access code into an independent DAO that is still
managed by Spring. Then I added a constructor to my UserDetailsService that
took the dao plus the salt and encoder:
private final static Logger LOG =
LoggerFactory.g
I exported all the data access code into an independent DAO that is still
managed by Spring. Then I added a constructor to my UserDetailsService that
took the dao plus the salt and encoder:
private final static Logger LOG =
LoggerFactory.getLogger(UserDetailsServiceImpl.class);
private final Da
Just for the records. What did you change now?
Am 27/05/2010 19:48, schrieb Todd Orr:
I changed the code so that these are injected and now it works. I cannot
describe how angry this makes me. Days wasted.
Thanks for you help though!!!
---
I changed the code so that these are injected and now it works. I cannot
describe how angry this makes me. Days wasted.
Thanks for you help though!!!
On Thu, May 27, 2010 at 1:37 PM, Todd Orr wrote:
> My UserDetailsService is managed by Spring and as such I can't inject the
> same exact instanc
Did you debug down to the point where the compare of the credential to
the stored pwd happens? Are they really the same?
Am 27/05/2010 19:37, schrieb Todd Orr:
My UserDetailsService is managed by Spring and as such I can't inject the
same exact instances that tapestry is using, but I do use the
My UserDetailsService is managed by Spring and as such I can't inject the
same exact instances that tapestry is using, but I do use the same types,
PlaintextPasswordEncoder and SaltSourceImpl.
UserDetailsService:
private final static Logger LOG =
LoggerFactory.getLogger(UserDetailsServiceImpl.cl
What about the salt. Did you change it? You have to 'save' password with
your PasswordEncoder prior to using it.
Which Am 27/05/2010 19:20, schrieb Todd Orr:
I've tried that way as well. It doesn't work either and I assume it's for
the same reason, though I cannot tell in that case because the
I've tried that way as well. It doesn't work either and I assume it's for
the same reason, though I cannot tell in that case because the exception
doesn't bubble out of Tapestry Spring Security.
Login code:
private final static Logger LOG = LoggerFactory.getLogger(Login.class);
@Inject
@Value("
Why do you try to do the work of Spring Security? Please follow the
sample in [1]. There's no need to check the credentials on your own. You
just need to provide your implementation of UserDetails.
[1] http://www.localhost.nu/svn/public/tapestry-spring-security-sample/
Am 27/05/2010 16:53, sch
