Difference between revisions of "HTTP security"

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 2.5. Up-to-date documentation for the latest stable version of Moodle may be available here: HTTP security.

(Regenerate session id during login)
Line 1: Line 1:
 +
{{Security}}
 +
<p class="note">'''Please refer to [[Page_notes#Security |these notes]] before editing this page.'''</p>
 +
 
Location: ''Administration > Security > HTTP security''
 
Location: ''Administration > Security > HTTP security''
 
  
 
==Use HTTPS for logins==
 
==Use HTTPS for logins==

Revision as of 02:22, 10 June 2011

Please refer to these notes before editing this page.

Location: 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

Template:Moodle 1.9Moodle 1.9 onwards includes a setting for secure cookies (when using HTTPS).

Please add further information here...

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.

See also