当前位置:   article > 正文

Authentication Providers_authenticationproviders

authenticationproviders

MongoDB Logo
ServerDriversCloudToolsGuides
Get MongoDB
Close ×
MongoDB Stitch

Introduction
Tutorials
Users & Authentication
    Overview
    User Management
        Stitch Users
        Configure Custom User Data
        Finding a User
        Viewing User Data
        Managing User Accounts
        Linking User Accounts
        Working with Multiple User Accounts
    Authentication Providers
        Overview
        Anonymous
        Email/Password
        API Key
        Apple ID
        Facebook OAuth 2.0
        Google OAuth 2.0
        Custom Function
        Custom JWT
MongoDB Atlas
GraphQL
MongoDB Mobile
Functions
Triggers
External Services
Values & Secrets
Application Deployment
Hosting
Troubleshooting
Stitch Administration
Application Logs
Client SDKs
Release Notes

Stitch > Users & Authentication > Authentication Providers 
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38

Authentication Providers

MongoDB Stitch provides several authentication providers, which can be integrated into a client application to provide a mechanism for users to log in to your app.

For applications where you want users to be able to view or manipulate data without registering or creating an account, you can use Anonymous Authentication.
For applications where end users create an account or log in with existing credentials, you can use providers that integrate with existing login services (Facebook and Google), or use providers that allow you or your end users to create new credentials (Email/Password, API Keys, Custom JWT Auth and Custom Function Auth).
  • 1
  • 2

You can use a single provider if you want all users to authenticate in the same way, or you can enable multiple providers for more flexibility. You can also link a user account from one provider to a user account from another provider by using the the client SDKs. For more information on linking, see Linking User Accounts.

An example of an app that would benefit from multiple authentication providers is a blog or news service. The typical user of such an app would authenticate anonymously so that they don’t need to register. The blog authors and/or journalists would need to sign in with some other provider to become authorized to publish new content.
Authentication Providers

The following is a list of the authentication providers available in Stitch.
Authentication Provider Description
Anonymous
anon-user
Mechanism for authenticating without credentials. You should not use Anonymous authentication in applications where you want to persist user data.
Email/Password
local-userpass
Mechanism for authenticating with an email address and password. Requires implementing scripts with the SDKs for confirming an email and resetting a password.
API Key
api-key
Mechanism for logging in with API keys generated in the Stitch admin console, or by your end users.
Apple ID
oauth2-apple
OAuth2-based mechanism for logging in with an Apple ID.
Google
oauth2-google
OAuth2-based mechanism for logging in with an existing Google account.
Facebook
oauth2-facebook
OAuth2-based mechanism for logging in with an existing Facebook account.
Custom JWT
custom-token
Allow users to log in with JWT-based credentials generated by a service external to MongoDB Stitch.
Custom Function
custom-function
Allow users to log in with arbitrary credentials according to custom authentication logic that you define.
← Working with Multiple User Accounts Anonymous Authentication →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.
Was this page helpful?
Yes
No

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/笔触狂放9/article/detail/534084
推荐阅读
相关标签
  

闽ICP备14008679号