LinkedIn SDR Auth Configuration FAQs

Question 1

Do I need to update these settings frequently?

Accepted Answer

Authentication remains valid as long as your browser session is active. If you log out of LinkedIn or your session expires, you will need to re-run the configuration to update the tokens.

Question 2

Why does this skill require manual cookie extraction?

Accepted Answer

Since LinkedIn does not provide a public API for SDR-style actions like commenting, the plugin uses the internal Voyager API which requires active session cookies (li_at and JSESSIONID) to function.

Question 3

How do I find my JSESSIONID and li_at values?

Accepted Answer

You can find these by opening LinkedIn in your browser, accessing Developer Tools (F12), navigating to the 'Application' or 'Storage' tab, and looking under the 'Cookies' section for linkedin.com.

Question 4

What is a CSRF token in this context?

Accepted Answer

The CSRF token is derived from your JSESSIONID by removing the 'ajax:' prefix and surrounding quotes. It is a security requirement for making POST requests to LinkedIn's internal APIs.

Question 5

How do I know if the authentication was successful?

Accepted Answer

The skill includes a built-in test command that attempts to fetch your LinkedIn profile data. If the API returns your profile information, the authentication is correctly configured.

LinkedIn SDR Auth Configuration

主要功能

使用场景

LinkedIn SDR Auth Configuration

主要功能

使用场景