Indeed signs users in with their Indeed account, which fits recruiting products and job-board integrations where the candidate identity already lives there.
Copy the redirect URI
In the Authdog console, select the project and environment, open Authentication > Providers, find Indeed, 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 Indeed developer portal.
- Add the redirect URI from Authdog to the allowed redirect URLs.
- Request the OpenID Connect scopes for profile and email.
- 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 Indeed returns
Authdog requests the openid profile email scopes and reads the profile from https://apis.indeed.com/v2/me.
The /v2/me endpoint returns the sub identifier, email, and name for the signed-in account.
Indeed reviews applications and grants scopes per use case, so confirm which claims your registration is approved for before building on them.
Test it
- Open your environment's hosted sign-in page, or link to
https://identity.authdog.com/api/v1/signin/<connectionId>. - Select the Indeed button and complete the flow.
- Confirm the user appears under Users in the console with a Indeed identity linked.
Troubleshooting
| Symptom | Cause |
|---|---|
invalid_scope |
The registration is not approved for the requested scopes |
| 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 |