Hello,

we've migrated an existing SiverStripe Website with a customer login to a new server. Since then existing customers can't login to the website anymore. If we register a new member for the website the login is possible.

Any idea or hint how to solve this is very welcome.

Best regards,

Boris

Have you tried changing the customer password from within the CMS? On reason I can think of is that your previous setup still used the old password encryption...

If I change the password from the backend everything is fine. Unfortunately I can't do this for 300+ users. Is there a way to use the old password encryption?

Best regards,

Boris

Ok, that's tricky! What version of silverstripe are you on? Did you upgrade or just clone the existing install to the new server?

Unfortunately I don't know how to get the SilverStripe version. We've inherited the installation of the former agency. I just did a clone without an update and just copied files and restored a mysqldump.

If, in your site root, there is a directory 'sapphire', you're on 2.4 or below. If you have a directory 'framework' you're on 3.0 or above. On versions below 3.0 you should be able to see the version number in the footerbar of the CMS, to the right.

If this is an older site (say 2.3.x), this might have something to do with this ticket: http://open.silverstripe.org/ticket/3004.

[EDIT] Of course I don't know about your site and if this is at all possibl - is it in production already? - but I'd suggest you prevent other users from registering for the time being, until you find out what the cause is. Otherwise you might end up with a mix of password settings...

Thank you that far.

Seems we are running an older version of SiverStripe, since we got a folder called "sapphire" in the webspace.
Right now the domain is only available if you modify the /etc/host file manually.

I've also checked the PasswordEncryptor.php file and line 164 as described in the link, but it seems to be already fixed there:
$password = parent::encrypt($password, $salt, $member);

'Right now the domain is only available if you modify the /etc/host file manually.'

I'm not sure what you mean, and how this connects to the problem at hand? Unfortunately, based on you information alone I don't really know how to tackle this problem.

Do you still have access to the previous hosting and the old version of the website? Or do you know the password for one of the old useraccounts, so you could add a new user with the same password? In that case you could check the hashes (see the MemberPassword table) and see how they are different...