Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Authentication.

Authentication: Difference between revisions

From MoodleDocs
Main page ► Managing a Moodle site ► Authentication
Managing a Moodle site
(content moved to Managing authentication)
 
(59 intermediate revisions by 20 users not shown)
Line 1: Line 1:
There are various ways of managing user '''authentication''':
{{Managing a Moodle site}}
Authentication is the process of allowing a user to login to a Moodle site based on their username and password.


:[[Email-based authentication]]
==Authentication plugins==
:[[Manual accounts only]]
:[[No authentication]]
:[[PAM (Pluggable Authentication Modules)]]
:[[Shibboleth]]
:[[Use a CAS server (SSO)]]
:[[Use a POP3 server]]
:[[LDAP authentication|Use an LDAP server]]
:[[NTLM authentication|Use NTLM/Integrated Authentication (3rd party plugin)]]


==Закрытие областей профиля==
Moodle provides a number of ways of [[Managing authentication|managing authentication]], called ''authentication plugins''.  
To prevent users from altering some fields (e.g. students changing profile information to inappropriate or misleading information, the site administrator can lock profile fields.


[[Image:Authent-data-map-fname.jpg|Data Mapping Options]]
*[[Manual accounts]] - accounts created manually by an administrator
*These fields are optional. You can choose to pre-fill some Moodle user fields with information from the LDAP fields that you specify here.  If you leave these fields blank, then nothing will be transferred from LDAP and Moodle defaults will be used instead.  In either case, the user will be able to edit all of these fields after they log in.
*[[No login]] - suspend particular user account
*'''Update local''': If enabled, the field will be updated (from external auth) every time the user logs in or there is a user synchronization. Fields set to update locally should be locked.
*[[Email-based self-registration]] - for enabling users to create their own accounts
*'''Lock value''': If enabled, will prevent Moodle users and admins from editing the field directly. Use this option if you are maintaining this data in the external auth system.
*[[CAS server (SSO)]] - account details are located on an external CAS server
*'''Update external''': If enabled, the external auth will be updated when the user record is updated. Fields should be unlocked to allow edits.  Note: Updating external LDAP data requires that you set '''binddn''' and '''bindpw''' to a bind-user with editing privileges to all the user records. It currently does not preserve multi-valued attributes, and will remove extra values on update.
*[[External database authentication|External database]] - account details are located on an external database
 
*[[FirstClass authentication|FirstClass server]] - account details are located on an external FirstClass server
If you are using a mixture of authentication types (such as IMAP and manual), then the fields you lock in the authentication options will only apply to the type of authentication indicated by the drop down box at the top of the screen.  Remember to test the field locking by logging in with the proper type of account!  If you test with a manual account but have set the field locking to apply to IMAP accounts, you will not be able to tell if it worked!
*[[IMAP authentication|IMAP server]] - account details are located on an external IMAP server
 
*[[LDAP authentication|LDAP server]] - account details are located on an external LDAP server
==Customising the login page==
*[[MNet|Moodle Network authentication]] - how different Moodle sites can connect and authenticate users
 
*[[NNTP authentication|NNTP server]] - account details are located on an external NNTP server
Depending upon the authentication method (i.e. not applicable for email authentication) login instructions may be easily added. Alternatively, an alternate login URL may be added - please check the Using Moodle discussion [http://moodle.org/mod/forum/discuss.php?d=26629 Customising the log in page] for further details.
*[[No authentication]] - for testing purposes only
*[[PAM (Pluggable Authentication Modules)]] - account details come from the operating system Moodle is running on, via PAM (can only be used Linux/Unix).
*[[POP3 server]] - account details are located on an external POP3 server
*[[RADIUS authentication|RADIUS server]] - account details are located on an external RADIUS server
*[[Shibboleth]] - account details are located on an external Shibboleth server
* Web services authentication


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


*[http://moodle.org/mod/forum/view.php?id=42 Using Moodle: User authentication] forum
*[[Authentication FAQ]]


[[Category:Administrator|Admin/auth]]
[[Category:Authentication]]
[[Category:Authentication|Admin/auth]]


[[eu:Erabiltzaileen_autentifikazioa]]
[[fr:Authentification]]
[[fr:Authentification]]
[[de:Authentifizierung]]
[[ja:認証]]

Latest revision as of 10:11, 18 October 2011

Authentication is the process of allowing a user to login to a Moodle site based on their username and password.

Authentication plugins

Moodle provides a number of ways of managing authentication, called authentication plugins.

See also

Retrieved from "https://docs.moodle.org/20/en/index.php?title=Authentication&oldid=92181"
Powered by MediaWiki