# Automate linkedin sign in with a saved email and password

**URL:** <https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974>\
**Category:** Get Help\
**Tags:** linkedin\
**Created:** [October 22, 2020, 6:18am UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974 "2020-10-22T06:18:30Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![customautosys](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/customautosys/32/13540_2.png) [@customautosys](https://community.auth0.com/u/customautosys)\
**Post date:** [October 22, 2020, 6:18am UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/1 "2020-10-22T06:18:30Z")

</div>

Hi, is it possible for me to perform an automated linkedin sign in using auth0 using a pre-determined email and password (e.g. retrieved from localStorage)?

If not, how is the user\_id (the “sub” of the JWT) for a linkedin account generated? Is there a standard way in which I can compute it on my own?

Also, is it possible for me to generate an auth0 JWT which I can send to my API on my own without going through auth0?

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [October 22, 2020, 7:47pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/3 "2020-10-22T19:47:59Z")

</div>

> [@customautosys](#):
>
> Hi, is it possible for me to perform an automated linkedin sign in using auth0 using a pre-determined email and password (e.g. retrieved from localStorage)?

I wouldn’t recommend storing email/password in localStorage. Can you tell us a bit more about your use-case?

> [@customautosys](#):
>
> If not, how is the user\_id (the “sub” of the JWT) for a linkedin account generated? Is there a standard way in which I can compute it on my own?

Why not get it from the user DB, why would you need to compute it? I don’t think you would be able to.

> [@customautosys](#):
>
> Also, is it possible for me to generate an auth0 JWT which I can send to my API on my own without going through auth0?

We manage the private keys if you are using RSA256, last I checked you didn’t have access to them. If you use a symmetric algo then you could. _I probably wouldn’t recommend this though._ Now I’m really curious what you are trying to do. 😄

---

<div class="post-metadata">

**Author:** ![customautosys](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/customautosys/32/13540_2.png) [@customautosys](https://community.auth0.com/u/customautosys)\
**Post date:** [October 24, 2020, 5:03am UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/4 "2020-10-24T05:03:15Z")

</div>

Well basically I want to do something using the LinkedIn Voyager API because I realised that I can’t do it with the public API. So I need the user’s username and password and I can’t use the socialIdentity returned by auth0. But I still want to use auth0 to manage the logins if possible. I’d just like a seamless login (user keys in email and password directly into my app, then my app sends the email and password concurrently to both the voyager API and to auth0 to login).

Is that possible?

And yes, I know about the implications of using the Voyager API but I’d still like to try (for testing purposes at least).

My app is a Cordova app.

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [October 26, 2020, 4:27pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/5 "2020-10-26T16:27:54Z")

</div>

Still not sure I grasp the needs here. Are you are trying to store a user’s LinkedIn credentials?

---

<div class="post-metadata">

**Author:** ![customautosys](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/customautosys/32/13540_2.png) [@customautosys](https://community.auth0.com/u/customautosys)\
**Post date:** [October 30, 2020, 11:39am UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/6 "2020-10-30T11:39:56Z")

</div>

Yes, basically my app needs to use the user’s LinkedIn email and password directly and thus I need them to key them into my app and not just into the auth0 login page.

I don’t want them to have to login again into auth0 (which means that they would have to key in their email and password a second time) after they have already keyed in their LinkedIn email and password into my app. Is there a way that my app can use the email and password which has already been entered by the user to login into auth0 via LinkedIn?

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [October 30, 2020, 8:02pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/7 "2020-10-30T20:02:09Z")

</div>

> [@customautosys](#):
>
> Yes, basically my app needs to use the user’s LinkedIn email and password directly and thus I need them to key them into my app and not just into the auth0 login page.

You can’t (and shouldn’t) do this. When a user logs in with LinkedIn, they are sent to [linkedin.com](http://linkedin.com) where they enter their credentials and a token is returned to the application if it is successful. You shouldn’t be handling passwords for a third-party identity provider.

If you want to get API access to a user’s LinkedIn account you can use their [IDP access token](https://auth0.com/docs/tokens/identity-provider-access-tokens).

---

<div class="post-metadata">

**Author:** ![customautosys](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/customautosys/32/13540_2.png) [@customautosys](https://community.auth0.com/u/customautosys)\
**Post date:** [October 31, 2020, 6:17am UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/8 "2020-10-31T06:17:06Z")

</div>

The problem is that I can’t use the LinkedIn public API for what I want to do (I would have to become a LinkedIn partner and LinkedIn rejected my application). Thus, I need to use the Voyager API which requires me to use the user’s email and password rather than a token.

---

<div class="post-metadata">

**Author:** ![customautosys](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/customautosys/32/13540_2.png) [@customautosys](https://community.auth0.com/u/customautosys)\
**Post date:** [October 31, 2020, 3:57pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/9 "2020-10-31T15:57:55Z")

</div>

Currently I’m using a JavaScript injection into the InAppBrowser to fill in the user’s email and password, however, that is obviously a hacky and undesirable solution.

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [November 16, 2020, 11:40pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/10 "2020-11-16T23:40:36Z")

</div>

@customautosys,

I am going to mark this as solved, as this is not something that we can recommend as it does not follow linkedIns TOS.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 1, 2020, 11:40pm UTC](https://community.auth0.com/t/automate-linkedin-sign-in-with-a-saved-email-and-password/51974/11 "2020-12-01T23:40:38Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
