IDPartner lets users authenticate through their bank, using an identity a financial institution has already verified. It suits onboarding flows that need a real, KYC-grade identity without running the checks yourself.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find IDPartner, and click Enable. Copy the redirect URI shown in the form:
https://identity.authdog.com/api/v1/callback/<connectionId>Create the application
- Register an application in the IDPartner dashboard.
- Add the redirect URI from Authdog to its redirect URIs.
- Copy the Client ID and Client Secret.
- Note the environment 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 IDPartner environment host |
Save, then toggle the connection active.
What IDPartner returns
Authdog requests the openid profile email scopes and reads the profile from https://<domain>/userinfo.
The userinfo endpoint returns bank-verified claims — name, email, and, depending on the participating institution, address and date of birth.
Available claims vary by bank. Design your sign-up so a missing optional claim does not block the user.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the IDPartner button and complete the flow.
- Confirm the user appears under Users in the console with a IDPartner identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
| No matching bank | The user's institution does not participate in the IDPartner network |
| 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 |