Note: This article is for all LMSs, unless items are marked as specific to an LMS.



Link Existing GoOpen CT Account to LMS System Account  

If a user has previously created an account on GoOpen CT and then later launches the GoOpen CT LTI Tool in the LMS, the user will be asked for a one-time identity verification to confirm linking their accounts The user should enter the password for their existing GoOpen CT account and select the Link This Account button. 


Blocked Cookies  

First-party cookies must be enabled. You will not be able to use the tool or launch embedded links if your browser settings block ALL cookies. Make sure your digital library has been whitelisted (added to your allowed sites) if you are strict about cookie settings. 


Digital Library: LMS

Digital Library URL Domain to Whitelist

GoOpen CT: Moodle, OpenLMS, Blackboard Classic and Ultra, Canvas

https://goopenct.org




Refer to the links below for more information about managing cookies in different browsers. 


Browser Settings Require Opening the Tool in a New Window or Tab 

Depending on the browser you choose and its security settings that control cookies, you may get this screen. You can open the LTI tool in a new browser window or tab to view the content.



Common Error Messages

The LTI 1.3 tool must be installed by the GoOpen CT Administrator and the LMS Administrator. It can’t be installed by teachers or course managers. As an LMS Administrator testing the new LTI tool before you release it to teachers, you may encounter these error messages that prevent teachers from adding content to a course. It’s also possible that a teacher may encounter these errors if the tool is not properly configured. Teachers who encounter issues should contact their LMS admin (who can contact the GoOpen CT Help Center by email support@goopenct.org Help Center ticket). 



Error Message and Description

LMS Admin Response

GoOpen CT Help Center Response

1

No launch URL configured

LMS didn't send a required parameter (Redirect URL) in login request

  • Moodle: ISKME supplies launch URL (Redirection URL). Moodle Admin should verify that the Redirection URL has been correctly added to the Tool Configuration. Moodle Admin should then contact the GoOpen CT Admin to obtain a Redirect URL if one has not been entered, or to verify that the entered Redirection URL is correct.

  • Blackboard: The Redirect URL is auto-populated in Blackboard when the LMS Admin configures the tool. LMS Administrator should contact the GoOpen CT Help Center to confirm the correct Redirect URL and that it was entered correctly in GoOpen CT.

  • Canvas: ISKME supplies launch URL (Redirection URL) and LMS Administrator should confirm that the correct Redirection URL is entered in Canvas. If error persists, contact LMS Technical Support to troubleshoot.

Confirm that Redirect URL is entered correctly in GoOpen CT Site Admin. 

  • Moodle: Confirm that Redirection URL from ISKME was correctly supplied to LMS Admin.

  • Blackboard: LMS Admin supplies Redirect URL. Ensure that the correct Redirect URL was entered in GoOpen CT Site Admin.

2

Could not find Issuer

LMS didn't send a required parameter (Issuer) in login request

LMS Administrator should contact the GoOpen CT Help Center to confirm that Issuer has been entered correctly in GoOpen CT. 

Confirm that Issuer is entered correctly in GoOpen CT Site Admin. 

  • Moodle: comes from LMS

  • Blackboard: comes from ISKME

  • Canvas: comes from ISKME

3

Could not find registration details

Combination of Issuer and Client ID was not found in   during login requestGoOpen CTGoOpen CT

LMS Administrator should contact the GoOpen CT Help Center to confirm that Issuer and Client ID have been entered correctly in GoOpen CT. GoOpen CT

Confirm that Issuer and Client ID are entered correctly in GoOpen CT Site Admin.

  • Moodle: comes from LMS

  • Blackboard: comes from ISKME

  • Canvas: comes from ISKME

4

iss %s [client_id=%s] not found in settings

Combination of Issuer and Client id was not found in GoOpen CT during launch request

5

“iss” is empty

LMS didn't send required parameter (Issuer) in launch request

LMS Administrator should contact the GoOpen CT Help Center to confirm that Issuer has been entered correctly in GoOpen CT. 

Confirm that Issuer is entered correctly in GoOpen CT Site Admin.

  • Moodle: comes from LMS

  • Blackboard: comes from ISKME

  • Canvas: comes from ISKME

6

Launch data not found

After every launch request for adding an LTI link, the launch data will save on the site. If these data are not found on the resource picker page, this error will occur.

7

deployment_id is not set in jwt body

LMS didn't send required parameter (Deployment ID) in launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

Confirm that Deployment ID is entered correctly in GoOpen CT Site Admin

  • Moodle: comes from Site Admin

  • Blackboard: comes from Blackboard

  • Canvas: comes from Canvas

8

Unable to find deployment

LMS sent invalid Deployment id in launch request

LMS Administrator should contact the GoOpen CT Help Center to verify that the Deployment ID has been entered correctly.

9

endpoint is not set in jwt body

LMS didn't send required parameter in launch request

LMS Administrator should contact the GoOpen CT Help Center to verify that Auth Login URL, Auth Token URL, and Key Set URL have been entered correctly in GoOpen CT. If changes need to be made, LMS Admin may need to remove and reinstall the tool before this error will be resolved. If this fails, LMS Administrator should contact LMS Technical Support to troubleshoot.

Confirm that Auth Login URL, Auth Token URL, and Key Set URL have been entered correctly in GoOpen CT Site Admin. If changes need to be made, LMS Admin may need to remove and reinstall the tool before this error will be resolved.

10

Not Found

The requested URL was not found on this server

The LMS could not reach the  Auth login URL and Auth token URL, sometimes because there is a typo in the URL. 

LMS Administrator should check Tool settings in the LMS to ensure that Auth login URL and Auth token URL are correct. 

Confirm that Auth login URL and Auth token URL are correct in GoOpen CT Site Admin.

  • Moodle: Confirm that LMS Administrator sent correct Auth login URL and Auth token URL to GoOpen CT Administrator

  • Blackboard: Confirm that GoOpen CT Administrator has entered correct Auth login URL and Auth token URL 

  • Canvas: Confirm that LMS Administrator received correct Auth login URL and Auth token URL from GoOpen CT Administrator

11

Invalid response from [Key Set URL] Must be JSON: [response text for the URL]

Invalid response from LMS when accessing to Key Set URL

LMS Administrator should contact the GoOpen CT Help Center to verify that the Key Set URL has been entered correctly. If changes need to be made by GoOpen CT, LMS Administrator may need to remove and reinstall the Tool before this error will resolve. If this does not resolve the error, the LMS Administrator should contact LMS Technical Support to troubleshoot.

Confirm that Key set URL has been correctly entered in GoOpen CT Site Admin.

  • Moodle: comes from Moodle

  • Blackboard: comes from Blackboard

  • Canvas: comes from ISKME

12

Invalid URL: [Key Set URL] 

Invalid Key Set URL

13

Unable to find public key

LMS returned invalid keys when accessing to  Key Set URL or invalid keys were set in Key Set field or launch request contains invalid data


Other Error Messages

 


Error Message and Description

LMS Admin Response

GoOpen CT Help Center Response

1

Invalid Nonce

 

Usually, this happens during malicious launch requests when LMS preliminary didn't send login a request

LMS Administrator or LMS Technical Support should submit a Bug Report to the GoOpen CT Help Center. In your Bug Report, please include a screencast that shows your step-by-step process to produce the bug (with developer console open), and information about your LMS (including version), browser (including version), and operating system (including version). 

Escalate the Bug Report to ISKME and follow up with the LMS Administrator

2

Can't validate restored launch

 

Error in GoOpen CT: incorrect usage of launch data

LMS Administrator or LMS Technical Support should submit a Bug Report to the GoOpen CT Help Center. In your Bug Report, please include a screencast that shows your step-by-step process to produce the bug (with developer console open), and information about your LMS (including version), browser (including version), and operating system (including version). 

Escalate the Bug Report to ISKME and follow up with the LMS Administrator

3

State not found

 

Usually, this happens during malicious launch requests when LMS preliminary didn't send login a request

LMS Administrator or LMS Technical Support should submit a Bug Report to the GoOpen CT Help Center. In your Bug Report, please include a screencast that shows your step-by-step process to produce the bug (with developer console open), and information about your LMS (including version), browser (including version), and operating system (including version). 

Escalate the Bug Report to ISKME and follow up with the LMS Administrator

4

Validator conflict

 

Error in code in GoOpen CT

LMS Administrator or LMS Technical Support should submit a Bug Report to the GoOpen CT Help Center. In your Bug Report, please include a screencast that shows your step-by-step process to produce the bug (with developer console open), and information about your LMS (including version), browser (including version), and operating system (including version). 

Escalate the Bug Report to ISKME and follow up with the LMS Administrator

5

Message validation failed

 

LMS sent invalid launch request or an error occurred in GoOpen CT during validation of this request

LMS Administrator or LMS Technical Support should submit a Bug Report to the GoOpen CT Help Center. In your Bug Report, please include a screencast that shows your step-by-step process to produce the bug (with developer console open), and information about your LMS (including version), browser (including version), and operating system (including version).

Escalate the Bug Report to ISKME and follow up with the LMS Administrator

6

Could not find login hint

 

LMS didn't send a required parameter (login hint) in login request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

7

Missing id_token

 

LMS didn't send launch data in launch request

LMS Administrator should contact LMS Technical Support to determine why launch data is missing from LTI 1.3 launch request.

n/a

8

namesroleservice is not set in jwt body

 

LMS didn't send required parameter in launch request

LMS Administrator should check Tool settings in the LMS to ensure that the Tool is allowed to send user role data. If role data is allowed, LMS Administrator should contact LMS Technical Support to determine why role data is not being sent in LTI 1.3 launch requests.

n/a

9

deep_linking_settings is not set in jwt body

 

LMS didn't send required parameter in launch request. This is only for deep linking requests

LMS Administrator should check Tool Settings in the LMS to verify that Deep Linking has been enabled. If Deep Linking is enabled in Tool Settings, the LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

10

Can't convert JWT key to PEM format

 

LMS returned invalid keys when accessing to  Key Set URL or invalid keys were set in Key Set URL field

LMS Administrator should contact LMS Technical Support to troubleshoot. Keys retrieved from LMS during launch were invalid. 

n/a

11

JWT ALG not found

 

LMS didn't send the JWT ALG parameter in the launch request. Cannot decrypt the  message.

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

12

Missing state param

 

LMS didn't send required parameter (State) in launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

13

JWT KID not found

 

LMS didn't send required parameter in launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

14

Invalid id_token, JWT must contain 3 parts

 

LMS sent invalid request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

15

Invalid JWT format, can't be decoded

 

LMS sent invalid launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

16

“nonce” is empty

 

LMS didn't send required parameter (Nonce) in launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

17

Can't decode id_token

 

LMS sent invalid launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

18

Invalid message type

 

LMS sent invalid launch request: message type wasn't set

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

19

Unrecognized message type

 

LMS sent invalid launch request or message type in launch request is not supported

The LTI 1.3 tool supports the LtiResourceLinkRequest and LtiDeepLinkingRequest message types. LMS Administrator should contact LMS Technical Support to ensure launch requests conform to one of these message types.

n/a

20

Missing sessionid cookie

 

This error occurs on launch request and indicates that for some reason cookies were not set or were deleted

Cookies must be allowed in all supported browsers.

n/a

21

Missing Deep Linking Settings

 

LMS didn't send required parameter in launch request. This is specific only to deep linking requests.

LMS Administrator should check Tool Settings in the LMS to verify that Deep Linking is enabled. If Deep Linking is enabled in Tool Settings, the LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

22

Missing Deep Linking Return URL

 

LMS didn't send required parameter in launch request. This is specific only to deep linking requests.

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

23

Must support resource link placement types

 

LMS didn't send required parameter in launch request. This is specific only to deep linking requests.

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

24

Must support a presentation type

 

LMS didn't send required parameter in launch request. This is specific only to deep linking requests.

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

25

Must have a user (sub)

 

LMS didn't send required parameter (User ID) in launch request

LMS Administrator should check Tool Settings in the LMS to ensure the Tool is allowed to send user information in the launch request. If this does not resolve the error, the LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

26

Incorrect version, expected 1.3.0

 

LMS sent invalid parameter (LTI version) in launch request

LMS Administrator should check Tool Settings in the LMS to ensure the LTI Tool is configured as an LTI 1.3 Tool. If the tool is configured as an LTI 1.3 Tool, the LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

27

Missing Roles Claim

 

LMS didn't send a required parameter (Roles) in launch request

LMS Administrator should check Tool Settings in the LMS to ensure the Tool is allowed to send role data in the launch request. If role data is allowed, and the error persists, the LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

28

Missing Resource Link Id

 

LMS didn't send a required parameter in launch request

LMS Administrator should contact LMS Technical Support to troubleshoot.

n/a

29

403 Forbidden

 

Student does not have access to view this content

Teachers should contact the LMS Administrator, who should contact the GoOpen CT Help Center to verify that students should have access to the content and to ask that students be given access to the content. 

n/a


Other Technical Documentation

The LTI Tool Provider conforms to the IMS Global LTI 1.3 Standard:
https://www.imsglobal.org/spec/lti-dl/v2p0

Required Parameters

The following parameters must be present in the LTI launch request sent by the Tool Consumer.

  • role

  • email