Importing users using the Import Users function in admin does not MD5 has the passwords from plaintext, so you will need to add a MD5 function.
I’m just going to end up doing an UPDATE query, I think to fix, since I just imported 18292 users.
I’ll post back to the forums when I get a working UPDATE query. The data for password is stored in mage_customer_entity_varchar as attribute_id 12
N.B. pass_new will be the column where you will put your plain text password
This class can be overwritten if required. But if not then revert back the change after successful import
ok so , will the values then be converted once this rule is reverted back to the use of hashpassword??? i’m confused as to what exactly to do
i have plain text passwords… whats the best way to import them directly in.. and not worry about bugs later??
will using this rule cause a conflict later once reverted back?
"email@example.com","base","default","","2011-03-28 18:55:05","Default Store View","","Leonardo","Male","1","Garcia","","","","1","","","1","test123","São Gonçalo","webdesigner","BR","12345","Leonardo","Garcia","","24430650","","Rio de Janeiro","Roberto Stevenson, Gradim","","219999999","1","1"
From what I understand the file Customer.php it will only create a new password is if the column is blank in password_hash import_custormer.csv ok?!
My question is this?
In column pass_new import_customer.csv I put in the password “test123” or password that is in the field attribute_id = 12 database table customer_address_entity_varchar ``??
I was tested here using the example above and the table does not save your password.
Is anyone experiencing this same problem when importing customers from version 126.96.36.199 to 188.8.131.52
I can confirm the method of putting a colon (:) at the end of a hash works in v1.6
Here is what I did to replace existing passwords: (i assume it would work if you are making new customers)
1. go to system>import/export>export choose customers, all fields. save the csv file that you get
2. open up the csv file.
3. pick any customer, delete the value in the “password_hash” column.
4. if you have a MD5 hash already - put it in the column and add the colon to the end.
4a. if you have a plain text password - you need the md5 hash. I used this generator to make a hash. Example: the hash for “password’ is 5f4dcc3b5aa765d61d8327deb882cf99
5. so my password_hash field now has 5f4dcc3b5aa765d61d8327deb882cf99: for that customer. (notice the colon at end)
6. import the file back into Magento. choose “replace”
7. test it - “password” is now the password for that customer.
I’m not exactly sure on the encryption method virtuemart uses so this could be my problem. I’m assuming the first string before the : is an md5hash and the string after the : is a salt.
After scouring the web though it appears a salt should only be 2 characters long, atleast thats what i’ve found magento to be using so i may have the above wrong and it could be a different encryption all together.
Would anyone have any other suggestions for me or could someone atleast tell me what encryption my passwords are in ?