Chrome Extension
Connect a LinkedIn account from the person's own Chrome with the Lempile Connect extension, without a password or copied cookies: what it reads, what it sends, and where.
Lempile Connect is Lempile's Chrome extension (Chrome Web Store). It connects the LinkedIn account already signed in on a person's own Chrome to Lempile, without typing a password and without copying cookies by hand. It does what Unipile's UniLogin extension does for Unipile's hosted auth.
Where It Appears#
Every LinkedIn connect page of Lempile offers three ways to sign in: Credentials, Cookies and Extension. That includes the page your hosted auth links open (POST /api/v1/hosted/accounts/link, see Authentication And Accounts). Nothing changes in your API calls: the account, its account_id, the notify_url call and the webhooks are the same whichever way the person signs in. Unipile's unilogin option on the link is accepted and has no effect: the Extension tab is always there.
What The Person Does#
- On the connect page, they choose Extension.
- If the extension isn't in their Chrome yet, the page shows Install for Chrome, which opens its Chrome Web Store page, and I already installed it.
- They click Connect. The extension opens its own small window. It names the site that asked and lists exactly what will be sent.
- They click Connect in that window. The window closes, and the connect page carries on as for any sign-in: checks, then the account is connected.
If they aren't signed in to LinkedIn in that Chrome, the window says so and offers Open LinkedIn, then Check again.
What The Extension Reads And Sends#
Only after the click in its own window, and once, to that one connection:
- the LinkedIn session of that Chrome: the
li_atcookie,li_awhen the account has Sales Navigator or Recruiter, and the other cookies Chrome keeps for linkedin.com (such asbcookieandJSESSIONID), which tell LinkedIn it is still the same browser; - that browser's user agent, languages, time zone and client hints (the same fields Unipile's cookie connect takes:
user_agent,user_language,user_languages,user_timezone).
The session goes straight from the extension to Lempile's server over HTTPS. The connect page itself never sees a cookie, and neither does your app.
How The Handoff Is Protected#
- The connect page first asks Lempile's server for a one-time handoff: valid for 5 minutes, used once, for that page's own sign-in only (that console user, or that hosted auth link) and for that account only on a reconnect.
- The extension accepts requests only from Lempile's own pages. It sends only to the same Lempile site that asked, on one fixed path. Lempile's server accepts that POST only from a Chrome extension.
- Lempile keeps the session encrypted while it waits, and wipes it the moment the sign-in starts. A handoff nobody used is wiped after its 5 minutes.
- The extension stores nothing: no cookie, no history, no settings. It never runs in the background, and it reads nothing until the person clicks Connect in its window.
Keeping The Account Connected#
The connected account uses the same LinkedIn session as the person's Chrome. If the person signs out of LinkedIn in that Chrome, LinkedIn ends that session everywhere, Lempile included, and the account must be reconnected. Ask people to stay signed in to LinkedIn in the Chrome they connected from.
Permissions#
| Permission | Why |
|---|---|
cookies, on *.linkedin.com |
To read the LinkedIn session of that Chrome, after the click. |
lempile.com, admin.lempile.com |
To see that a Lempile connect page asks for it, and to send the session to that page's handoff. |
Nothing else: no access to other sites, no browsing history, no storage, no background activity. Privacy policy: lempile.com/privacy/chrome-extension.
Was this page helpful?