The Moodle network feature allows a Moodle administrator to establish a link with another Moodle or a Mahara site and to share some resources with the users of that Moodle. Users go from the first Moodle to the linked site via the Network servers block.
The initial release of MNet is bundled with a Authentication Plugin, which makes single-sign-on between Moodles possible. A user with the username jody logs in to her Moodle server as normal, and clicks on a link that takes her to a page on another Moodle server. Normally, she would have only the privileges of a guest on the remote Moodle, but behind the scenes, single-sign-on has established a fully authenticated session for Jody on the remote site.
If you were using the webservice_xmlrpc plugin for integrations with other systems, be warned that it has been removed from core for Moodle 4.1 (see MDL-76052 for details). It's now available @ https://github.com/moodlehq/moodle-webservice_xmlrpc and has been also published in the Plugins directory. Note that, if you want to continue using this plugin, then you will need, before starting the upgrade process, to:
- Install the XMLRPC PHP extension, the webservice requires it.
- Install the webservice_xmlrpc plugin, from the links in the previous paragraph, into the webservice/xmlrpc directory.
- Then, and only then, start the upgrade process.
WARNING: MNet requires the use of xmlrpc. Please go to your phpinfo page if you are interested in using this and search for --with-xmlrpc. If your php has not been compiled with xmlrpc then you need to address that first! At present it appears that PEAR xmlrpc will not work.
The MNet feature requires that your server has the Curl and OpenSSL extensions installed. Your system will generate a OpenSSL certificate for encrypted communication with other Moodles, and will rotate encryption keys on a monthly basis (approx).
Communication takes place over an XML-RPC transport, and the XML-RPC documents are wrapped first in an XMLDSIG (XML digital signature) envelope, and then in an XMLENC (XML encryption) envelope. The encryption all happens within PHP, and does not require an https (Apache SSL) server.
A special mode can be enabled which would allow a machine with a specified IP address to make calls to the XML-RPC layer without using either encryption or signature envelopes. This mode is provided to enable Moodle to communicate with other software systems in which the integration of signatures and encryption might be prohibitively difficult. It is not envisioned that unencrypted inter-Moodle networking will ever be enabled.
Peer to Peer Network
This is the basic layout of the system. It can be very useful to run one Moodle per faculty or departments, each with its own user management, and yet permit users to roam across the Moodle installs... subject to permissions of course.
The instructions will cover 2 Moodle installations: MoodleA and MoodleB. Both are installed correctly and have never had a Moodle Network configuration.
Note: If you experience problems, ensure debugging is turned on in Administration > Site administration > Server > Debugging. Extra diagnostic messages may be displayed.
You need to first enable Networking in Administration > Site administration > Advanced Features. This will add the "Networking" menu to the Site Administration menu.
- Get them to talk to each other
- Ensure Administration > Site administration > Server > Environment indicates you have curl installed
- If MoodleA and MoodleB are hosted in the same domain, ensure they have a different cookie prefix. Note that changing the cookie prefix will log you out! You can change the cookie prefix via Admin > Server > Session Handling.
- On both, go to Administration > Site administration > Advanced Features and turn Networking ON.
- On MoodleA go to Administration > Site administration > Network > Manage peers - put the URL of MoodleB under "Add New Host" and click Add. The URL should include the directory where your Moodle code is located and may include the protocol as well, for example https://www.mymoodle.org/moodle.
- Do the equivalent on MoodleB.
- Get user roaming going
 ). On both servers:
- Go to Administration > Site administration > Plugins > Authentication > Manage authentication. Enable MNet Authentication by clicking the 'enable' icon.
- On MoodleA go to Administration > Site administration > Networking > (Manage) Peers, click on 'MoodleB', and click on the 'Services' tab. Enable SSO-IDP (SSO Identity Provider) publish and subscribe, and SSO-SP (SSO Service Provider) publish and subscribe.
- Do the equivalent on MoodleB. (By both publishing and subscribing you allow users to move freely between the two servers. By only publishing or subscribing between servers you create a one way traversal)
- On both, go to Administration > Site administration > Users > Permissions > Define Roles, only roles that have "Roam to a remote Moodle moodle/site:mnetlogintoremote" will be allowed to roam. Grant the privilege as appropriate.
- eg. enabling for Authenticated user allows any authenticated user to roam between servers.
- On both servers, go to the homepage, and add the 'Network Servers' block.
- To test, it is recommended to use a different browser (even on a different machine) that is logged in to neither. Login to MoodleA with a non-administrator account that has the permissions to roam. You should see the Network Servers block, and clicking on it you should go to MoodleB with a newly autocreated account.
- Get remote enrolments going -- this is optional. It allows an administrator of MoodleB to enrol users that are "native" to MoodleB in remote courses in MoodleA, and viceversa.
- On both, go to Site administration > Plugins > Enrolments > Manage enrol plugins and enable the Mnet remote enrolments plugin (click Save). Click on 'Edit' and enable 'allow_allcourses' or select some courses or categories to be remotely enrolled.
- On the server you want to receive enrolments:
- Go to Site administration > Plugins > Enrolments > Manage enrol plugins. Enable MNet remote enrolments by clicking the 'enable' icon. (For MNet remote enrolments settings info see MNet remote enrolments)
- On MoodleA go to Admin > Networking > Peers, click on 'MoodleB', and click on the 'Services' tab. Enable Enrolment publish and/or subscribe.
- Do the equivalent on MoodleB.
- On every course you want to allow enrolments into:
- Enter course and go to Administration > Course administration > Users > Enrolment methods
- From Add method drop-down select MNet remote enrolments
- On the new screen select the Remote host you want to allow enrolments from, the Role for the enrolled users, and click save. (Note: you can only add a single MNet remote enrolments method per course.)
- In MoodleA go to Admin > Networking > Remote enrolments client. You will see MoodleB listed. Click on Edit enrolments button beside MoodleB and you will see a list of courses that MoodleB offers for remote enrolment. Click Edit enrolments, select the users you want to enroll, and then click Add to enroll them in the course.
Connecting to a Mnet hub
A Mnet hub (do not confuse it with the Community hub) is a Moodle server that is configured to accept connections from other Moodle servers, and to provide a set of services to users of these other servers. This guideline will direct you to connect to a Mnet hub, assess the services it has to offer, and enable those services for your users.
- Get talking to the Hub
- Ensure that the Admin > Server > Environment page indicates you have curl and openssl installed
- Go to Admin > Advanced Features and turn Networking on
- Go to Admin > Network > Peers and enter the URL of Mnet Hub under "Add New Host". Click Add
- The host details for the Mnet Hub should appear with the Site Name field already populated. Click Save changes
- The details will be written to your database and two new tabs will appear in this window: 'Services' and 'Logs'. Click Services
- A list of services will appear, each with a checkbox for 'publish' and 'subscribe'. Check the checkboxes for any services you want to publish or subscribe to
If the Mnet Hub has already enabled a service for you, there will be a tick alongside the appropriate checkbox, for example: if the Hub is publishing Moodle Networked Enrolment, then a tick will appear alongside the subscribe checkbox for this service. Note that in order to enable some functionality, prominently single-sign-on, you may have to publish a service, e.g. the Identity Provider service. The Mnet Hub will access this service on your Moodle, asking it to authenticate your users.
- Enable Roaming
- Subscribe to SSO (Service Provider) by checking the box
- Publish SSO (Identity Provider) by checking the box
- Click Save changes
- Go to Admin > Users > Permissions > Define Roles, and grant the capability Roam to a remote Moodle moodle/site:mnetlogintoremote to an appropriate role
- Go to Administration > Plugins > Authentication > Manage authentication and enable the Moodle Network authentication plugin
- Go to your homepage, turn on editing, and add the 'Network Servers' block
- Using a different web-browser, log on as a non-admin user who inhabits the role you granted the roaming capability to
- Note that the Mnet Hub is listed in the Network Servers block on the homepage. Click on the link to that server
- Some of your user details will be transferred to the Mnet Hub server, and a browsing session will be started for you as if you had logged on there directly
- Enable Networked Enrolment
- Return to the web browser you've been using as the site administrator
- Go to Admin > Network > Peers and click on the entry for the Mnet Hub.
- Click on the Services tab
- Subscribe to Moodle Networked Enrolment
- Go to Site administration > Plugins > Enrolments > Manage enrol plugins and enable the Mnet remote enrolment plugin. Click Save changes
- Click on edit to view the details for networked enrolments.
- Go to Admin > Networking > Enrolments to see a list of Moodle servers that offer this service to you
- Click on a server name to view a list of courses that the server offers to your users
- Click on a course name, to view a list users that you can enrol in this course
- Enrol users
Running a Mnet hub
A Mnet hub is a regular Moodle site that runs in a special mode. As a Moodle Administrator, when you add another Moodle site to your list of network peers, your Moodle will contact that site to find out what it is called, and to request its public key for encrypted communication. Normally, the remote server will simply provide this information without making any record of the transaction.
A Mnet hub is different. As soon as you add an entry for a Mnet hub to your system, the Mnet hub will create an entry for your server in its list of hosts, and may immediately begin to offer services to the users of your site.
This section will guide you to set up a Mnet hub, and select services to offer to all comers.
- Ensure that the Settings > Site administration > Server > Environment page indicates you have curl and openssl installed
- Go to Settings > Site administration > Advanced Features and turn Networking on
- Go to Settings > Site administration > Network > Peers and tick the checkbox for Register all hosts. Click on Save Changes
- On the same page, the first entry in your list of hosts should be All hosts. Click this link
- Click on Services and enable any services you want to offer to all comers
Assigning the role of admin
For security reasons, users cannot be assigned the role of admin via the Moodle interface. Instead, admin user IDs must be listed in config.php e.g.
$CFG->siteadmins = '2,45,67';
Note: This applies to local admins as well as remote admins, as this overrides any local DB stored settings that assign administrative permissions.