Since we switched from Firebase Hosting to Netlify, we no longer have a route to handle incoming password reset and verification emails, so our outbound emails have this ugly URL:
Furthermore, using the above URL for password reset means that the users password manager will offer to save the password for this domain and not members.rally.mozilla.org
We need to be able to handle these, I suggest we do these two steps in this order:
[ ] rewrite/proxy from netlify to firebase. A simple redirect would make the URLs in email look nicer, but it wouldn't address the password manager issue like proxying.
[ ] override Firebase's and provide our own, which can be customized exactly the way we want and use our site's style. This requires creating a cloud function that implements a custom email action handler.
Rewrite/proxy is very easy as it is just a Netlify configuration change, and it addresses the "ugly url" and password manager problems.
I think we want to ultimately provide a custom email action handler, to make it match the style of our site and provide improvements to the reset/verification flow (providing a link for users to go to next, for instance), this will require a new cloud function to be written and new screens to be designed and implemented on the website.
Since we switched from Firebase Hosting to Netlify, we no longer have a route to handle incoming password reset and verification emails, so our outbound emails have this ugly URL:
https://moz-fx-data-rally-w-prod-dfa4.firebaseapp.com/__/auth/action?[...]
Furthermore, using the above URL for password reset means that the users password manager will offer to save the password for this domain and not members.rally.mozilla.org
We need to be able to handle these, I suggest we do these two steps in this order:
Rewrite/proxy is very easy as it is just a Netlify configuration change, and it addresses the "ugly url" and password manager problems.
I think we want to ultimately provide a custom email action handler, to make it match the style of our site and provide improvements to the reset/verification flow (providing a link for users to go to next, for instance), this will require a new cloud function to be written and new screens to be designed and implemented on the website.