The ID.me Community connector is the ID.me connector plus the community scope, which returns the verified communities a user belongs to rather than identity alone.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find ID.me Community, and click Enable. Copy the redirect URI shown in the form:
https://identity.authdog.com/api/v1/callback/<connectionId>Create the application
- Set up the application as in the ID.me connector.
- Request approval for the community policy your product gates on.
- Add the redirect URI from Authdog to the application.
- 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 |
Save, then toggle the connection active.
What ID.me Community returns
Authdog requests the openid profile email community scopes and reads the profile from https://api.id.me/api/public/v3/userinfo.
The response adds community affiliation to the standard claims, so your application can branch on the group a user has proven.
Approval is per policy. An application approved for one community is not automatically approved for another.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the ID.me Community button and complete the flow.
- Confirm the user appears under Users in the console with a ID.me Community identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
invalid_scope |
The community policy has not been approved for this application |
| 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 |
| ID.me | Use identity verification without community scope |