Migration to Firebase Auth

[HossamTarek-bits]

Migration to firebase auth

Consider this a document, for lack of a better place to document changes to the code

General Details @MohammedAbdulaziz @SaifAbuelhasan @rafa763 @stevensamir20

• no more password usage in the server or passwords are dealt by firebase auth and we don't have access to them, check below for migration from firebase in the future
• all userName are now emails any old accounts used are now obsolete and should create new ones for testing or admins
• no more session handling, switching to firebase JWT for scalability since we only use them for APIs protection

For frontend & mobile app @MohammedAbdulaziz @stevensamir20

• No more cookies sent to the client from the server, for any protected route from now on use firebase token and set it in the header of the request Authorization: <Firebase Token>

To get token in frontend

firebase.auth().currentUser.getIdToken(/* forceRefresh */ true).then(function(idToken) {
  // Send token to your backend via HTTPS
  // ...
}).catch(function(error) {
  // Handle error
});

To get token in flutter

await credential.user?.getIdToken();

• To use socket you have to include firebase token in headers also, follow this from the docs in the token
  • for frontend it should look something like this in the current code ioInstance = io(URL, {withCredentials: true, auth: {token: <Firebase Token>}});
• recheck APIs document to see the routes that have change
• usually any route that you would send userName and password are now email and firebaseUID, you get the firebaseUID from the credientials object after login/signup ( note that there are two UIDs in the object I want the top level UID the inner UID is called providerUID something like this )

Mobile App @MohammedAbdulaziz

• no more login route, login using firebase
• after you use signInWithEmailAndPassword use the api PUT customer/fcmToken to send the fcmToken
• to update the user's email send the new email in the updateProfile API this will update in firebase and database at the same time (might need to relogin not sure), if you want to change the password use firebase auth SDK
• when you sign up using createUserWithEmailAndPassword use the signup route putting in the body email, firebaseUID and fcmToken
• for social logins you must check if the user is new or not even if he used the login page check isNewUser and if so use the signup API to ensure that he is created in the backend, otherwise you won't be able to use the routes !!important

Frontend @stevensamir20

• for creating a new shop use firebase sign in and then send to the API email, firebaseUID and the rest of the details
• for login use the firebase sign in with email and password and store the token for api requests
• for creating a shop moderator use firebase signup and after signing up send in the createShopModerator API the email and firebaseUID and any other details as usual

Migrating from firebase

• incase we need to migrate from firebase for any reason here are some resources I found
  • migrating to supabase
  • Can I seamlessly migrate users from Firebase Auth?
  • Firebase Auth Export

hopefully I haven't forgotten anything

[MohammedAbdulaziz]

Impressive work ❤️❤️🙏

[stevensamir20]

شغل طرش

[rafa763]

reading this a bit late, impressive work
hope your military service passes quickly