Sign In with LinkedIn (OpenID Connect)
Lets a site sign people in with their LinkedIn account and receive basic profile data.
In one line
Can sign you in with LinkedIn and get your name, photo and email
Lets a site sign people in with their LinkedIn account and receive basic profile data.
After the person approves, the site gets a stable pairwise ID, name, photo, locale and optionally a verified email. It does not verify real world identity.
What it can and can't do
What the user does: You tap Sign in with LinkedIn and approve the LinkedIn consent screen
It can
- Receive a stable ID for you that is unique to that site
- Get your name, photo, language and, if you allow, a verified email
- Create or sign in to your account on that site
It cannot
- Prove who you are in real life
- See your work history, connections or posts
- Get anything beyond the permissions listed on the consent screen
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | GET https://www.linkedin.com/oauth/v2/authorization; POST /oauth/v2/accessToken; GET https://api.linkedin.com/v2/userinfo |
| How access is granted | prompt |
| What the user sees | LinkedIn consent screen listing scopes |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Access token lifetime set by LinkedIn; consent until revoked in LinkedIn settings |
| How to take it back | LinkedIn account permitted services |
| Inside an iframe | Redirect flow, not for iframes |
Typical flow
- Site redirects with scope openid profile email
- Person signs in and consents
- Site exchanges the code for tokens (RS256 id_token, jwks at /oauth/openid/jwks)
- Site calls userinfo
Data you get
What comes back: OIDC claims
Shape: object
How often: per sign in
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
sub | string | None | pairwise | stable per app |
name, given_name, family_name | string | None | Not listed | Not listed |
picture | string | URL | Not listed | Not listed |
locale | string | None | Not listed | Not listed |
email | string | None | optional | Not listed |
email_verified | boolean | None | optional | Not listed |
Technical limits
- Does not verify identity
- email and email_verified are optional
- Subject is pairwise: not matchable across apps
The story
What it is
Sign in with LinkedIn: you approve, and the site learns your name, photo and maybe email.
For you
You are sent to a LinkedIn page that lists what the site wants (basic profile, email). You press Allow and you are sent back signed in. The site never sees your LinkedIn password.
For makers
Makers of work apps skip password systems and get a real name and picture. Leads and trials arrive with cleaner data, and the site can personalize the first screen.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | A resume builder fills in a person's name, photo and email with one LinkedIn click, then offers to import their job history. | None named |
| enterprise | A webinar or whitepaper form is replaced with a LinkedIn sign in so the sales team gets a real contact. | None named |
| education | An online course site signs in learners with LinkedIn so they can add a certificate to their profile. | Coursera |
| social | An alumni or events platform imports names and photos so attendees look familiar in the guest list. | None named |
| games | A career focused web game or hackathon portal uses it to register players with a real name. | None named |
| ads | B2B marketers use the verified email to match leads to ad campaigns and measure conversions. | None named |
Risks
- Shares work identity
- Name tied to real person
Good uses and abuse
Legitimate uses
- One click sign up
- Prefilled profile
Known abuse
- Profile scraping, contact harvesting
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
A real example: LinkedIn
LinkedIn as identity provider for third party sites; part of the data flow around LinkedIn but not a fingerprinting method.
Sources
How well checked: Checked against real behavior.