- 06 Aug 2024
- 1 minute to read
Available authentication methods
- Updated on 06 Aug 2024
- 1 minute to read
Authentication methods control the different ways in which users are able to access your site.
There are many different authentication methods that can be used on your site, and you may have multiple plugins in use at once. The combination of authentication methods you use will depend on your use case.
Plugin | Description |
---|---|
Manual accounts | Accounts created manually by a Site Administrator. |
No login | This is another way of suspending a user account. If you set the No login method as the authentication method on a user's profile then they will no longer be able to log in to your Totara site. However, unlike when a user is suspended, this will not trigger a purge type and all of their data will still exist in the system. The user will also still receive messages from your Totara site. |
Email-based self-registration | Enables users to create their own accounts. |
LDAP server | Account details are located on an external LDAP server. |
LTI (Experimental) | Use this with the Publish as LTI tool enrolment plugin to allow remote users to access selected courses and activities. |
Self-registration with approval | Enables users to create their own accounts, but prevents them joining the site until they are approved. |
CAS server (SSO) | Account details are located on an external CAS server. |
Totara Connect client | Automatic single sign-on via Totara Connect servers. |
External database | Account details are located on an external database. |
MNet authentication | Separate Totara sites can connect and authenticate users. The MNet authentication plugin is deprecated as of Totara 13. |
OAuth 2 | Allows users to log in via a Microsoft, Google, or Facebook account. |
Shibboleth | Account details are located on an external Shibboleth server. |
Web services authentication | Accounts used exclusively by web service clients. |