What it is for
LTI (Learning Tools Interoperability) is the standard that connects an LMS to learning tools. From Administration → LTI connections, you declare each integration, and DGTLMS can play two roles:
- Tool Provider — DGTLMS is launched from an external LMS (Moodle, etc.).
- Platform — DGTLMS launches an external tool (e.g. Kahoot); this integration then feeds the LTI activities in your courses.
Both LTI 1.1 and LTI 1.3 are supported.
DGTLMS endpoints
The page shows your platform's addresses, which you give to the other system:
| Endpoint | Use |
|---|---|
| LTI 1.1 Launch URL | 1.1 launch point |
| LTI 1.3 OIDC Login | Start of 1.3 authentication |
| LTI 1.3 Redirect URI | 1.3 authentication return |
| LTI 1.3 JWKS URL | Public keys used to verify 1.3 tokens |
Generate the RSA keys (LTI 1.3)
For any 1.3 integration, first generate an RSA key pair (Generate a key pair button). This is a prerequisite: without keys, signed 1.3 exchanges cannot work.
Add an integration
Open
Administration → LTI connections, click Add.Integration name
A meaningful label (e.g. Kahoot, Moodle University X).
LTI version
1.1 or 1.3.
DGTLMS role
Tool Provider (launched from an external LMS) or Platform (launches an external tool).
User provisioning
How accounts are created/matched during launches.
Active
Turn the integration on or off without deleting it.
The list summarises all integrations (activate/deactivate, delete).
Link with a course's LTI activity
An integration in the Platform role is what then lets you add an LTI activity to a course (see "E-learning activities in detail"). The technical configuration is done here, once; the activity relies on it.
- 1.1 relies on a shared key + secret; 1.3 on OIDC + RSA keys (more secure).
- Give the endpoints above to the administrator of the other platform (and get theirs).
- Keep these settings for administrators: a badly configured integration blocks launches.