Note: You are currently viewing documentation for Moodle 3.6. Up-to-date documentation for the latest stable version of Moodle is likely available here: HTTP security.

HTTP security: Difference between revisions

From MoodleDocs
(see also forum discussion link)
(Secure cookies only - MDL-55273)
Line 4: Line 4:
==Use HTTPS for logins==
==Use HTTPS for logins==
HTTPS encrypts the user's login data, so it's difficult to sniff out a user's username and password on the network. You will need to enable HTTPS on your server before you turn on this setting, or else you will be locked out of your site. Every web server has a different method for enabling HTTPS, so you should check the documentation for your web server.
HTTPS encrypts the user's login data, so it's difficult to sniff out a user's username and password on the network. You will need to enable HTTPS on your server before you turn on this setting, or else you will be locked out of your site. Every web server has a different method for enabling HTTPS, so you should check the documentation for your web server.
==Secure cookies only==
In Moodle 3.1.2 onwards, the 'Secure cookies only' default setting is on i.e. it is recommended to use secure cookies only when serving over SSL. When not serving over SSL, the setting is ignored. (It is likely that the setting will be removed in 3.2 onwards - see MDL-55662.)


==See also==
==See also==

Revision as of 14:47, 7 September 2016

HTTPS for logins can be enabled by an administrator in Settings > Site administration > Security > HTTP security.

Use HTTPS for logins

HTTPS encrypts the user's login data, so it's difficult to sniff out a user's username and password on the network. You will need to enable HTTPS on your server before you turn on this setting, or else you will be locked out of your site. Every web server has a different method for enabling HTTPS, so you should check the documentation for your web server.

Secure cookies only

In Moodle 3.1.2 onwards, the 'Secure cookies only' default setting is on i.e. it is recommended to use secure cookies only when serving over SSL. When not serving over SSL, the setting is ignored. (It is likely that the setting will be removed in 3.2 onwards - see MDL-55662.)

See also

Forum discussions: