-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firebase auth:import do not use the right password #1617
Comments
This issue does not seem to follow the issue template. Make sure you provide all the required information. |
Internal tracking id: 140201224 |
Hi, does anyone have an update to the status of this issue? |
I asked the engineering team and we currently don't support 0-round hashing for SHA1 passwords. I will add a warning to reflect this. |
Hi @samtstern , I was hoping to get a bit of direction for a problem we're having with the import users method.
Since
Any advice as to what number of rounds we should try? Is there any alternative solution to this problem, or are we out of luck with this one? |
I think the problem is in the Base64 encoding. You should generate Base64 from un-hex-ed SHA1 hash. Refer to this SO post: https://stackoverflow.com/questions/27838177/convert-string-to-sha1-and-to-base64 And we basically import our data using this command:
-- |
Anyone else having this issue? I can't get the export/import to work properly. Going from one database to another. Basically running |
@cfofiu - you have to specify the hash-key of your old project while importing
The hash key is located in |
firebase auth:import
appear to be broken?With MD5:
This works fine.
But, with SHA1, SHA256, etc.:
this don't allow me to login with the password that I choosed. The account is created, but I cannot login. On login I get error is:
The plain password for those tests of mine is:
tester5
. I tried with both the latest version of firebase-tools ( 7.2.4 ), and the previous major version as well - same behaviour.Am I missing something?
The text was updated successfully, but these errors were encountered: