Skip to content
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

Security #48

Closed
martinlockett opened this issue Jul 20, 2018 · 2 comments
Closed

Security #48

martinlockett opened this issue Jul 20, 2018 · 2 comments

Comments

@martinlockett
Copy link

Really great article! One concern I have is that (e.g. on Safari you can view the source using the Develop Menu -> Show Page Source) anyone can read your Firebase configuration details e.g. api key and project id. Is this enough information to allow people to hack into your Firebase service?

@rwieruch
Copy link
Owner

Yes, that's true. However, the Firebase credentials are supposed to be used in client applications. That's why you can restrict the domains in your Firebase console to your own domain. Then no one else can use it. Does it make sense?

@martinlockett
Copy link
Author

There are a number of scenarios I can think of.

If your web pages are hosted on Firebase then I believe you can restrict access to your domain so the api key and project id are not enough for someone to hack into your service. The other options below assume you do not use Firebase hosting.

If you use OAUTH your permitted callback URLs will restrict access to the service although many developers will include localhost to facilitate development so that isn't safe.

If you just use account and password authentication I don't think that is safe.

I guess the recommendation is to use Firebase hosting and restrict the domain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants