LinkedIn Social Login Integration Guide
Last updated
Was this helpful?
Last updated
Was this helpful?
Log in to LinkedIn's Developer Portal and create an application. Once the application is created, LinkedIn will generate a Client ID and Client Secret.
Here’s how to proceed with the process.
A: Visit LinkedIn Developer Portal - Go to:- Log in with your LinkedIn account. B: Create a New App - Click on “My Apps” in the top navigation. - Click the “Create app” button.
C: Fill in App Details: You'll be asked to provide the following: - App Name (e.g., JobSphere Login Tool) - LinkedIn Page (your company’s LinkedIn page – required) - App Logo (100x100 PNG or JPG) - Business Email - Accept the LinkedIn API Terms of Use - Click Create app after filling in the details.
D: Get Client ID and Client Secret - Once your app is created, go to the Auth tab of your app dashboard. - Here, you'll see - Client ID and Client Secret (Click “Show” to reveal) - Copy both for your application’s OAuth setup.
Important: The client must share these credentials with the Artha Support Team, who will add them to the backend. The client does not need to configure or add them anywhere.
Ensure that the callback/redirect URL is set correctly in LinkedIn's Developer Portal: https://api.arthajobboard.com/social-auth/linkedin/callback
Once Artha Support confirms the integration, the client can test the login.
Ensure Correct Branding:
The application name, logo, and other branding settings should reflect the client’s identity.
Confirm Redirect URL:
The redirect URL configured in LinkedIn Developer Portal should match the one provided above.
The Client should wait for confirmation from Artha Support before testing.
Perform login tests to ensure smooth user authentication and correct branding.
Check for Artha Branding: Ensure no references to Artha (e.g., logos, names) appear.
Once confirmed, the social login will be active.
Monitor login success rates via analytics or server logs.
Regularly review credentials and rotate the Client Secret as per security best practices.