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

HTTP security: Difference between revisions

From MoodleDocs
Tomaz Lasic (talk | contribs)
No edit summary
m Deprecate loginhttps
 
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Security}}
{{Security}}
<p class="note">'''Please refer to [[Page_notes#Security |these notes]] before editing this page.'''</p>
HTTPS for logins can be enabled by an administrator in ''Settings > Site administration > Security > HTTP security''.


Location: ''Administration > Security > HTTP security''
==HTTPS for logins (deprecated - don't use)==
 
==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==
It is not recommended that you use this setting as it's not secure despite using HTTPS for logins. Instead, please look at [[Transitioning to HTTPS]] completely


{{Moodle 1.9}}Moodle 1.9 onwards includes a setting for secure cookies (when using HTTPS).
You are also unable to use the SSL proxy setting at the same time


''Please add further information here...''
==Secure cookies only==
 
==Only http cookies==
 
Moodle 1.9 onwards includes a setting "Only http cookies".
 
''Please add further information here...''
 
==Regenerate session id during login==
 
In Moodle 1.9.8 onwards, for security reasons, the setting ''regenloginsession'' should be enabled. This setting is compatible with all core authentication plugins, including [[MNet]], but may not be compatible with all contributed authentication plugins.
 
If necessary, the setting can be disabled by adding the following line to your config.php:
 
$CFG->regenloginsession = false;
 
==Required Flash player version==


In Moodle 1.9.7 onwards, for security reasons, a minimum Flash player version may be set. Users with a lower Flash player version will prompted to upgrade.
It is recommended to use secure cookies only when serving over SSL. When not serving over SSL, the setting is ignored. In Moodle 3.1.2 onwards, the 'Secure cookies only' default setting is on. (It is likely that the setting will be removed in 3.2 onwards - see MDL-55662.)


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


*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=79110 Locked out] forum discussion
Forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=79110 Locked out]
*[https://moodle.org/mod/forum/discuss.php?d=339129 Secure Cookies]


[[Category:Administrator]]
[[Category:Site administration]]
[[Category:Security]]


[[de:HTTP-Sicherheit]]
[[de:HTTP-Sicherheit]]
[[es:Seguridad HTTP]]

Latest revision as of 03:18, 6 September 2017

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

HTTPS for logins (deprecated - don't use)

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.

It is not recommended that you use this setting as it's not secure despite using HTTPS for logins. Instead, please look at Transitioning to HTTPS completely

You are also unable to use the SSL proxy setting at the same time

Secure cookies only

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

See also

Forum discussions: