.. _moodle:

Connecting Moodle
=================

.. contents:: On this page
   :local:
   :depth: 2

Moodle 4.2 and later can auto-configure an LTI 1.3 tool from a single URL using **LTI Dynamic
Registration**. This is the fastest way to connect Moodle to Blocks.

Step 1: Create the platform in Blocks
-------------------------------------

#. In the workspace sidebar, open **Integrations**.
#. Create a new **platform** and choose the **Moodle 4.2** setup type.
#. Enter your Moodle site's issuer (its base URL) and save.

Step 2: Copy the dynamic registration URL
-----------------------------------------

#. Open the new platform's edit page in Blocks.
#. Copy the **record-specific dynamic registration URL**. It is tied to this platform record and
   looks like ``https://blocks.aulasneo.com/lti/register/?platform=<signed-token>``.

.. note::

   The signed token binds the registration to *this* platform record. This is why two different
   workspaces can connect the same Moodle site without sharing records — each uses its own signed
   URL.

Step 3: Register in Moodle
--------------------------

#. In Moodle, go to **Site administration → Plugins → External tool → Manage tools**.
#. Paste the dynamic registration URL into the **Tool URL** field and start the registration.
#. Moodle contacts Blocks, exchanges configuration automatically, and creates the tool.
#. Activate / approve the newly registered tool in Moodle.

Behind the scenes, Blocks fetches Moodle's OpenID configuration, registers itself with Moodle's
registration endpoint, and stores the resulting **registration** and **deployment** on your
platform record automatically.

Manual registration (fallback)
------------------------------

If you cannot use Dynamic Registration, create the registration manually:

#. On the platform edit page, use the suggested registration shortcut. Blocks pre-fills Moodle's
   token and keyset endpoints from the issuer (``/mod/lti/token.php`` and
   ``/mod/lti/certs.php``) and derives the authorization/login endpoint as ``/mod/lti/auth.php``.
#. Adjust these values if your Moodle deployment exposes different paths, then save.
#. Give Moodle the Blocks endpoints shown on the platform page (OIDC login, launch, JWKS, and
   Deep Linking URLs).

Step 4: Add an activity to a course
-----------------------------------

#. In a Moodle course, turn on editing and add an **External tool** activity.
#. Select the Blocks tool you registered.
#. Use **Select content** (Deep Linking) to open Blocks and choose a tool type. See
   :ref:`deep_linking`.
#. Save and return to the course. Learners can now launch the activity.

Troubleshooting
---------------

* **Registration fails immediately** — confirm your Moodle version supports LTI Advantage
  Dynamic Registration (Moodle 4.2+) and that the dynamic registration URL was copied in full,
  including the signed ``platform`` token.
* **Certificate / TLS errors** — if Moodle's certificate chain is not trusted, contact Aulasneo
  support; outbound trust settings may need adjustment on the hosted side.

`Back to Home <index.html>`_