Configure OpenID Connect Single Sign-On and Profile Synchronization - Article
Summary
Connect Eurekos with the identity system your organization already uses so learners can sign in through a familiar, governed route. Optional first-login account creation and login-time profile synchronization can reduce manual administration.
Authentication, account state, training enrollment and permissions remain separate decisions. A successful identity-provider login does not grant every Course or automatically manage the complete user lifecycle.
Use this article to:
- Configure the OIDC connection and intended login experience
- Choose account creation, mapping and synchronization behavior
- Verify existing-user matching, alternative access and lifecycle boundaries
Business context
A customer, partner network or internal organization may already manage identity in Microsoft Entra ID, Okta or OneLogin. Connecting that provider to Eurekos lets people use the established authentication process, including the policies configured for that route, while keeping training administration in Eurekos.
For example, a new distributor’s technician can authenticate through the distributor’s identity system. If automatic creation is enabled and the configured attributes are valid, Eurekos can create their account at that login and apply the intended profile values. Enrollment and learning access still follow their separately configured rules.
For an established audience, agree how incoming identities match existing accounts before rollout. The benefit is continuity of learning history and less duplicate administration; it depends on correct identifiers and mappings, not a universal guarantee that every identity will be matched automatically.
Separate the identity outcomes
| Capability | What it establishes |
|---|---|
| Authentication | The configured identity provider authenticates the user through OIDC |
| Auto-create a new user | Allows a new Eurekos account after successful authentication when no matching account exists |
| Synchronize user info on login | Updates mapped profile fields at login; synchronized fields become read-only locally |
| Eurekos enrollment and permissions | Separate rules determine the Training Activities, content and administrative functions available |
| Deactivation and departure | SSO authentication policy, Eurekos account state, sessions and other login routes must be governed together |
Synchronization happens at login. It is not continuous background provisioning. If the objective includes scheduled account creation, updates or blocking independently of login, assess the separately configured provisioning route, such as SCIM where supported.
How the identity exchange works
The learner follows the configured login route, authenticates with the identity provider and returns to Eurekos with the supported identity response. Eurekos processes the configured identifier, optional account creation and profile mappings, then applies its own access rules.
OIDC exchanges the configured identity claims through its client and endpoint configuration. Eurekos does not receive the identity provider’s password. Local password login, where deliberately enabled, remains a separate route with its own controls.
Login Experience and Behavior
Once configured, OpenID Connect becomes part of the Eurekos login experience and can be adapted to different user groups and access models.
Users may see SSO as a login option alongside other methods such as email/password, depending on how the login form is configured. Administrators control this behavior in Settings → Forms → Login.
Here, you can define:
- Which login methods are primary or secondary
- Whether SSO is visible or hidden
- How login options are presented to users
Multiple identity providers can be supported simultaneously, allowing flexibility across different user groups or organizational contexts.
This flexibility makes it possible to design login experiences that align with:
- Fully centralized identity environments
- Mixed audiences (internal and external users)
- Controlled rollout or testing scenarios
The following section outlines common login experience models and when to use them.
Login Experience Scenarios
Depending on how OpenID Connect and login settings are configured, different authentication experiences can be created in Eurekos. These configurations allow organizations to align login behavior with their user base, security requirements, and operational model.

| Scenario | Typical Use Case | Key Characteristics |
|---|---|---|
| SSO-only environment All users authenticate exclusively through the Identity Provider. The login process is fully centralized and controlled externally | Internal platforms where all users belong to the same organization and are managed in a central identity system (e.g. employees via Azure AD or a centralized partner portal) |
|
| Hybrid environment Both SSO and local login are available, allowing different user groups to authenticate using different methods | Platforms with mixed audiences, such as internal employees and external partners, customers, or learners |
|
| Hidden SSO SSO is enabled but not visible on the standard login screen. Access is provided through a direct login URL | Controlled access scenarios (funnels), also pilot groups, specific clients, or staged rollouts. Is sometimes used in combination with other scenarios |
|
How To Choose the Right Approach
The appropriate setup depends on your organizational context:
- Use SSO-only when all users are managed centrally and security policies must be enforced consistently
- Use Hybrid when supporting multiple user types with different identity sources
- Use Hidden SSO for controlled rollouts, testing, or segmented access strategies
💡 In practice, many organizations begin with a hybrid or hidden setup during implementation and transition to an SSO-only model once fully validated.
Existing Users, Login Behavior, and Transition to SSO
When OpenID Connect is introduced in an existing Eurekos environment, users may already have accounts created through email/password or manual administration.
Eurekos is designed to support a seamless transition to SSO without creating duplicate users or requiring manual migration.
Match existing users deliberately
Configure the unique identifier and incoming attributes with the identity owner. Test a representative existing Eurekos account before rollout and confirm that the same record, learning history and enrollments are retained. An incorrect identifier can produce a mismatch or unintended new account; do not promise duplicate-free migration without that check.
Use a limited pilot to resolve mismatches before enabling automatic creation for a wider audience. Do not delete a learner’s existing account as a shortcut for testing profile synchronization.
Login Behavior After SSO Is Introduced
Authentication behavior depends on how login options are configured.
If “Use regular login” is enabled:
- Users can log in using both SSO and email/password
- Users who authenticate via SSO may need to reset their password before using email/password login, as SSO accounts are assigned a system-generated password
If disabled:
- Users are expected to log in exclusively via SSO
- Authentication is fully delegated to the Identity Provider
Introduce SSO without losing the existing context
A platform with existing customers can retain its established records while introducing SSO. Start with a known account, verify the identifier and profile result, then extend to the intended group. Decide separately whether those users may retain regular login and how account departure will be handled.
User Provisioning and Profile Mapping
One of the most important aspects of the integration is how user data is transferred, interpreted, and structured within Eurekos. When a user logs in via OpenID Connect, Eurekos receives a set of attributes (claims) from the Identity Provider.
These attributes must be mapped to the corresponding user profile fields in Eurekos to ensure that users are created correctly and that their data is usable for reporting, grouping, and access control.
For example:
| Identity Provider Attribute | Eurekos Field |
|---|---|
| Email (unique identifier) | |
| given_name | First name |
| family_name | Last name |
| department | Department |
| manager | Immediate manager |
This mapping determines:
- How users are uniquely identified in the platform
- How they appear across the user interface
- How they are grouped, filtered, and reported on
- How they align with organizational structure and governance
Map received attributes to the intended fields
Open User profile attributes in the provider form and map the claims or attributes actually supplied by your identity provider. Visible labels can be customized; use the configured technical field identifiers and mapping syntax supplied for that integration rather than assuming a renamed label is the claim name.
For example, the visible label “Business Unit” does not tell the identity administrator which attribute or mapping expression to send. Agree the source attribute, target field, accepted values and missing-value behavior, then inspect the result in a pilot user profile.
Plan missing values and dynamic organization data
Set defaults only for fields that offer that option, and choose values appropriate for the incoming audience. Do not use a broad fallback to place unrelated customer or partner users into one privileged organization merely to make account creation succeed.
The supported organization/category mapping can create missing values during login. With login synchronization enabled, this can occur on subsequent logins as well as first creation; with synchronization disabled, the creation route applies when the user is first created. Do not assume that every arbitrary field, department or custom record is automatically created from any received string.
Review the exact organization, category and tag mappings with your identity owner. Test missing values, unfamiliar values and an existing user before relying on those assignments for access or reporting.
Synchronization Behavior
Synchronization determines how user data evolves over time and, more importantly, which system is responsible for maintaining that data.
When integrating with an Identity Provider, organizations must decide whether Eurekos should act as a consumer of identity data or retain some level of local control over user profiles. This decision has a direct impact on governance, reporting accuracy, and administrative workload.
The two approaches can be compared as follows:
| Aspect | One-time provisioning (static) | Synchronization at each login |
|---|---|---|
| Data lifecycle | Data is set once during initial login | Data is updated on every login |
| Source of truth | Eurekos (after creation) | Identity Provider |
| Updates from IdP | Not reflected automatically | Always reflected on login |
| Profile editing in Eurekos | Allowed | Restricted (read-only fields) |
| Administrative control | Local control within Eurekos | Centralized control via IdP |
| Typical use case | Flexible environments where data may differ from IdP | Enterprise environments with centralized identity governance |
| Risk/limitation | Data may become outdated over time | Less flexibility for local overrides |
Practical example
Consider a user who moves from the Sales department to Marketing in the Identity Provider.
- With one-time provisioning, the user remains assigned to Sales in Eurekos unless manually updated
- With login-time synchronization, the change is applied automatically on the next login
As a result:
- Reports reflect the correct department
- Access and grouping remain aligned with the organization
- The mapped change is applied at the next successful login
💡 Choose one-time provisioning for flexibility and local control, or login-time synchronization for consistency, scalability, and alignment with your identity system.
Configuration
Configuring OpenID Connect requires coordination between Eurekos administrators and the IT team managing the Identity Provider. The objective is not only to establish a secure connection, but also to ensure that authentication, user provisioning, and data governance behave as expected in your organization.
In practice, this means configuring both systems so that authentication works seamlessly and user data is structured correctly from the first login onward.
Step 1: Configure Identity Provider
The setup begins in your Identity Provider (e.g. Microsoft Entra ID, Okta, OneLogin), where Eurekos must be registered as an OpenID Connect application.
At this stage, you define how Eurekos is allowed to authenticate users and what identity data it will receive.
This typically involves:
- Creating an OpenID Connect application
- Defining the redirect URI (provided by Eurekos), which allows users to return to the platform after authentication
- Configuring scopes such as openid, email, and profile, which determine what identity data is shared
- Defining claims (attributes) such as email, name, department, or other organizational data
These attributes are critical, as they will later be mapped to Eurekos user profile fields. If attributes are missing or inconsistently defined, user provisioning may fail or result in incomplete profiles.
💡 In most implementations, this step is handled by IT, but it should be aligned with how user data is expected to appear and behave in Eurekos.
Step 2: Add the provider in Eurekos
Open Settings → Third party integrations → OpenID Connect and select Add identity provider. Give the connection a clear Name so users recognize it on the login page. Keep Enabled off until the connection is ready for the agreed pilot.
| Control or group | Meaning and decision |
|---|---|
| Client credentials | Enter the Client ID and Client secret from the intended identity-provider application |
| Endpoints and Scopes | Use the provider’s authorization, access-token and resource-owner details endpoints and the approved scopes |
| Token endpoint auth method | Match the provider’s supported POST/body or HTTP Basic/header credential method; do not assume POST is mandatory for every provider |
| Hidden | Suppress the visible login option when appropriate; the direct route is not thereby disabled |
After the provider record exists, use its displayed Redirect URL and test route when completing the identity-provider setup. Copy the exact production values from that record rather than a QA example.
Step 3: Configure account and profile behavior
Expand User profile attributes and map the agreed identifiers and profile values. Then configure the Synchronization and Regular login sections:
| Control | When to use it and effect |
|---|---|
| Auto-create a new user | Enable when a successfully authenticated identity may create a new Eurekos account; disable when accounts should already exist |
| Synchronize user info on login | Enable when the identity provider owns the mapped fields; later logins update them and make them read-only locally |
| Use regular login | Enable only when the SSO-linked user should also be allowed the local email/password route |
If a user is connected to several SSO providers, each must permit regular login for that password route to be available. An SSO-created account needs a usable password set through the supported reset process before local password login can be used.
Step 4: Agree the operating model
For a centrally managed partner population, login-time synchronization can keep mapped organization and contact details aligned with the source. For an external customer audience whose profile is maintained locally after creation, one-time provisioning may be more suitable. Use the earlier comparison to choose deliberately; changing a source attribute does not update a user who has not logged in again.
Keep enrollment and account departure in the same design discussion. Neither a mapped profile value nor the existence of an SSO account proves that the intended Training Activity is assigned.
Step 5: Configure the entry and exit experience
Use Settings → Forms → Login for the displayed login methods. Provider visibility and authentication permission are different controls: hiding a provider does not disable its direct login route.
| Control | Effect and practical boundary |
|---|---|
| Auto-login | Redirects the supported main-page login flow to the provider; only one identity-provider connection can use this option |
| Pre-login redirect URL | Defines a portal or intermediate entry before authentication; agree how the journey returns |
| After-logout redirect URL | Defines the destination after logout; it does not by itself establish logout from every connected system |
| Enable UUID for import/export files | Adds the provider-specific unique-identifier column to user import/export files where that workflow is needed |
The reserve login route is /user/reserve-login. Preserve and test the authorized administrative recovery route before changing the normal entry experience. With Auto-login, logout can lead to the confirmation page asking the user to close the browser tab; test that experience rather than assuming a global SSO logout.
Step 6: Save and run the agreed pilot
For OpenID Connect, Save and make test login can retrieve the mapped attributes as part of the test journey. It saves the configuration and performs a real login test; use an agreed account and preserve administrative access. Then use the complete verification table below with both new and existing accounts.
Verify the identity and learning journey
Test a pilot with a new user, a known existing account and representative incomplete or changed attributes. Use a fresh authentication session when checking changed source values.
| Scenario or check | Expected result or evidence |
|---|---|
| Protocol connection | The intended callback, endpoints/metadata, credentials and trust complete the sign-in round trip |
| Existing user | The configured identifier matches the original learner record and retains history, enrollment and permissions |
| New user | An account is created only under the configured auto-create policy and required attributes are valid |
| Mapped fields and renamed labels | The expected values reach the intended technical fields rather than a similarly named label |
| Missing data | Approved defaults or a clear validation outcome apply; no unintended privileged assignment |
| New organization/category value | Organization/category values are created according to the selected login synchronization mode |
| Profile changed at source | A subsequent login updates the mapped fields when synchronization is enabled; disabled sync retains local ownership |
| Mapped field editing | Synchronized fields are read-only locally where configured |
| Visible, hidden and direct entry | The intended audience can use its route; hidden display is not treated as blocked authentication |
| Auto-login and recovery | Only the chosen provider redirects the supported main-page login and the authorized reserve route is usable |
| Regular login and multiple providers | The chosen local-login policy applies, including password setup and all connected-provider restrictions |
| Identity-provider departure | A new authentication through that provider is denied; other login routes, sessions and Eurekos account state are reviewed separately |
| Training access | The intended enrollment and permissions produce the right learning access independently of successful authentication |
Standards and Security Considerations
The OpenID Connect integration in Eurekos is based on OpenID Connect (OIDC) 1.0, built on OAuth 2.0 and maintained by the OpenID Foundation. This ensures compatibility with enterprise identity providers such as Microsoft Entra ID, Okta, and OneLogin.
Standards And References
- OpenID Connect Core 1.0
- OAuth 2.0 Authorization Framework (RFC 6749)
- OpenID Connect Discovery
These standards define how authentication, token exchange, and identity data are securely handled.
Keep authentication and local access controls distinct
The identity provider applies its configured authentication policies to the SSO route. Eurekos processes the supported identity response and applies its account, permission and learning-access rules. Eurekos does not receive the provider’s password; if regular login is allowed, local password handling is a separate configured route.
MFA and conditional-access policies belong to the route on which they are configured. Do not assume a provider policy also governs an enabled alternative local login.
Plan deactivation across the complete journey
Blocking an identity at the provider can prevent a new authentication through that provider. It does not, by itself, prove that an existing Eurekos session has ended, that every alternative login has been disabled, that the Eurekos account is blocked or that enrollments have been cancelled.
Agree the account-deactivation and session policy separately. Where supported, provisioning such as SCIM can manage account updates and blocking independently of login-time synchronization. Verify the intended departure outcome with an agreed test account; do not rely on a successful SSO login test as evidence of revocation.
Common Identity Provider Configurations
While OpenID Connect follows a standard, each Identity Provider has its own terminology and setup flow. The configuration in Eurekos remains the same, but how values are obtained may differ slightly depending on your provider.
Below are common patterns to help align configuration across typical enterprise setups.
Microsoft Entra ID (Azure AD)
In Microsoft Entra ID, OIDC is configured through an App Registration.
- The Client ID corresponds to the Application (client) ID
- The Client Secret is created under Certificates & secrets
- The Authorization and Token endpoints are derived from the tenant’s OpenID configuration document
- User attributes (claims) are configured under Token configuration
A typical setup includes:
- Redirect URI pointing to Eurekos
- Scopes such as openid, profile, email
- Optional claims like department, job title, or manager
💡 In many organizations, Azure AD is also used to enforce MFA and conditional access policies, which automatically apply to Eurekos when using OIDC.
Okta
In Okta, OIDC is configured by creating a Web Application integration.
- The Client ID and Secret are generated automatically
- Endpoints are available via the Okta authorization server metadata URL
- Attributes are configured using claims mapping
Typical considerations:
- Ensure correct authorization server is used (default vs custom)
- Map attributes clearly (e.g. email, given_name, family_name)
- Test using Okta’s built-in preview tools before enabling in Eurekos
OneLogin
In OneLogin, OIDC is configured through a Custom Connector or OIDC app.
- Client credentials are generated during app creation
- Endpoints are defined per application
- User attributes are mapped through parameter mapping
Common setup includes:
- Defining user attributes explicitly (e.g. email, username)
- Ensuring consistent naming between OneLogin and Eurekos
- Validating token and user info endpoints
Key Takeaways Across Providers
Although setup steps differ slightly, the integration always depends on the same core elements:
- A registered OIDC application
- Client credentials (ID + Secret)
- Standard endpoints (authorization, token, user info)
- Properly defined user attributes (claims)
The most important success factor is alignment between the Identity Provider configuration and Eurekos attribute mapping.
Troubleshooting
| Problem | What to check |
|---|---|
| Login returns a protocol error | The intended application, exact callback and endpoints or federation metadata and trust |
| A duplicate or unexpected account is created | Unique identifier, source attributes, account matching and auto-create policy |
| Profile change is not reflected | Synchronize user info on login and a fresh subsequent authentication |
| A mapped field cannot be edited | Whether the field is deliberately owned by the identity provider |
| Hidden provider still works by direct URL | Hidden visibility is separate from disabling the connection |
| Provider-disabled user still has access | Existing sessions, local or other-provider login, Eurekos account state and the separately configured deactivation workflow |
| Training remains unavailable after sign-in | Enrollment and learning permissions rather than authentication alone |
FAQ
-
Do users need to be created in Eurekos before using OpenID Connect?
No. If auto-create user is enabled, users are created automatically when they log in via the Identity Provider for the first time. This is known as just-in-time provisioning.
-
What happens if a user already exists in Eurekos before SSO is enabled?
When the identifier supplied by the Identity Provider matches an existing Eurekos account, that account can be reused for SSO, retaining its training history. Agree the matching identifier and test both existing and new accounts before rollout. If the identifiers do not match, the outcome depends on the account-creation configuration; enabling SSO alone does not guarantee that duplicate accounts will be avoided.
-
Can users still log in with email and password after SSO is enabled?
Yes, if “Use regular login” is enabled. However, users who authenticate via SSO may need to reset their password before using email/password login, as SSO accounts are assigned a system-generated password by default.
-
What happens if a user is removed from the Identity Provider?
Disabling or removing the identity at the provider prevents new authentication through that provider. It does not by itself prove that the Eurekos account has been blocked or deleted, that every existing session has ended, or that another login route has been disabled.
For complete offboarding, review the user’s Eurekos status, existing sessions and any regular-login or alternative-provider access alongside the organization’s identity-management process. Do not rely on single sign-on alone as an account-deactivation workflow.
-
What is the most common cause of OpenID Connect configuration issues?
The most common issue is incorrect attribute mapping. This typically occurs when:
- The Identity Provider does not send the expected attributes
- Attribute names do not match the configured mappings in Eurekos
-
What is the Redirect URI and where do I find it?
The Redirect URI is the URL where users are returned after authentication. It is provided directly in the Eurekos OpenID Connect configuration screen and must be copied exactly into the Identity Provider setup.
-
Can Eurekos handle missing user data from the Identity Provider?
Use the defaults for fields that expose that option, and agree how required and missing attributes will be handled with the identity administrator. A default is not a general guarantee that every incomplete profile can be created.
Supported organization/category mappings can create missing values under the configured provisioning and login-synchronization behavior. Do not assume that every department, arbitrary profile field or custom record is automatically created. Test a missing value, an unfamiliar value and an existing account, and confirm that no fallback assigns an unintended privileged organization or access scope.
-
What is the difference between synchronization and provisioning?
- Provisioning refers to creating the user account on first login
- Synchronization refers to updating user data on subsequent logins
Synchronization can be enabled or disabled depending on whether the Identity Provider should remain the source of truth.
-
Can multiple identity providers be used at the same time?
Yes. Eurekos supports multiple OpenID Connect providers, allowing different login methods for different user groups (e.g. internal users via SSO and external users via email/password or another provider).
-
When should I use auto-login?
Auto-login is recommended when all users authenticate via a single Identity Provider, such as in internal environments. It creates a seamless experience by automatically redirecting users to SSO without requiring them to choose a login method.
-
Does hiding the OIDC provider prevent login through its direct URL?
No. Hiding the displayed login option is separate from disabling the provider. Test the direct route and use the appropriate account and provider controls for access restrictions.