Authentication is how your learners/users gain access to the LMS with the use of a username and a password. There are over a dozen ways you can configure authentication within ScholarLMS including self-email-based registration to generate a password and manual generation of username and passwords by an admin.
I already have a website with a membership area and login credentials. Will my learners have to login twice?
Absolutely not! That is the beauty of a modern online learning system. Once you are ready to set-up the authentication process of your LMS, our engineers will work with you to integrate your current user database, including the authentication credentials, to work with ScholarLMS – put simply, if your user is logged in to your membership area with the credentials he already has, they will not have to log into ScholarLMS again and will automatically be logged into the system.
This is just one of the ways ScholarLMS adapts to your eLearning needs. To know more about which would be the best authentication method for your LMS, get in touch with us here.
ScholarLMS provides a number of ways of managing authentication by means of authentication plugins.
- Manual accounts - accounts created manually by an administrator
- No login - suspend particular user account
- Email-based self-registration - for enabling users to create their own accounts
- CAS server (SSO) - account details are located on an external CAS server
- External database - account details are located on an external database
- FirstClass server - account details are located on an external FirstClass server
- IMAP server - account details are located on an external IMAP server
- LDAP server - account details are located on an external LDAP server
- LTI - works with the Publish as LTI tool enrolment method to connect courses and activities. (New in 3.1)
- Moodle Network authentication - how different Moodle sites can connect and authenticate users
- NNTP server - account details are located on an external NNTP server
- No authentication - for testing purposes or if the Moodle site is not available on the Internet. Do NOT use on public servers!
- 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 server - account details are located on an external RADIUS server
- Shibboleth - account details are located on an external Shibboleth server
- Web services authentication
- Unique login authentication to limit users to one simultaneous session