Firebase身份验证第三提供商选择Firebase或其他解决方案
我确实喜欢Firebase DB解决方案Beause它很快，您可以对更改进行子订阅，但是我的一个问题是关于用户访问。我确实想用一个MasterPassword构建一个系统，在该系统中，您不将所有用户一直识别为Google Firebase。我想将用户ID存储在另一台服务器上，而不是在Firebase中。这完全可以使用燃料吗？您如何在Firebase中建立3：RD Party身份验证提供商？我不想将身份数据存储在Firestore内，而是想在另一个地方存储。这是我应该使用其他数据库解决方案的方式破坏交易的人吗？
I do like the firebase db solution beause it is fast and you can subcscribe to changes but my one question is about user access. I do want to build a system with one masterpassword where you dont ID identify every user all the way into Googles firebase. I want to store user ID on another server and not inside firebase. is this doable with firebase at all? How do you go about building a 3:rd party Authentication provider in firebase? I do not want to store identification data inside firestore but in another place. Is this a dealbreaker in a way I should use any other db solution?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当您
无需在Firestore中存储标识，甚至使用Firestore，但是如果您使用上面链接中记录的自定义令牌登录用户，则它们的令牌将在
request.auth < /code> Firestore安全规则中的变量。如果您想了解实现自定义身份验证提供商有多容易/难以容易，请查看一个简单的示例，用户名+密码提供商构建在云功能之上（也不需要，但仅在此示例中使用）。
When you implement a custom authentication provider you control pretty much everything out the user token, including its UID and the claims in there.
There is no requirement to store the identification in Firestore, or to even use Firestore either, but if you sign in the user with the custom token as documented in the link above, their token will be available in the
request.authvariable in your Firestore security rules automatically.If you want to get a feeling at how easy/hard it is to implement a custom authentication provider, have a look at this simple example of a username+password provider built on top of Cloud Functions (which is not required either, but just used in this example).