OAuth 2 services: Difference between revisions
m (added link to Spanish translation of page) |
Helen Foster (talk | contribs) (Category:OAuth 2, OAuth 2 authentication, see also) |
||
| Line 2: | Line 2: | ||
==OAuth2 services== | ==OAuth2 services== | ||
Moodle 3.3 adds support for OAuth 2 services | Moodle 3.3 adds support for OAuth 2 services, which can be used by any plugin to provide authenticated access to external services either as the current user, or using a system account. | ||
OAuth 2 services are used for example, to provide a "Login using Google/Microsoft/Facebook" feature on the login page, and then to share that authenticated session with repositories like Google Drive and Office 365 without having to re-authenticate. | OAuth 2 services are used for example, to provide a "Login using Google/Microsoft/Facebook" feature on the login page, and then to share that authenticated session with repositories like Google Drive and Office 365 without having to re-authenticate. | ||
| Line 10: | Line 10: | ||
== Login == | == Login == | ||
See [[OAuth 2 authentication]] for details of how to enable the feature. | |||
== Open ID Connect == | |||
Open ID Connect is a standard for OAuth 2 login services that makes it easier to setup a working login system. If the service you are setting up is Open ID Connect compliant, you will only have to enter the base url for the service, and Moodle will discover all the other information required by requesting the "discovery document" which is expected to exist at <issuer base url>/.well-known/openid-configuration. | Open ID Connect is a standard for OAuth 2 login services that makes it easier to setup a working login system. If the service you are setting up is Open ID Connect compliant, you will only have to enter the base url for the service, and Moodle will discover all the other information required by requesting the "discovery document" which is expected to exist at <issuer base url>/.well-known/openid-configuration. | ||
== How do I get a client ID and secret? == | |||
The client ID and secret are created outside of Moodle when setting up the OAuth provider. Instructions for prominent OAuth 2 providers are linked here. | The client ID and secret are created outside of Moodle when setting up the OAuth provider. Instructions for prominent OAuth 2 providers are linked here. | ||
| Line 29: | Line 24: | ||
* [[OAuth 2 Facebook service]] | * [[OAuth 2 Facebook service]] | ||
==See also== | |||
* [[:Category:OAuth 2]] | |||
[[Category:OAuth 2]] | |||
[[es:Servicios OAuth 2]] | [[es:Servicios OAuth 2]] | ||
Revision as of 10:14, 14 May 2017
OAuth2 services
Moodle 3.3 adds support for OAuth 2 services, which can be used by any plugin to provide authenticated access to external services either as the current user, or using a system account.
OAuth 2 services are used for example, to provide a "Login using Google/Microsoft/Facebook" feature on the login page, and then to share that authenticated session with repositories like Google Drive and Office 365 without having to re-authenticate.
OAuth 2 services can be used by plugins even if they do not use them on the login page, and it's possible to login to multiple services at the same time.
Login
See OAuth 2 authentication for details of how to enable the feature.
Open ID Connect
Open ID Connect is a standard for OAuth 2 login services that makes it easier to setup a working login system. If the service you are setting up is Open ID Connect compliant, you will only have to enter the base url for the service, and Moodle will discover all the other information required by requesting the "discovery document" which is expected to exist at <issuer base url>/.well-known/openid-configuration.
How do I get a client ID and secret?
The client ID and secret are created outside of Moodle when setting up the OAuth provider. Instructions for prominent OAuth 2 providers are linked here.
