After successfully incorporating "twitter authentication" on my firebase application following the instructions provided at this link:
I have observed that it functions seamlessly.
Once a user logs in, they are able to make requests to my domain using XMLHttpRequest.
Unfortunately, I realized that passing the "username" through JavaScript during these XMLHttpRequests could be vulnerable to interception and tampering by individuals using tools like "Chrome Dev Tool".
Is there a solution to address this potential security issue?
==================================================================
For example:
Let's say my website is hosted at:
www.example.com/
This site delivers a static page index.html containing extensive JavaScript code. It utilizes the Firebase API for authentication via Twitter or Github. Suppose a signed-in user wants to make a post; currently, the implementation looks like this: https://www.example.com/writeComment?comment=hello&username=jeff&provider=github
The concern here is that even after signing in, there remains a risk of users altering their username through the Chrome console, jeopardizing data integrity.