Aquesta pàgina forma part de la documentació de Moodle en català, tot i que no ha estat traduïda encara. Podeu contribuir obertament a les tasques de traducció. Podeu consultar la Guia d'edició de la documentació i també participar ens els debats del fòrum de traductors de la documentació a moodle.org

Authentication FAQ

De MoodleDocs
Salta a:navegació, cerca

What is an authentication plugin?

An authentication plugin is a method of handling user authentication i.e. enabling certain people to login to your Moodle site.

How do I enable the "Create new account" button on the login page?

To display the "Is this your first time here?" instructions and the "Create new account" button:

  1. Make sure that the email-based self-registration plugin (or any other plugin that can support self-registration, such as LDAP) is enabled in Settings>Site administration > Plugins > Authentication > Manage authentication.
  2. Select the self-registration plugin in the Common settings.

Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. See Reducing spam in Moodle for ways of minimizing the risk.

How can I change the "Is this your first time here?" instructions?

  1. Access Settings > Site administration > Plugins > Authentication > Manage authentication.
  2. Write the instructions in the auth_instructions text field.
  3. Click the "Save changes" button at the bottom of the page.

An alternative method of providing custom login instructions is to edit the default login instructions using the language customization feature. This method should be used if you wish to provide custom login instructions in more than one language. See Managing authentication for further details.

How do I set up LDAP authentication?

See LDAP authentication for full instructions.

How is the "No login" authentication plugin used?

The No login authentication plugin can be used to suspend particular user accounts. To do so:

  1. Access the user's profile page.
  2. In the Settings block, click "Edit profile".
  3. Select "No login" as the authentication method. (If the setting isn't shown, click the "Show advanced" button to reveal it.)
  4. Click the "Update profile" button at the bottom of the page.

What is the difference between enabling the email-based self-registration auth plugin and selecting it as the self registration method?

The email-based self-registration authentication plugin must be enabled to allow users who previously self-registered to login.

Selecting email-based self-registration as the self registration method allows potential users to self register.

Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. This risk can be minimized by limiting self registration to particular email domains with the allowed email domains setting in Settings > Site administration > Plugins> Authentication > Manage authentication. Alternatively, self registration may be enabled for a short period of time to allow users to create accounts, and then later disabled.

There is some discussion about having admin approval or new accounts created this way here: http://tracker.moodle.org/browse/CONTRIB-1444

How can I create an authentication plugin?

See Development:Authentication plugins.

How can students without email addresses create new Moodle accounts?

See No Email.

My students are too young to have emails, but it's a required field - what do I do?

You can either use a fake email address when you upload the CSV file of your young students - or -

  1. Upload a CSV file without an email field. When previewing the accounts, set "Prevent email address duplicates" to No.
  2. In "Default values", type in an email address.
  3. When the users are uploaded, they will all have the same email address. (It will say "duplicated" but the accounts will work)

Where are users' details stored?

Users' details can be stored in local Moodle database or externally.

If Users' details are stored in the local Moodle database, it is called "internal authentication". Storing users' details externally is called "external authentication".

Can you arrange for an e-mail to be sent to notify Users of new accounts?

If you are creating ONE manual account, then no.

See Feature request here: http://tracker.moodle.org/browse/MDL-19390

See discussion http://moodle.org/mod/forum/discuss.php?d=117005

Bulk upload can be set up to send e-mails: see the discussion here: http://moodle.org/mod/forum/discuss.php?d=85333 (Which includes a code hack to do this as well. (Also http://moodle.org/mod/forum/discuss.php?d=125000)

Can you arrange for Admins to be notified of new self registrations

See this discussion: http://moodle.org/mod/forum/discuss.php?d=212648

How can I have users logging in with their email address?

See this Forum thread: Logging in Using Email or Username

How can I allow users to bypass NTML SSO?

When NTLM SSO is enabled on a Moodle site the SSO function always logs the user who is logged into the computer into Moodle. Sometimes you may need to override this feature and login to Moodle as another user. Example: when a teacher or site administrator needs to login to the students computer to troubleshoot a problem. Or the teacher simply needs to access functionality that is not available to the student and the teacher is not anywhere near her own computer.

The problem is that the Moodle logout option is not available when SSO is enabled - the user simply gets logged back into Moodle. To bypass the SSO you can add this to the url:

/login/index.php?authldap_skipntlmsso=1

Example: http://yourschool.com/login/index.php?authldap_skipntlmsso=1

The NTLM SSO will be disabled (for this login only) and you will get the regular Moodle login page.

warning.png Warning: This bypass won't work if you have the Force users to login site policy enabled. In that case, SSO is applied to all pages on the site, including the log in and log out pages.

See the Using Moodle Bypass NTML SSO for Moode 2.2 forum discussion for details.

See also