Skip to Content
Platform.Ontology

Sign In with LinkedIn (OpenID Connect)

Lets a site sign people in with their LinkedIn account and receive basic profile data.

Asks you firstSign in and identityFederated sign inWeb browsersWhen you are signed in

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

BrowserStatusFirst versionNote
ChromeSupportedNot availableNone
EdgeSupportedNot availableNone
FirefoxSupportedNot availableNone
SafariSupportedNot availableNone
Safari on iPhoneSupportedNot availableNone
Chrome on AndroidSupportedNot availableNone
Samsung InternetSupportedNot availableNone

How a site asks for it

APIGET https://www.linkedin.com/oauth/v2/authorization; POST /oauth/v2/accessToken; GET https://api.linkedin.com/v2/userinfo
How access is grantedprompt
What the user seesLinkedIn consent screen listing scopes
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsAccess token lifetime set by LinkedIn; consent until revoked in LinkedIn settings
How to take it backLinkedIn account permitted services
Inside an iframeRedirect flow, not for iframes

Typical flow

  1. Site redirects with scope openid profile email
  2. Person signs in and consents
  3. Site exchanges the code for tokens (RS256 id_token, jwks at /oauth/openid/jwks)
  4. Site calls userinfo

Data you get

What comes back: OIDC claims
Shape: object
How often: per sign in

FieldTypeUnitRangePrecision
substringNonepairwisestable per app
name, given_name, family_namestringNoneNot listedNot listed
picturestringURLNot listedNot listed
localestringNoneNot listedNot listed
emailstringNoneoptionalNot listed
email_verifiedbooleanNoneoptionalNot 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

TypeExampleApps
productivityA resume builder fills in a person's name, photo and email with one LinkedIn click, then offers to import their job history.None named
enterpriseA webinar or whitepaper form is replaced with a LinkedIn sign in so the sales team gets a real contact.None named
educationAn online course site signs in learners with LinkedIn so they can add a certificate to their profile.Coursera
socialAn alumni or events platform imports names and photos so attendees look familiar in the guest list.None named
gamesA career focused web game or hackathon portal uses it to register players with a real name.None named
adsB2B 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

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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.

On this page