Customer login not working : Magento 2

Hello Sir 
 
We have successfully migrated data from Magento 1 to Magento 2 via UB Data Migration Pro.
 
Everything working smoothly, but customers login not working on the frontend.
 
In customer_entity table, a field, password_hash is migrated in the following format.
for eq. 
243ddb41bb2a7553f112a0ae37d2bda28e3416fc95034b7e07eaeebcbfafa6fe:nAMTva5xVf7j7SZKTsRy2N1wseNL3rY5:0      (Magento 2)
FROM 
243ddb41bb2a7553f112a0ae37d2bda28e3416fc95034b7e07eaeebcbfafa6fe:nAMTva5xVf7j7SZKTsRy2N1wseNL3rY5         (Magento 1)
 
But When i replace :0 to 1 at the end of password_hash, It’s working fine, I tried 5-6 random login, all worked.
 
I have referred all related post in a forum about “customer login not working”, but this one is a unique issue
 
We have more than 45000 customers, can you please help me how can i fix this issue.
 
Thank you in Advance.

3 answers

Profile photo of Mall Staff 184060.00 $tone March 13, 2018
Public

Hi there,

In customer_entity table, a field, password_hash is migrated in the following format.
for eq. 
243ddb41bb2a7553f112a0ae37d2bda28e3416fc95034b7e07eaeebcbfafa6fe:nAMTva5xVf7j7SZKTsRy2N1wseNL3rY5:0      (Magento 2)
FROM 
243ddb41bb2a7553f112a0ae37d2bda28e3416fc95034b7e07eaeebcbfafa6fe:nAMTva5xVf7j7SZKTsRy2N1wseNL3rY5         (Magento 1)

Yes, that is right. 

But When i replace :0 to 1 at the end of password_hash, It’s working fine, I tried 5-6 random login, all worked.

You shouldn’t do that. Because Magento2 supported for two formats. Magento2 will auto updates after any customer’s action.
What is version of Magento2 instance in your working now? Did you re-correct your customer credentials once more?
Let’s provide me information about your instances as followings:
+ Admin credentials and back-end URL
+ SSH credentials and web root path to your Magento2 folder
+ A customer credentials which has the issue as you mentioned and the front-end URL of your Magento1 site to verify that, this customer credential is corrected.
+ phpMyadmin credentials of your databases (Magento 1 and Magento 2 databases) if you have.
I will help to check further in your instances and reply you more later.
Regards,
Mall.
 
 

#1
Profile photo of sina 90.00 $tone March 13, 2018
Public

Hi Mall
 
I am using Magento 2 CE 2.2.3 Version
 
When i migrated data using your UB Data Migration Pro, It has added :0 at the end of password_hash field in customer_entity table
 
I can see that change in your file \pub\ub-tool\protected\controllers\Step6Controller.php   (Line # 489)
 
But this change doesn’t work in Magento 2 CE 2.2.3 Version
 
For solution: 
 
I ran a query to remove :0 from password_hash field in customer_entity table
 
cleaned cache, reindex, cleaned cache again
 
Now It works fine, Login working,
 
Thank you for your reply.
 
 

#2
Profile photo of Mall Staff 184060.00 $tone March 14, 2018
Public

Hi there,

I am using Magento 2 CE 2.2.3 Version
When i migrated data using your UB Data Migration Pro, It has added :0 at the end of password_hash field in customer_entity table
I can see that change in your file \pub\ub-tool\protected\controllers\Step6Controller.php   (Line # 489)
But this change doesn’t work in Magento 2 CE 2.2.3 Version

No, we had already tested our migration tool before the release of our compatibility version for M2.2.3. 
And we re-tested our tool once again upon your report on the issue above. But the migrated Customers can still login normally without any change in our tool.
So, the issue should come from your specific instance only. The possible cases might be due to wrong customer credentials; or you tried to login a website which differs from the one that your customer signed up. As you know, if you did not select the Merge Default Website setting (in Step 2 -- Migration Settings | Sites, Stores), then migrated data will be ported in a separated website.  
 
Also, other users who used our migration tool so far didn’t get the issue as you mentioned.
Please re-check from your end once more.
Regards,
Mall.

#3

Please login or Register to Submit Answer

Written By

Comments