Authentication FAQ

 

General Questions

What is an authentication plugin?

An authentication plugin is a method of handling user authentication to LMS when users log into your site. This means, in the most usual practice, matching a user’s username with their password.

You can have one or more methods at the same time enabled on your site, but each user can only use one method of authentication at a time. So, you may have manual authentication for some users, LDAP for others, Shibboleth for others, but each user authenticates with only one of those.

See Authentication for the list of these various methods and their use and settings.

Can I have more than one authentication method?

Yes, you can enable and configure as many methods as you need for your users in Site administration > Plugins > Authentication > Manage authentication. Note that the order of processing on this page does matter and after manual and nologin, you should next put the method that most users will have. See Managing Authentication for details.

Can a user have more than one authentication method?

No, a user account has only one authentication method at a time. You can change this method for a user, but you will also need to handle issues such as passwords, etc. that arise from this.

Manual and Self-registration Questions

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 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.

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

See the section ‘Is this your first time here?’ instructions in Managing authentication.

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

The difference is that self-registration is the general term for having a user create an account themselves. There could be many ways to do that, for instance, to allow users to sign up with no email at all. Almost all web applications these days, however, require users to first confirm their email address. This is to prevent spam accounts and other security issues. LMS has only one type on self-registration currently, which is email-based.

Therefore: to allow users to create self-registered accounts, you must do two things:

1. Enable email-based self-registration authentication plugin to allow such users to be able to log in.
2. Set Site administration > Plugins > Authentication > Managing authentication > Common settings > Self registration from Disable to Email-based self-registration to allow potential users to create their accounts.

This division of labor into two settings means that it is possible to Disable Self-registration to prevent accounts, but as long as the Authentication method Email-self registration is still enabled, users will still be able to log in and use their accounts.

You could do this in a case where you may wish to allow signup for a limited period (a day, week, month) to allow users to self-create their accounts, then Disable creating new accounts while allowing the already created users to log in.

How can I prevent spam accounts if I use self-registration?

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 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.

Why isn’t the Email-Based Self-Registration sending emails?

Email based sends out an email with a message and confirmation link to users when they sign up. The possible reason why this make not be working, and also a useful order to troubleshoot this, is:

1. Is email working at all from LMS for other features such as forum posts? If not, check that you have Messaging enabled and that your Email Settings are set.
2. Is email for new sign-ups working? You can test this yourself by signing up with a dummy test user and a valid email.
3. Has the user checked their spam or junk folder? The email comes by default from your LMS administrator account, and it is not uncommon for that to be flagged by some systems as potential spam.
4. Did the user make a typo or other error in their email address or are they using the wrong account?

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

If you are creating ONE manual account, then no.

Other authentication methods

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. This means the user will not be able to log into LMS, but their account is otherwise unchanged.

Note: Users will not receive any error or another message when they try to log in but it simply will not allow them in. So it will appear as though their password was incorrect and they may attempt to reset it. Consider this issue when using No login, in order to reduce support issues.

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.

Can I change manual accounts to LDAP?

Yes. You can change any user account from one authentication method to another in LMS, but you are of course responsible for making sure that the information matches and is valid in the new method.

You can set this manually for each user in their user profile by changing the “Authentication” field. This can also be changed en masse for many users by using the User file upload tool Upload_users and changing the field called “auth”.

How can I allow users to bypass NTML SSO?

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

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

/login/index.php?authldap_skipntlmsso=1

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

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

Other Questions

How can young students or other users without email addresses create new LMS accounts?

You can either use a fake email address when you upload the CSV file of your young users – or – you can use the Upload_users file upload tool to get around this, as follows

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

See also No Email.

Where are the users’ details stored?

Basic user account information, the required fields of username, first name, last name, and email address, which allow a user to be known to LMS and are stored in the LMS database. How much other user profile information is stored depends on the authentication method used for that user, and whether that information is stored externally to LMS in another system. All user activity is done in LMS, e.g., course enrollments, grades, and so forth are stored in LMS.

“Internal” users are those who are created directly in LMS and whose information is not directly linked to or synchronized with any other system. Manual and self-registration authentication methods are internal.

“External” users are those whose user account information is based in another system and is synchronized or referenced by LMS when needed. LPAD, External database, CAS, Shibboleth, etc. are examples of external methods.

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

This is set in Site administration > Plugins > Authentication > Manage authentication > Common settings > Allow login via email.

See also

• Accounts FAQ