Well, that did help. Somehow, as it left me even more confused at the
beginning. Debugging activated, I came to realize, that the
loadByUsername method in the UserDetailsServiceImpl never even is called
on Login.
So, knowing that I started to mock around in the AppModule and pushed
things aro
My advice is to debug your application to check if the password encoding at
login time is the same as the one you provided at creation time.
Put a break point in the method that retrieves the user from DB, have a look
the stack in eclipse debug mode, identifiy the Authentication Spring Filter,
go
The way I encode the password is using the following create method in
UserServiceImpl:
...
public UserServiceImpl(PasswordEncoder encoder, SaltSource salt, UserDAO
userDao, Logger logger, IRoleService roleService) {
this.encoder = encoder;
this.salt = salt;
this.userDao
Have you checked that the encoder used by Spring filter is the same you use
to encode it in your DB ?
Password Encoding is made of a salt and an algorithm.
2010/6/10 Daniel Henze
> Thanks for your reply.
>
> Yes, I did check that. And it's ok, lovely long and encrypted passwords.
>
> Daniel
>
Thanks for your reply.
Yes, I did check that. And it's ok, lovely long and encrypted passwords.
Daniel
Am 10.06.2010 09:51, schrieb Christophe Cordenier:
Hi
I guess you already did it but have you checked if the password is stored in
SHA1 ?
2010/6/10 Daniel Henze
Hi there,
I installed
Hi
I guess you already did it but have you checked if the password is stored in
SHA1 ?
2010/6/10 Daniel Henze
> Hi there,
>
> I installed Tapestry-Spring-Security and followed the installation and
> configuration advise. But I have no luck as the login does not work for me
> and always returns
Hi there,
I installed Tapestry-Spring-Security and followed the installation and
configuration advise. But I have no luck as the login does not work for
me and always returns "Username and/or password was wrong!". There was a
recent post about the "Bad credentials" and it was the wrong SaltSer
