EasyCoach supports launching roleplays in third-party platforms (such as Learning Management Systems) using the LTI 1.3 (Learning Tools Interoperability) standard.
LTI 1.3 enables secure roleplay delivery with Single Sign-On (SSO), allowing learners to access EasyCoach roleplays directly from their LMS without requiring a separate login. This ensures a seamless user experience while maintaining modern security standards.
This article outlines both the functional overview and the technical configuration required to implement LTI 1.3 with EasyCoach.
Not sure whether to use SSO or LTI?
Not sure whether to use SSO or LTI?
Both SSO and LTI let your learners open an EasyCoach roleplay without having to create a separate EasyCoach account or remember another password. The difference is how the roleplay reaches them:
SSO (OAuth or SAML) is about easy sign-in. You send learners a roleplay link (or add it to a course or page). When they click it, they log in with the same company account they already use for other work tools — and go straight into the roleplay. Use this when you want to share roleplays by link or place them inside a course.
LTI (1.1 or 1.3) is about opening roleplays from inside your learning system (LMS). If your organization already runs training through an LMS like Moodle, Canvas, or Cornerstone, LTI lets learners start the roleplay right there — and their scores are sent back into the LMS automatically. Use this when you want the roleplay to act as a training activity inside your LMS, with everything tracked in one place.
In simple words: SSO = an easy, no-extra-password way to log in. LTI = launching roleplays from your LMS, with results sent back to it.
Overview
LTI 1.3 allows an LMS (LTI Platform) to launch EasyCoach roleplays (LTI Tool) in a secure and standardized way.
When launched via LTI:
Learners are automatically authenticated
Roleplays open directly within the LMS
No additional login is required
User data is securely passed from the LMS to EasyCoach
User progress and results can optionally be shared back to the LMS
Basic Concepts
LTI Platform (LMS)
The platform that manages users and initiates secure launch requests. Examples include:
Cornerstone
Moodle
Canvas
Blackboard
SuccessFactors
LTI Tool (EasyCoach)
EasyCoach acts as the LTI Tool, delivering roleplay content when launched from the LMS.
How It Works
A learner selects a roleplay in the LMS.
The LMS initiates an LTI 1.3 launch request.
EasyCoach validates the request and authenticates the learner.
The roleplay is displayed within the LMS environment.
User progress and results can be shared back with the LMS (if configured).
Architecture diagram
Setup Process
LTI 1.3 setup requires exchanging configuration details between your LMS and EasyCoach.
Please provide the required configuration details using the following form:
Our team will use this information to configure the integration for your environment.
To proceed with the integration, please complete the LTI 1.3 configuration form. This form collects the required LMS configuration details and provides the EasyCoach endpoints needed for setup.
Generating an EasyCoach LTI 1.3 link
Once the connection is set up, you can generate an LTI 1.3 launch link for any roleplay directly in EasyCoach:
Open the roleplay you'd like to share.
Click Share.
Under Via link, click the arrow next to Normal link.
Select LTI 1.3 link.
Click Copy Link and use it to embed the roleplay into your course.
In EasyCoach, the LTI 1.3 link format looks like this:
https://easycoach.easygenerator.com/#/lti-launch/<roleplay_id>
EasyCoach fills in the roleplay identifier automatically when the link is generated — you don't need to construct it manually.
Technical Details (for LMS / IT Teams)
Authentication Model
EasyCoach's LTI 1.3 implementation is based on:
OAuth 2.0 (Authorization)
OpenID Connect (OIDC) (Authentication)
JWT (JSON Web Tokens)
The LMS sends a ID Token (JWT) which is validated by EasyCoach using public key authentication.
OIDC Login and Forwarded Query Parameters
During the LTI 1.3 launch process, the LMS initiates an OpenID Connect (OIDC) login request to EasyCoach. As part of this request, certain query parameters are forwarded to ensure a secure and valid launch.
Supported query parameters:
Parameter | Description |
login_hint | Identifies the user session in the LMS |
lti_message_hint | Provides launch context for the LTI message |
These parameters are passed from the LMS to EasyCoach during the OIDC login initiation.
Example OIDC login request
https://lti.easygenerator.com/api/v1/login
?iss=https://lms.example.com
&login_hint=abc123
<i_message_hint=xyz456 &target_link_uri=https://lti.easygenerator.com/course/launch
How it works
The LMS sends an OIDC login request to EasyCoach.
The request includes login_hint and lti_message_hint.
EasyCoach forwards these parameters to the authorization endpoint.
EasyCoach validates the request.
The learner is authenticated and the roleplay launches.
Notes
These parameters are part of the LTI 1.3 OpenID Connect flow.
The LMS automatically generates these parameters.
No manual configuration is typically required.
Missing parameters may cause launch failures.
Key Endpoints
Initiate Login URL
https://lti.easygenerator.com/api/v1/launch
This endpoint is used by the LMS to initiate the OpenID Connect login flow.
OIDC Redirect URI
https://auth.easygenerator.com/api/auth/oauth/<client_id>
This endpoint receives the authentication response from the LMS.
Required LMS Configuration
The LMS administrator must provide the following information:
Client ID
Platform Host (LMS base URL)
Authorization Endpoint
Token Endpoint
Public key endpoint (public key URL)
These details are required to establish secure communication between the LMS and EasyCoach.
User Information Mapping
User information is extracted from the ID token claims sent by the LMS during launch. Typical user attributes include:
Email
First Name
Last Name
User ID
If learner information is not provided by the LMS, EasyCoach may:
Display a default user name
Use a generated identifier
Limit certificate personalization
Token Details
Token type: JWT (JSON Web Tokens)
Signing algorithm: RS256
Authentication standard: OpenID Connect
Authorization standard: OAuth 2.0
Notes
LTI 1.3 does not use shared secrets.
Authentication is based on signed tokens.
Configuration must be completed on both LMS and EasyCoach sides.
Missing user claims may impact reporting and certificates.
Each LMS deployment may require separate configuration.
Difference from LTI 1.1
Feature | LTI 1.1 | LTI 1.3 |
Authentication | Shared secret | Public key (JWT) |
Security | Basic | Modern & secure |
SSO | Limited | Full OpenID Connect |
Scalability | Limited | High |
Standard | Legacy | Current standard |
LTI 1.3 provides improved security, scalability, and a better user experience compared to LTI 1.1.
User data and privacy
Your LMS controls what learner information is shared with EasyCoach. If learner details are not provided:
Certificates may not include learner names
Reporting may be limited
Default identifiers may be used
Support
If you need assistance with LTI 1.3 configuration, please contact [email protected].