Creating Verifier on Web3Auth Dashboard
A verifier is essentially a configuration that contains information about the OAuth provider you've chosen for your application. It acts as a bridge between Web3Auth and the OAuth provider, enabling the Auth Network nodes to query and validate JWT tokens effectively.
Create Verifier
The Custom Authentication tab of a project looks something like this:
Once you click on the Create Verifier button, you'll see a page similar to this:
Here, you can create a new verifier for your application by specifying the necessary details as per your OAuth provider / login details.
To create a verifier, you need to input the following details:
Verifier identifier
The name of your verifier. This is a unique identifier that will be used to reference this verifier.
Supported Auth Provider
Once you have named your verifier, the next step is to choose the authentication provider for the verifier. We have listed some of the providers we support. Please note, the support is not just limited to listed porviders. If you don't find the provider you want to integrate, please feel free to reach out to us on Discord, or post your query on the Community Support Forum and we will take care of things from there.
Social Providers
Authentication Service Providers
Authentication Service Providers allow you to utilize certain implicit and authorization code grants. You may also use social providers on top of Federated / Identity providers to pick other social providers (for example, Twitter, Apple, GitHub, LinkedIn, WeChat, and so on) that we do not natively support. It is important to note that you must register an app with the Authentication Service Providers before proceeding.
The links below will help you set up the following authentication service providers:
Bring your own JWT Provider
You can integrate your own custom login providers with Web3Auth by using one of the custom login schemes, such as JWT or ECDSA signatures. This enables your users to continue using your existing login provider. Your application should adhere to the JWT specification and utilize JWKS for signing the JWT. The public keys for signing the JWT should be exposed through an endpoint.
There are some nuances with certain login providers, so don't hesitate to get in touch with us on Discord or simply post your query on the Community Support Forum and we will take care of things from there.
Edit Verifier
Click on the verifier or the three dots next to the verifier you wish to edit and click on
Edit Verifier in the dropdown.
The Edit Verifier page will appear with previously filled information. Make the necessary changes
and click on the Update Verifier button on the bottom.
Archive Verifier
To archive a verifier from the existing list, click on the three dots next to the verifier you wish to archive, and then select "Archive Verifier" from the dropdown.
When you archive a verifier, it will no longer be available for use in your application. However, you can always unarchive it later from the Archive page in the dashboard.
