DataCamp supports LTI 1.3 integrations that allow your users to seamlessly access learning content hosted by external partners directly within the DataCamp platform. In this setup, DataCamp acts as the LTI Platform (LMS) and the external content provider acts as the LTI Tool.
This article covers how this integration works, what's needed to set it up, and what privacy protections are in place.
How It Works
When a DataCamp user navigates to partner content, the following happens behind the scenes using the standard LTI 1.3 / OIDC Third-Party Initiated Login flow:
1. Launch initiation - DataCamp redirects the user's browser to the partner's Login URL with standard LTI parameters including a login_hint, target_link_uri, and DataCamp's issuer.
2. OIDC redirect - The partner validates the request and redirects back to DataCamp's Authorization Endpoint with standard OIDC parameters (scope=openid, response_type=id_token, response_mode=form_post).
3. Token issuance - DataCamp authenticates the user, signs a JWT id_token containing LTI 1.3 claims, and POSTs it to the partner's registered Redirect URI.
4. Content display - The partner validates the token using DataCamp's public JWKS endpoint and renders the requested content.
The entire flow is transparent to the end user — they click on content within DataCamp and are seamlessly authenticated into the partner's platform.
What the Partner Needs to Provide
To register a new LTI integration, the partner must share:
- Login Initiation URL - where DataCamp sends the initial LTI login request
- Redirect URI(s) - where DataCamp POSTs the signed `id_token` after authentication
- Base Domain URL - the partner's top-level integration domain
- JWKS URL or Public Key (optional) - for validating any JWTs originating from the partner
What DataCamp Provides
DataCamp will share the following OIDC/LTI configuration details:
| Parameter | Value |
| Issuer | https://partner-content-integrations.datacamp.com |
| OpenID Configuration | https://partner-content-integrations.datacamp.com/oidc/.well-known/openid-configuration |
| JWKS URI | https://partner-content-integrations.datacamp.com/oidc/jwks |
| Authorization Endpoint | https://partner-content-integrations.datacamp.com/oidc/auth |
In addition, DataCamp and the partner will agree on:
- Client ID - a unique identifier for the partner (used as the `audience` in the `id_token`)
- Deployment ID - a UUID identifying the specific deployment
Getting Started
If you are a content provider interested in making your content available on DataCamp via LTI 1.3, please reach out to your DataCamp partnership contact to begin the integration process.
The setup involves:
1. Exchanging the configuration details listed above
2. Agreeing on a content catalog and identifiers
3. Testing the integration in a staging environment
4. Going live