Book Image

Moodle 3.x Developer's Guide

By : Ian Wild, Jaswant Tak
Book Image

Moodle 3.x Developer's Guide

By: Ian Wild, Jaswant Tak

Overview of this book

The new and revamped Moodle is the top choice for developers to create cutting edge e-learning apps that cater to different user’s segments and are visually appealing as well. This book explains how the Moodle 3.x platform provides a framework that allows developers to create a customized e-learning solution. It begins with an exploration of the different types of plugin.. We then continue with an investigation of creating new courses. You will create a custom plugin that pulls in resources from a third-party repository. Then you’ll learn how users can be assigned to courses and granted the necessary permissions. Furthermore, you will develop a custom user home. At the end of the book, we’ll discuss the Web Services API to fully automate Moodle 3.x in real time.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
6
Managing Users - Letting in the Crowds

Authentication


Luckily, Moodle supports a range of different authentication protocols out of the box, each one supported by its own plugin. We should say at the outset that this means that it is unlikely to be necessary for you to create a new plugin. So, before you do decide to create a new authentication plugin, it is best to make absolutely certain that your authentication requirements can't already be accommodated. To go to the list of available plugins, from the Administration block, click on Site administration, click Plugins, then click Authentication, and finally click on Manage authentication. The list of currently installed authentication plugins is displayed:

Each plugin interfaces with the Access API--see the Moodle developer documentation for details at: https://docs.moodle.org/dev/Access_API.

Authentication - general principles

The authentication process begins either because the user has attempted to log in directly at the login page (/login/index.php), or because the user has...