Skip to main content
Question

Who has gotten LTI 1.3 to work?

  • 14 June 2024
  • 3 replies
  • 94 views

Hi all,

Has anyone succeeded in importing content to the central repository using the new LTI 1.3 functionality? If yes, where do you add the course link? In one of these fields?


Thank in advance!

3 replies

John
Rank
Userlevel 5
Badge +2

@JenniferRituals  Thanks for the question!

Yes, you can definitely import content to the central repository using the new LTI 1.3 functionality.

Here’s how you can do it:

1. Tool URL (iss): This is the issuer URL from your LTI tool provider.

2. Public keyset URL: The URL where your LTI tool’s public keys are hosted.

3. Initiate login URL: This URL initiates the login process with your LTI tool.

4. Redirection URI(s): The URL where the LTI tool will redirect users after a successful login.
 

The course link usually goes into the Initiate login URL or it’s included within the LTI tool’s setup, depending on how your tool provider structures it. For more detailed guidance, you can also check out the Docebo Help & Support documentation.

If you need more detailed steps or run into any issues, feel free to reach out—we’re here to help!

J
Rank

Hi @John, thank you for your answer! It’s good to know that the course link usually goes in the Initiate login URL. It doesn’t seem to work for us at the moment. We have support tickets open with Docebo and our content vendor so hopefully we’ll have a solution soon.

In the mean time it would be good to hear if LTI 1.3 works successfully for other clients.

John
Rank
Userlevel 5
Badge +2

You’re welcome @JenniferRituals! I’m glad to know that you’re working with our Support team on the request as well given the technical nature of the blocker.

Reviewing the info in the case, I can see that one challenge is how your provider is using a custom launch parameter. Today, Docebo does not yet support that functionality LTI 1.3 can offer. Not to say we won’t implement or consider but just that it is competing against other development priorities. The current version in 1.3 was introduced to meet the minimum need on security while giving customers an option to upgrade from 1.1 and 1.2 versions they may have had in use in the platform.

It is a good scenario to discuss and connect with your CSM, to review any additional options we could provide to make the content integration a successful one.

Reply


Terms & ConditionsCookie settings