Authentication: Difference between revisions
(common settings - order of enabled plugins) |
Helen Foster (talk | contribs) (multi-authentication) |
||
| Line 1: | Line 1: | ||
==Managing user authentication== | |||
There are several ways to manage user authentication. These are called Authentication plugins and include: | |||
*[[Manual accounts]] | *[[Manual accounts]] | ||
| Line 11: | Line 11: | ||
*[[IMAP authentication|IMAP server]] | *[[IMAP authentication|IMAP server]] | ||
*[[LDAP authentication|LDAP server]] | *[[LDAP authentication|LDAP server]] | ||
*[[Moodle Network authentication]] | *[[Moodle Network|Moodle Network authentication]] | ||
*[[NNTP authentication|NNTP server]] | *[[NNTP authentication|NNTP server]] | ||
*[[No authentication]] | *[[No authentication]] | ||
| Line 19: | Line 19: | ||
*[[Shibboleth]] | *[[Shibboleth]] | ||
*[[NTLM authentication|NTLM/Integrated Authentication (3rd party plugin)]] | *[[NTLM authentication|NTLM/Integrated Authentication (3rd party plugin)]] | ||
==Multi-authentication== | |||
{{Moodle 1.8}}From Moodle 1.8 onwards, multi-authentication is supported. Simply click on the closed eye icon to enable a particular plugin. | |||
Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers. | |||
==Common settings== | ==Common settings== | ||
The settings chosen here will apply for any chosen authentication method. Most of them are self explaining. | The settings chosen here will apply for any chosen authentication method. Most of them are self explaining. | ||
*With the ''' | *With the '''Self registration''' option, it is possible to choose a method whereby users can make there own account (if you want that possibility). | ||
*The '''Alternate login url''' should be used with care, since a mistake in the url or on the used login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config), using e.g. phpmyadmin for mysql. | *The '''Alternate login url''' should be used with care, since a mistake in the url or on the used login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config), using e.g. phpmyadmin for mysql. | ||
Revision as of 20:52, 16 July 2007
Managing user authentication
There are several ways to manage user authentication. These are called Authentication plugins and include:
- Manual accounts
- No login
- Email-based self-registration
- CAS server (SSO)
- External database
- FirstClass server
- IMAP server
- LDAP server
- Moodle Network authentication
- NNTP server
- No authentication
- PAM (Pluggable Authentication Modules)
- POP3 server
- RADIUS server
- Shibboleth
- NTLM/Integrated Authentication (3rd party plugin)
Multi-authentication
Moodle1.8
From Moodle 1.8 onwards, multi-authentication is supported. Simply click on the closed eye icon to enable a particular plugin.
Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.
Common settings
The settings chosen here will apply for any chosen authentication method. Most of them are self explaining.
- With the Self registration option, it is possible to choose a method whereby users can make there own account (if you want that possibility).
- The Alternate login url should be used with care, since a mistake in the url or on the used login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config), using e.g. phpmyadmin for mysql.
Locking profile fields
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.
- 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.
- 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.
- 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.
- 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.
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!
See also
- Multi authentication in Upgrading to Moodle 1.8
- Using Moodle: User authentication forum
