BitBadges signs users in with their blockchain-backed BitBadges identity, where on-chain badges represent membership and credentials. It fits products that gate access on those holdings.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find BitBadges, and click Enable. Copy the redirect URI shown in the form:
https://identity.authdog.com/api/v1/callback/<connectionId>Create the application
- Register an OIDC client with BitBadges.
- Add the redirect URI from Authdog to the client.
- Copy the Client ID and Client Secret.
Configure Authdog
| Field | Value |
|---|---|
| Client ID | The client identifier from the provider |
| Client Secret | The client secret from the provider |
| Domain URI | The BitBadges OIDC host |
Save, then toggle the connection active.
What BitBadges returns
Authdog requests the openid profile email scopes and reads the profile from https://<domain>/userinfo.
The userinfo endpoint returns the identity claims BitBadges releases for the connected account.
Badge holdings change on chain. Re-check them at the moment of authorization rather than trusting a claim captured at sign-in.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the BitBadges button and complete the flow.
- Confirm the user appears under Users in the console with a BitBadges identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
invalid_client |
Client credentials mismatch |
| 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 |