Use Eurekos as a SAML Identity Provider for External Services - Article
Summary
When Eurekos is the main entry point for a customer or partner learning ecosystem, selected external services can trust Eurekos for authentication. This can reduce repeated sign-in without requiring every tool to use the same local password.
Eurekos supplies the SAML identity assertion. The receiving service still decides how it matches or creates an account, grants access and manages an existing session. The SAML IdP capability must be available and configured for the platform.
Use this article to:
- Decide when Eurekos should act as the identity provider
- Coordinate certificates, application identifiers and attribute mappings
- Verify the complete external login, access and departure journey
Business Context
In most identity integrations, Eurekos acts as a Service Provider (SP), relying on external identity systems such as Microsoft Entra ID, Okta, or OneLogin to authenticate users.
However, there are scenarios where Eurekos itself becomes the central system managing user identity and access across multiple platforms. In these cases, Eurekos is configured as a SAML Identity Provider (IdP).
This approach is typically used when Eurekos sits at the center of a broader digital ecosystem and needs to provide seamless access to connected systems.
Common use cases include:
- Launching external tools (e.g. webinar platforms, partner portals, or content systems) directly from Eurekos
- Providing a unified login experience across multiple learning-related systems
- Managing users and organizational structure centrally within Eurekos
- Supporting partner or customer-facing environments where Eurekos is the primary entry point
A practical example
A distributor’s technician starts in Eurekos and opens an external service configured to trust its SAML assertions. If the person already has a valid Eurekos session, that can avoid entering credentials again. The service checks the assertion, matches the identity and applies its own authorization rules.
For a webinar service, the identity connection supports authentication; it does not replace the separate registration, licensing or training-enrollment configuration. Test both relationships before describing the journey as ready for participants.
Why organizations use this approach
Using Eurekos as an Identity Provider is most relevant in environments where Eurekos is positioned as the central system for managing users and access across multiple platforms.
In these setups, external systems rely on Eurekos rather than maintaining their own identity layer. This is particularly valuable when:
- Eurekos manages the primary user base and organizational structure
- External systems should reuse the agreed identity rather than require a separate local password
- A consistent and controlled login experience is required across platforms
- Identity and access need to be governed centrally
By consolidating authentication and identity management in one place, organizations reduce fragmentation, improve the user experience, and ensure that access and user data remain aligned across the entire ecosystem..
Feature Overview
When Eurekos is configured as a SAML Identity Provider (IdP), it takes on the role of a central authentication and identity authority for connected systems. This means that external applications can delegate authentication while retaining their own account and authorization responsibilities. Instead, they rely on Eurekos to verify who the user is and provide the necessary identity data to grant access.
In practice, this introduces four closely connected capabilities:
1. Authentication → When a user attempts to access a connected system, authentication is handled by Eurekos.
The user is redirected to Eurekos and logs in using the available authentication method, which may include:
- Standard username and password
- Existing SSO (if Eurekos itself is connected to another Identity Provider)
- Multi-factor authentication (MFA), depending on configuration
At this stage, Eurekos is responsible for verifying the user’s identity. The external system does not handle credentials or authentication directly—it simply trusts the result provided by Eurekos.
Eurekos is now positioned as a central access point, ensuring that authentication policies and user verification are applied consistently across multiple systems.
2. Identity Assertion → Once authentication is successful, Eurekos generates a SAML assertion, which is a secure, standardized message that confirms the user’s identity.
This assertion contains:
- A unique identifier for the user (NameID, typically email)
- A set of user attributes (such as name, department, or organization)
- A confirmation that authentication has taken place
The assertion is digitally signed using a certificate, ensuring that the receiving system can verify both its authenticity and integrity.
From the perspective of the external system, this replaces the need for its own login process. Instead of asking the user to authenticate again, it trusts the assertion provided by Eurekos and uses it as the basis for access.
3. User Data Provisioning → Beyond authentication, Eurekos also provides structured user data to the external system as part of the SAML assertion.
This means that:
- User profile data in Eurekos is mapped to SAML attributes
- External systems receive consistent and up-to-date identity information
- Automatic creation or updates occur only where the target system supports and enables them
For example, when a user logs in:
- Their name, email, and organizational data are sent automatically
- The external system can create or update the user profile based on this data
- The receiving service determines whether the identity can use the service immediately or still needs account, permission or license setup
This significantly reduces administrative overhead and ensures that identity data remains consistent across platforms.
4. Access Control Delegation → By using Eurekos as the Identity Provider, external systems delegate both authentication and identity context to Eurekos.
This means that the external system relies on Eurekos to:
- Confirm whether a user is authenticated
- Provide the necessary identity attributes
- Indirectly control whether access should be granted
In effect, Eurekos becomes the source of truth for user identity and access eligibility.
For example:
- A valid Eurekos identity can be evaluated against the external service’s access rules
- Blocking a Eurekos identity affects subsequent authentication; existing external sessions and alternative login routes need separate review
This creates a shared authentication relationship while each external service retains the permissions and session controls required for its own functions.

How the Integration Works
The SAML IdP integration is best understood as a trusted identity exchange between Eurekos and external systems, rather than a simple login redirect.
When a user accesses a connected system, the external platform does not authenticate the user directly. Instead, it relies on Eurekos to perform authentication and confirm identity.
A typical flow looks like this:
- The user attempts to access an external system
- The system redirects the user to Eurekos for authentication
- The user logs in (if not already authenticated)
- Eurekos generates a signed SAML assertion
- The assertion is sent back to the external system
- The external system validates the assertion and applies its own access rules
From the user’s perspective, this happens almost instantly and without interruption. They move between systems without needing to log in multiple times. From a system perspective, responsibilities are clearly separated:
- Eurekos handles authentication and identity
- External systems trust and consume that identity
This separation is what makes the integration both secure and scalable.
Agree responsibilities before setup
| Owner | Responsibility |
|---|---|
| Eurekos platform owner | Confirm SAML IdP availability, certificate ownership, application setup and permitted identity attributes |
| External service owner | Confirm SAML support, required license, account matching/provisioning and authorization |
| Joint rollout team | Test new and existing identities, missing attributes, alternative login and session/deactivation behavior |
Account sharing is not the goal. Use one mapped identity per person and check that a returning user is matched to the correct external record.
Configuration
Configuring Eurekos as a SAML Identity Provider is not just about connecting two systems—it defines how identity is established, verified, and shared across your ecosystem.
At a technical level, the configuration ensures that:
- Eurekos can authenticate users
- Eurekos can generate trusted SAML assertions
- External systems can validate and consume those assertions correctly
This is achieved by aligning three core elements:
- Trust → via certificates and metadata
- Identity → via NameID and attributes
- Flow → via endpoints such as the ACS URL
This is a configuration-dependent capability. If SAML IdP is unavailable in Settings → Third party integrations, ask Eurekos to confirm availability and activation before planning the setup. Do not confuse it with SAML, which is the opposite direction: Eurekos trusting another identity provider.
Step 1: Enable and Prepare SAML IdP
Navigate to Settings → Third party integrations → SAML IdP.
Before configuring any integrations, Eurekos must be prepared to act as a trusted Identity Provider. This involves setting up the components used to sign and expose identity information:
- A certificate, used to digitally sign SAML assertions
- An Entity ID, which uniquely identifies Eurekos as the Identity Provider
- An SSO endpoint, where external systems redirect users for authentication
- A metadata URL, which exposes all of the above in a standardized format
The certificate plays a critical role. Every SAML assertion generated by Eurekos is signed using this certificate, allowing the external system to:
- Verify that the assertion originates from Eurekos
- Ensure the content has not been tampered with
💡 Without a valid certificate and metadata, external systems cannot establish trust and will reject authentication attempts.
Step 2: Create the external application connection
Where enabled, open the SAML IdP Applications area and select Create application. Use the receiving service’s actual values:
| Field | Purpose |
|---|---|
| ACS URL | The external service endpoint that receives the SAML response |
| Entity ID | The identity of the intended receiving service |
| Name ID format and Name ID | The agreed unique identifier and format used for matching the person |
Names used as attribute keys are configuration identifiers, not the literal first name or email address of a sample person. Match those keys to the receiving service’s documented expectations.
Step 3: Configure Attribute Mapping
Once the connection is defined, the next step is to control exactly what identity data Eurekos shares with the external system. When a user authenticates, Eurekos generates a SAML assertion containing:
- A NameID (unique user identifier)
- A set of SAML attributes, derived from the user’s profile
Attribute mapping defines how Eurekos user profile fields are translated into these SAML attributes.
For example:
- Eurekos email → email (or NameID)
- Eurekos first name → first_name
- Eurekos last name → last_name
- Eurekos organization → organization
These values are embedded in the SAML assertion and sent to the external system during login. From the receiving system’s perspective, this data is used to:
- Identify the user uniquely
- Create or update the user account
- Assign roles, permissions, or access based on attributes
This step therefore determines:
- How users are identified across systems
- What data is available for provisioning and access control
- How consistently identity is represented across platforms
💡 If an expected attribute is missing or incorrectly named, authentication may succeed but the user may not be created correctly or may not receive the expected access.
Step 4: Share Metadata and Establish Trust
Once the application is configured, Eurekos provides a metadata URL containing all Identity Provider details.
This metadata includes:
- SSO endpoint
- Entity ID
- Signing certificate
- Protocol configuration
The external system uses this metadata to:
- Establish trust with Eurekos
- Validate incoming SAML assertions
- Configure its authentication flow
Using metadata ensures that both systems remain aligned and reduces the risk of manual configuration errors.
Step 5: Configure the External System (Service Provider)
In the external system, Eurekos must be registered as the Identity Provider.
This typically involves:
- Importing the Eurekos metadata
- Defining the expected NameID format
- Configuring required attributes
- Enabling SAML-based authentication
At this stage, the external system defines:
- How it interprets the incoming assertion
- Which attributes are required for access
- How users are created or matched
This is where alignment is critical—both systems must agree on identifiers and attribute names.
Step 6: Run the agreed pilot
Use a non-privileged test identity agreed by both system owners. Test a new identity and a returning external account, then review the full table below. Do not use a platform administrator account merely to see whether a connection works: an incorrect mapping can link or update the wrong identity.
Verify the external-service outcome
| Scenario or check | Expected result or evidence |
|---|---|
| Authentication round trip | The user reaches Eurekos when needed and returns to the intended service |
| ACS URL and Entity ID | The assertion reaches the correct receiver and is intended for that application |
| Certificate trust | The receiving service validates the agreed signature and current certificate |
| NameID and attributes | The intended technical keys and required values identify the correct person |
| Existing external account | The agreed matching policy reuses the correct record without unintended relinking |
| New external identity | Creation occurs only if the receiving service supports and enables it |
| Missing or partial attributes | A predictable validation outcome occurs without unintended access |
| Permissions and licensing | The external service grants only the access and entitlements intended for that person |
| Departure and alternate login | New authentication, existing external sessions and alternative routes are tested separately |
| Certificate renewal | Both owners know how trust is renewed before the signing certificate expires |
Troubleshooting
| Problem | What to check |
|---|---|
| SAML IdP configuration is unavailable | Feature activation and platform access with Eurekos; the ordinary SAML connection is a different direction |
| The service rejects the assertion | ACS URL, audience/Entity ID, signing certificate and NameID format |
| Login succeeds but access is wrong | Receiving-service authorization, account matching, licensing and the actual attributes |
| An external account is not created | Whether the service supports and enables creation from SAML assertions |
| A blocked user still has an external session | The receiving service’s session lifetime and alternative login paths, separately from new SAML authentication |
FAQ
-
What is the role of Eurekos in a SAML IdP setup?
Eurekos acts as the Identity Provider, meaning it authenticates users and sends verified identity data to external systems, which rely on Eurekos to grant access.
-
Do users need separate accounts in external systems?
The learner authenticates through Eurekos, but the external service still decides whether it requires an existing account, supports automatic account creation, or needs a license or additional permission. SAML IdP supplies the configured identity assertion; it does not guarantee provisioning or authorization in every connected service.
Agree account matching, required attributes, provisioning and access rules with the external service owner, then test the complete learner journey.
-
What is a SAML assertion?
A SAML assertion is a secure, signed message generated by Eurekos after authentication. It contains the user’s identity (NameID) and mapped attributes used by the external system.
-
What is the NameID and why is it important?
The NameID is the unique identifier for the user, typically an email address. It is used by the external system to match or create user accounts.
-
What happens if attribute mapping is incorrect?
Authentication may still succeed, but users may not be created correctly or may not receive proper access in the external system.
-
What is the ACS URL?
The Assertion Consumer Service (ACS) URL is the endpoint in the external system where Eurekos sends the SAML response after authentication.
-
Why is a certificate required?
The certificate is used to sign SAML assertions. External systems use it to verify that the assertion is authentic and has not been modified.
-
Can Eurekos integrate with multiple external systems?
Yes. Each external system is configured as a separate SAML application, allowing Eurekos to act as a central Identity Provider across multiple platforms.
-
What happens when a user is removed or deactivated in Eurekos?
A learner who can no longer authenticate in Eurekos cannot use that Eurekos identity to complete a new SAML sign-in to the external service.
Do not assume this also terminates an external session that is already active, deletes the external account, removes a license or disables a separate login route. Those controls belong to the external service. Include both systems in the organization’s offboarding checks.
-
How do I troubleshoot login issues in a SAML setup?
Start by checking:
- ACS URL and Entity ID alignment
- Certificate validity
- NameID and attribute mapping
- SAML assertion logs in the external system
Most issues are caused by configuration mismatches rather than system errors.
-
What is the difference between SAML and SAML IdP in Eurekos?
With SAML, Eurekos trusts an external identity provider. With the optional SAML IdP capability, an external service trusts Eurekos for authentication. They configure opposite directions of the trust relationship.