You need to be a site administrator, or have the appropriate permissions to be able to configure any settings related to Totara Connect.
Totara Connect is a single sign-on and user identity solution for multiple Totara instances. Connected sites can share user accounts and logins, allowing all users or selected audiences to navigate between them seamlessly.
Totara Connect requires one Totara Learn site to act as the server. Once Totara Connect has been enabled and configured on the server, it is then possible to start connecting more Totara Learn or Totara Social sites as clients. Once connected information is then synchronised from the server to the client.
Totara Connect server is a plugin that facilitates the server side aspects of connecting sites effectively, allowing the site to act as a master to which client sites can connect and synchronise.
|Totara Connect server is disabled by default. To enable it you must log in as a site administrator and turn on Enable Totara Connect server, which can be found under Site administration > Advanced features.|
Once enabled a new administration section will become available at Site administration > Users > Accounts > Totara Connect server.
Even when enabled, by itself the server plugin is inactive. It is not until a second Totara Learn or Totara Social site is connected as a client that the Totara Connect server provides added functionality.
The Totara Connect client is an authentication plugin that facilitates a connection between the current site and one or more Totara Learn sites with an active Totara Connect server.
To be able to add a client to a Totara Connect sever, you first need to enable the Totara Connect client authentication plugin. Go to Site administration > Plugins > Authentication > Manage authentication and enable Totara Connect client by selecting the icon in the Enable column.
Once you have enabled the Totara Connect server, you'll then need to configure the Totara Connect client. Make sure you have enabled the Totara connect client authentication plugin on the client site first.
Finally, add your Totara Connect client to your Totara Connect server.
Go to Site administration > Users > Accounts > Totara Connect server > Settings.
If you want to send user password hashes from your server site to client sites, enable this option.
Go to Site administration > Plugins > Authentication > Totara Connect client > Settings.
This setting allows you to automatically log on to a Totara Connect client site connected to a specific Totara Connect server. Choose a Totara Connect server to automatically sign-on from. Note that you need to connect to a server first to select it from the list.
When enabled, local accounts are migrated to Totara Connect accounts. Totara Connect accounts can log in only via single sign-on.
You should make sure the selected account mapping cannot be abused by Totara Connect server users to hijack existing client accounts. For example when mapping via username, users should not be allowed to sign up for new accounts on the Totara Connect server.
Choose the field you want to use to map user accounts by during migration. You should make sure this field is locked and cannot be modified by ordinary users or customised during user self registration, both on the server and clients.
User fields available are:
If your Totara Connect users are restricted to an audience on the server, this setting determines what happens with local accounts when the user is removed from that audience on the server.
Please note that any synchronised users who are deleted from the server will also be deleted from the local site.
Go to Site administration > Plugins > Authentication > Manage authentication > Totara Connect client > Servers and select Connect to new server.
|Note down the Client url and Client setup secret as you'll need this information to complete the setup.|
Log in as a site administrator to the site which is acting as the Totara Connect server, go to Site administration > Users > Accounts > Totara Connect server > Client systems and select Add client.
Enter a name for the client site.
The URL of the client site. This should be the URL provided when connecting to a new server.
|Client setup secret|
The setup secret for the client site. This should be the client setup secret provided when connecting to a new server.
|Restrict to audience|
You can choose to only synchronise users from a specific audience from the Totara Connect server to the Totara Connect client site. The restriction is applied to all synchronised audiences and courses too i.e. only the audience restricted gets synchronised.
|Add new courses|
If enabled, each new course created in the LMS will be synchronised with the client to create a matching new group (Totara Social) or audience (Totara Learn). The enrolled users of the courses will be added as members to the respective groups or audiences created.
|Add new audiences|
If enabled, each new audience created in the LMS will be synchronised with the client to create a new group (Totara Social) or audience (Totara Learn). The members of the audiences are added as members to the respective groups or new audiences.
Choose one or more audiences and synchronise members to the client site.
Choose one or more courses and synchronise all enrolled users to the client site.
|Comment||Add any applicable comments related to the client site.||-|
Once complete, select Add client. You'll now see that there is an active connection between the server and the client site and a new option will become available on the login page of the client site.
To set up a Totara Connect client for Totara Social please see the Totara Social 2.0 documentation for further information.
If you're new to scheduled tasks, see our dedicated page for more information about how they work.
This task runs internal clean up tasks required by the Totara Connect client.
This task checks the server for audience groups that are scheduled to be synced and recreates those audiences on the client.
This task syncs all information related to the individual users. This includes profile field data but excludes user custom field data, profile images and position assignment data.