|
1 | 1 | --- |
2 | 2 | title: Auth Provider Setup |
| 3 | +sidebar_label: Overview |
3 | 4 | image: "images/docs-meta-cards/documentation-card.png" |
4 | | -displayed_sidebar: docs |
| 5 | +displayed_sidebar: resources |
5 | 6 | description: "Auth Provider Setup | Documentation - Web3Auth" |
6 | 7 | --- |
7 | 8 |
|
8 | 9 | import BYOCustomJWTTiles from "@site/src/common/docs/_byo-custom-jwt-providers.mdx"; |
9 | 10 | import FederatedTiles from "@site/src/common/docs/_federated-providers.mdx"; |
10 | 11 | import SocialTiles from "@site/src/common/docs/_social-login-providers.mdx"; |
11 | 12 |
|
12 | | -Auth Provider setup refers to the capability of creating a **verifier**(_a way to do custom authentication_) with Web3Auth. By default, Web3Auth comes |
13 | | -with a set of default verifiers that you can use out of the box. |
| 13 | +Setting up authentication providers within Web3Auth is a crucial step in configuring the authentication flow for your application. This process |
| 14 | +involves creating a verifier, a unique identifier that Web3Auth uses to interact with the OAuth provider and validate user authentication requests. |
| 15 | +Verifiers play a pivotal role in ensuring secure and seamless authentication by leveraging the Web3Auth Auth Network nodes and a dedicated blockchain. |
14 | 16 |
|
15 | | -:::info Caveat with Default Verifiers |
| 17 | +## Understanding Verifiers |
16 | 18 |
|
17 | | -- **Migration from Default Verifiers to Custom Verifiers is not possible.** |
18 | | -- The default verifier is not suitable for all use cases. For example, if you are using a custom JWT provider, you will need to use the |
19 | | - [`Web3Auth Plug and Play No Modal SDK`](/sdk/pnp/web/no-modal/), since the Web3Auth Modal will only help you configure the social logins present |
20 | | - within the Modal UI. |
21 | | -- **Aggregation of the default verifier is not possible.** For example, if you want to aggregate Google and Email Passwordless, or any two/more social |
22 | | - providers, you will need to create an Aggregate Verifier, which is not possible if you start with: |
23 | | - - a Default Verifier |
24 | | - - or, Social Login Providers |
25 | | - - or, Custom Providers |
| 19 | +A verifier is essentially a configuration that contains information about the OAuth provider you've chosen for your application. It acts as a bridge |
| 20 | +between Web3Auth and the OAuth provider, enabling the Auth Network nodes to query and validate JWT tokens effectively. |
| 21 | + |
| 22 | +:::tip |
| 23 | + |
| 24 | +Head over to the [Verifiers](./verifiers.mdx) section to understand how to create a custom verifier for your application. |
26 | 25 |
|
27 | 26 | ::: |
28 | 27 |
|
| 28 | +## Setting Up Your Auth Provider |
| 29 | + |
| 30 | +Integrating an OAuth provider with Web3Auth involves a few key steps, from selecting your provider to configuring the verifier and integrating it into |
| 31 | +your application. Here's a broad overview of the process: |
| 32 | + |
| 33 | +1. **Select an OAuth Provider:** Choose an OAuth provider supported by Web3Auth, such as Google, Facebook, Twitter, or any other provider that fits |
| 34 | + your application's requirements. |
| 35 | + |
| 36 | +2. **Create a Verifier:** Using the Web3Auth Dashboard, create a new verifier for your selected OAuth provider. This involves specifying the provider |
| 37 | + details and any additional configuration required by the provider. |
| 38 | + |
| 39 | +3. **Deploy to the Web3Auth Blockchain:** Once your verifier is configured, it's deployed to the Web3Auth blockchain. This deployment process |
| 40 | + registers your verifier, making it accessible to the Auth Network nodes for JWT token verification. This process generally takes around 5-10 |
| 41 | + minutes to complete. |
| 42 | + |
| 43 | +4. **Integrate with Your Application:** Finally, integrate the verifier into your application's authentication flow. This typically involves utilizing |
| 44 | + Web3Auth SDKs and specifying the verifier details in your application's authentication setup. |
| 45 | + |
29 | 46 | ## Supported Auth Providers |
30 | 47 |
|
31 | 48 | ### Social |
32 | 49 |
|
33 | 50 | <SocialTiles /> |
34 | 51 |
|
35 | | -### Federated / Identity Providers |
| 52 | +### Authentication Service Providers |
36 | 53 |
|
37 | 54 | <FederatedTiles /> |
38 | 55 |
|
|
0 commit comments