Enable LinkedIn Sign-In for Connected User Accounts - Article
Summary
Let learners use a familiar professional identity to sign in while retaining their existing Eurekos account and learning history. This can reduce login friction for customer and partner audiences without creating a second learning record.
Administrators configure the connection and login visibility. Each user connects LinkedIn to their Eurekos profile before signing in with it.
Use this article to:
- Configure the LinkedIn application and callback
- Enable the intended login experience
- Verify account connection and returning-user sign-in
Business context
For a professional customer or partner audience, LinkedIn can provide a convenient alternative to another set of login credentials. The benefit is a simpler returning-user journey while Eurekos continues to manage training enrollment, access and learning evidence.
The platform application is configured once. Individual users connect their own LinkedIn identity in their existing profile. That connection is distinct from publishing a LinkedIn profile link or sharing a certificate to LinkedIn; this article covers the supported sign-in workflow.
Understand the three required layers
| Layer | Purpose |
|---|---|
| LinkedIn application | Defines the permitted sign-in product and approved callback |
| Eurekos platform settings | Stores the connection and controls whether LinkedIn appears as a login method |
| User Connected accounts | Links the individual’s LinkedIn identity to their existing Eurekos account |
Keep the identity boundary clear
LinkedIn supplies the identity information needed by the configured sign-in connection. It does not create a Training Activity enrollment or establish certificate eligibility. Do not infer broader profile synchronization, advertising or content-sharing capabilities from this login integration.
Configuration Overview
To successfully enable LinkedIn integration, configuration must be completed across three layers:
- LinkedIn Developer Application (external setup)
- Eurekos Integration Configuration (platform setup)
- User Account Connection (user-level activation)
Each layer is required for the integration to function correctly.
Configuration
Step 1: Create LinkedIn Developer Application
The integration relies on a LinkedIn developer application, which acts as the secure bridge between LinkedIn and Eurekos.
Configuration steps: Go to: https://developer.linkedin.com.
- Click Create app
- Provide required application details:
| Field | Description |
|---|---|
| App name | Name of your integration |
| LinkedIn Page | Your organization’s LinkedIn page (required) |
| App logo | Visual identifier |
| Privacy policy URL | Required in some environments |
- Accept LinkedIn API Terms and create the application
- Complete verification with your LinkedIn business page if prompted
Enable the sign-in product
Enable Sign In with LinkedIn using OpenID Connect for the developer application. The current Eurekos configuration identifies the required scopes as openid, profile and email. Advertising and sharing products are not prerequisites for this sign-in workflow.
Step 2: Configure Authentication
Navigate to the Auth tab in your LinkedIn developer application. Configure the following:
| Field | Description |
|---|---|
| Client ID | Used in Eurekos configuration |
| Client Secret | Used in Eurekos configuration |
| Redirect URL | Must match Eurekos callback endpoint |
Add the redirect URL provided by Eurekos, for example: https://yourdomain/api/linkedin/callback
This ensures a secure OAuth authentication flow between LinkedIn and Eurekos.
Step 3: Configure LinkedIn in Eurekos
Navigate to Settings → Third Party Integrations → LinkedIn.
Enter the credentials from your LinkedIn developer application:
| Field | Description |
|---|---|
| Client ID | From LinkedIn |
| Client Secret | From LinkedIn |
| Redirect URL | Must match LinkedIn configuration |
Click Save to activate the integration.
If configured correctly, LinkedIn will become available in user profile connection options.
Step 4: Enable Login Functionality
The LinkedIn integration must also be activated at the platform level to make it available as a login option for users. This is controlled both by global settings and by how login methods are configured in the Login form.
The Login form determines which authentication methods are presented to users and in what order, meaning that even a correctly configured integration will not be visible unless it is explicitly enabled here.
Required configuration:
| Setting | Location | Requirement |
|---|---|---|
| Social login | Settings → General | Enable “Login with social accounts” |
| Login method visibility | Settings → Forms → Login | Ensure LinkedIn is enabled as a secondary method |
Within the Login form, LinkedIn will typically appear as a secondary login method, accessible via options such as “Log in another way”. Administrators can control its visibility and positioning alongside other login methods (e.g. SSO, email/password, Microsoft, Google), ensuring alignment with the overall authentication strategy.
⚠️ If either setting is not configured, LinkedIn login will not be available to users—even if the integration itself is active.
User Workflow: Connecting LinkedIn Account
Once the integration is configured, users must connect their LinkedIn account manually:
- Navigate to Profile → Connected accounts
- Click Connect next to LinkedIn
- Log in to LinkedIn
- Approve access permissions
After this process, the LinkedIn account is securely linked to the user profile.
Logging in with LinkedIn
After connecting their account, users can log in using LinkedIn:
- Select “Log in another way” on the login screen
- Choose LinkedIn login
- Authenticate via LinkedIn
⚠️ LinkedIn login will only work if the account has been connected beforehand. Otherwise, access will be denied.
Keep profile links and certificate sharing separate
A connected sign-in account is an authentication relationship. Do not treat it as proof that a public LinkedIn profile link is displayed or that certificate-sharing features have been configured. Verify those separate experiences where they are part of your intended use case.
Governance and Best Practices
To ensure a reliable and secure implementation, administrators should treat LinkedIn integration as part of the overall identity and access strategy.
| Recommendation | Why It Matters |
|---|---|
| Align with your identity strategy | Ensure LinkedIn login complements existing authentication methods (e.g. SSO, email login) |
| Validate redirect URL configuration carefully | Incorrect URLs are the most common cause of failed authentication |
| Communicate clearly to users | Users must connect their LinkedIn account before login becomes available |
| Control login visibility intentionally | Only enable LinkedIn login where it adds value to the user experience |
| Limit enabled LinkedIn products | Avoid unnecessary complexity by enabling only required features |
| Test the full user journey | Validate connection, login, and profile display end-to-end before release |
Verify the sign-in journey
| Check | Expected result or evidence |
|---|---|
| Platform configuration | Client ID and Client secret belong to the intended LinkedIn app; its callback matches the displayed Redirect URL |
| Login visibility | Login with social accounts is enabled and LinkedIn is exposed in the Login form |
| Initial connection | The existing user connects the intended LinkedIn identity in Connected accounts |
| Returning login | That same identity returns to the intended Eurekos account and retained learning history |
| Unconnected identity | The user receives the connection requirement rather than an assumed new training account |
Troubleshooting
| Problem | What to check |
|---|---|
| LinkedIn does not appear on the login form | Integration settings, Login with social accounts and Login form visibility |
| Account should be connected message appears | Connect LinkedIn from the existing Eurekos profile first |
| Callback or consent fails | Exact Redirect URL, current developer product access and openid, profile, email scopes |
| A different learner record is expected | Confirm the identity linked to the existing account before attempting another connection |
FAQ
-
Can a learner use LinkedIn login before connecting it to their Eurekos profile?
The flow requires LinkedIn to be connected to the existing user profile first. The learner connects it through Connected accounts, then uses that same LinkedIn identity to sign in.
-
Does LinkedIn sign-in also configure certificate sharing or advertising?
No. This connection establishes a sign-in relationship. Certificate sharing and advertising are separate capabilities and are not prerequisites for LinkedIn login.