Dock Web3 ID signs users in with verifiable credentials they hold in a wallet, rather than an account on a provider's server. It is the connector for products built on decentralized identity.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find Dock Web3 ID, and click Enable. Copy the redirect URI shown in the form:
https://identity.authdog.com/api/v1/callback/<connectionId>Create the application
- Create an OIDC client in your Dock Web3 ID account.
- Add the redirect URI from Authdog to the client.
- Copy the Client ID and Client Secret.
- Note the host to use as the Domain URI.
Configure Authdog
| Field | Value |
|---|---|
| Client ID | The client identifier from the provider |
| Client Secret | The client secret from the provider |
| Domain URI | Your Dock Web3 ID host |
Save, then toggle the connection active.
What Dock Web3 ID returns
Authdog requests the openid profile email scopes and reads the profile from https://<domain>/userinfo.
The userinfo endpoint returns the claims released from the presented verifiable credential.
The subject identifier is derived from the credential, so a user who re-issues credentials may present a different subject. Decide up front whether your linking strategy tolerates that.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the Dock Web3 ID button and complete the flow.
- Confirm the user appears under Users in the console with a Dock Web3 ID identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
| Presentation rejected | The requested credential type is not one the wallet holds |
| Redirect or callback URL error | The URI registered with the provider does not match Authdog's exactly |
| Works in one environment only | Each environment has its own connectionId, and so its own redirect URI to register |
Related
| Read | To learn how to |
|---|---|
| Connectors | Set up any other social provider |