LinkedIn is the connector for B2B products: the identity carries a work email and a professional profile, and users treat it as the natural choice on a business sign-up page.

## Copy the redirect URI

In the [Authdog console](https://console.authdog.com), select the project and environment, open **Authentication > Providers**, find **LinkedIn**, and click **Enable**. Copy the redirect URI shown in the form:

```url
https://identity.authdog.com/api/v1/callback/<connectionId>
```

## Create the LinkedIn app

1. Open the [LinkedIn Developer Portal](https://www.linkedin.com/developers/apps) and select **Create app**.
2. Fill in the app name, the **LinkedIn Page** it belongs to, and a logo.
3. Verify the app from the **Settings** tab — an admin of the associated LinkedIn Page must approve it. Nothing works until this is done.
4. Open the **Products** tab and request **Sign In with LinkedIn using OpenID Connect**.
5. Open the **Auth** tab, and under **Authorized redirect URLs for your app**, paste the redirect URI from Authdog.
6. Copy the **Client ID** and **Client Secret** from the same tab.

> **Caution**
>
> The company page association and its admin verification are the step teams
> forget. Without them the product request stays pending and every sign-in
> attempt returns `unauthorized_scope_error`.

## Configure Authdog

| Field | Value |
| --- | --- |
| **Client ID** | From the **Auth** tab |
| **Client Secret** | From the **Auth** tab |

Save, then toggle the connection **active**.

## What LinkedIn returns

Authdog requests `r_emailaddress r_liteprofile` and reads the profile from LinkedIn's v2 API, with the email fetched from a second endpoint — LinkedIn splits identity across `/v2/me` and `/v2/emailAddress`.

Two limits are worth knowing before you build on this data:

- The profile is deliberately thin. Name, identifier, and profile picture; no headline, company, or position without additional products and review.
- The email is the address on the LinkedIn account, which for many users is personal rather than corporate. Do not treat a LinkedIn sign-in as proof of employment at a given company.

LinkedIn periodically revises its API products and scope names. If sign-in breaks after working for months, check the **Products** tab first — a product may have been deprecated or need re-requesting.

## Test it

1. Open your environment's hosted sign-in page, or link to `https://identity.authdog.com/api/v1/signin/<connectionId>`.
2. Select **Continue with LinkedIn** and authorize.
3. Confirm the user appears under **Users** with an email address attached.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| `unauthorized_scope_error` | The Sign In product is not approved on the app |
| `The redirect_uri does not match the registered value` | The URI is missing from **Authorized redirect URLs** |
| App stuck unverified | The associated LinkedIn Page admin has not completed the verification link |
| No email returned | The email endpoint call was refused — confirm the requested products cover email |

## Related

| Read | To learn how to |
| --- | --- |
| [Connectors](/docs/connectors) | Set up any other social provider |
| [Enterprise SSO](/docs/sso) | Sign in employees through their employer's identity provider instead |