Book Image

Moodle 4 Administration - Fourth Edition

By : Alex Büchner
Book Image

Moodle 4 Administration - Fourth Edition

By: Alex Büchner

Overview of this book

This updated fourth edition of the classic Moodle Administration guide has been written from the ground up and covers all the new Moodle features in great breadth and depth. The topics have also been augmented with professional diagrams, illustrations, and checklists. The book starts by covering basic tasks such as how to set up and configure Moodle and perform day-to-day administration activities. You’ll then progress to more advanced topics that show you how to customize and extend Moodle, manage authentication and enrolments, and work with roles and capabilities. Next, you'll learn how to configure pedagogical and technical Moodle plugins and ensure your LMS complies with data protection regulations. Then, you will learn how to tighten Moodle’s security, improve its performance, and configure backup and restore procedures. Finally, you'll gain insights on how to compile custom reports, configure learning analytics, enable mobile learning, integrate Moodle via web services, and support different types of multi-tenancy. By the end of this book, you’ll be able to set up an efficient, fully fledged, and secure Moodle system.
Table of Contents (24 chapters)

Enabling web services for users

It is sometimes necessary for users to have to access web services directly instead of applications – for example, a developer who needs to execute test runs against the system. The process is a subset of steps already covered in the previous section and follows the Users as clients with token section on the web services overview screen:

Figure 18.12 – Web services for users as clients with tokens

These steps should be familiar by now; there are only two minor deviations from the previous scenario when web services were allowed for external systems instead of users.

In step 3, the Authorized users option must be unchecked. In addition to the protocol use capabilities, the users must have the moodle/webservice:createtoken capability set to allowed (see step 5).

To test the service (see step 6), log in as the user, obtain a security token for testing, and avoid using the simple authentication method in the web...