This solution lets Moodle distribute all or part of its user account information to “friendly” applications, allowing a simple transfer of a user's identity to that application. It is then up to that application to use this identity data to expose a service or create a local user account.

This local plugin implements an integration of the PHP League OAuth2 server framework, plus the OIDC layer, to act as an OIDC identity server for other client applications.

In this scenario, the “friendly” application will not log users in itself, but will delegate the authentication phase to the Moodle carrying the embedded OIDC server. A session will be established on the IDP Moodle, as well as in the client application.

The server supports the SLO (Single Logout) function, which removes the IDP session when the user logs out of the friendly application.

This server relies on the central definition of OAuth2 services in a standard Moodle. As a result, an IDP can serve as many clients as exist in its central configuration.

In the case of an application federation, the SLO function, if the clients provide a “Logout” entry point, will ensure that all applications in session attached to the IDP session are disconnected at the same time.

• Installation guide
• User guide
• Technical guide

• Provides an identity server function
• OAuth authorisation server
• OAuth token server
• Handles the openid, email, profile scopes (by default)
• User info endpoint
• SLO endpoint
• Authentication screen
• Supports non-local Moodle accounts

Administration:

• Administration of authorised clients
• Administration of scopes

• Filtering of authorised users per client through an evaluable expression engine (Moodlescript)
• Exclusion of unauthorised users per client through an evaluable expression engine (Moodlescript)

Administration:

• View of authorisation tickets (planned)
• Local mapping of scopes

• Component type: Local plugin
• Name: OidcServer
• Technical name: local_oidcserver
• Supported versions: to
• Distribution: Community and PRO

Note: a “Failing” status does not necessarily mean that the plugin does not work. This status reflects the result of automated tests checking the code against Moodle's strict standards. We are continuously working on bringing all supported plugins progressively into compliance with these development rules.

Branch	Continuous integration tests
405
501

Plugins index - Catalogue home