You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now I'm facing the issue of migrating users from other platforms (firebase, cognito) to mine without asking them to reset password. Because others use different hash functions. I would like to override this using my own emailpass provider.
I can't figure out a workaround for this. Adding my own emailpass provider to the auth configs won't work, because it would always resolve to the first provider with id 'emailpass', which is hard coded to be the first in array.
// Note: For now we want to inject some providers out of the boxconstproviderConfig=[{resolve: EmailPassProvider,id: "emailpass",},
...(options?.providers??[]),]
When will this be removed? I think it could be put in the config file by default instead of in the auth module?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Right now I'm facing the issue of migrating users from other platforms (firebase, cognito) to mine without asking them to reset password. Because others use different hash functions. I would like to override this using my own emailpass provider.
I can't figure out a workaround for this. Adding my own emailpass provider to the auth configs won't work, because it would always resolve to the first provider with id 'emailpass', which is hard coded to be the first in array.
And I can see that in auth provider loader, comment on line 36 says:
When will this be removed? I think it could be put in the config file by default instead of in the auth module?
Beta Was this translation helpful? Give feedback.
All reactions