Updated in the last 15 minutes

When someone registers for an e-learning course via Springest, it is now possible for them to immediately start e-learning! After completing the online payment, they can start the e-learning course right away. This is called Single Sign-On via Learning Tool Interoperability (LTI). The student's data is transferred to your system directly via the LTI protocol. 

How does it work?

Once Single Sign-On is activated, the training page shows a green button, 'Register now'. Clicking this button directs the student to the registration page and then to the payment page. After everything is confirmed, the student can click on a blue button, 'Start course', which directs them to the e-learning course on the trainer's online environment. This enhances usability for students and lightens the workload of trainers.  

On Springest Go websitesOnce Single Sign-On is activated, the blue 'Start course' button will become visible. This button will be displayed even before registration and payment are completed. 

How can I activate this?

Does your system support LTI? Then you can apply Single Sign-On via LTI for all of your e-learning courses. At this time, only Springest can activate this, so if you would like to use LTI or have any questions, do not hesitate to contact our Support team. Reach us at info@springest.fr, we would be happy to help or activate this instantly. 

What does this look like?, you see an example of what this looks like on a training page on Springest (the Dutch version) before registration and payment. Right, you see what this looks like on Springest after registration and payment.

On Springest Go websitesRight, you see an example of what this looks like on a training page on a Springest Go website.

Public platform

Go platform

Technical implementation and guidelines

We have set up our SSO via LTI according to the documentation of IMS Global, the organisation behind LTI:

The entire LTI implementation guide.

SSO-specific documentation: Learning Tools Interoperability® as a SSO Mechanism. Springest is the "tool consumer" in this article; as a provider you are the "tool provider".
Remarks:

Springest is on LTI v1.1. Newer versions are backwards-compatible, so if you are using a newer version it does not negatively impact the SSO.
Springest only supports a one-way connection: we send data to the provider's system. We cannot (yet) receive back information (such as progress).
Our system is flexible. We support SSO via LTI in multiple ways: 

1. Your system works with one Launch URL for all of your products

In this case you have to provide us with:

The Launch URL
Consumer Key and Consumer Secret Key, with two options:You deliver one Key and Secret Key that applies to all of your productsYou deliver a Key and Secret Key per product
Per product: one custom parameter that serves as an unique id for the product
2. Your system works with a separate Launch URL per product

In this case you have to provide us with:

The Launch URL per product
Consumer Key and Consumer Secret Key, with two options: You deliver one Key and Secret Key that applies to all of your productsYou deliver a Key and Secret Key per product
Note: are your products published on multiple Springest sites? Then it is possible –and advised– to have separate Consumer and Secret Keys per site. 

Did this answer your question?