Contents
- Link Existing openNCCCS Account to LMS System Account
- Blocked Cookies
- Browser Settings Require Opening the Tool in a New Window or Tab
- Common Error Messages
- Other Technical Documentation
- Additional Resources
Link Existing openNCCCS Account to LMS System Account
If a user has previously created an account on openNCCC and then later launches the openNCCC 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 openNCCC 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.
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 openNCCC 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 openNCCC Help Center by email openNCCChelp@nccommunitycolleges.edu or by opening a Help Center ticket).
Other Error Messages
Error Message and Description | LMS Admin Response | openNCCC 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 openNCCC 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 openNCCC: incorrect usage of launch data | LMS Administrator or LMS Technical Support should submit a Bug Report to the openNCCC 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 openNCCC 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 openNCCC | LMS Administrator or LMS Technical Support should submit a Bug Report to the openNCCC 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 openNCCC during validation of this request | LMS Administrator or LMS Technical Support should submit a Bug Report to the openNCCC 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 openNCCC 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
Additional Resources
Refer to these articles on the openNCCC Help Center.
Adding openNCCC content to Moodle and Open LMS Courses with the LTI 1.3 Tool
How to Install the openNCCC LTI 1.3 Tool in Moodle and Open LMS
Blackboard Classic or Ultra: How to Install the openNCCC LTI 1.3 Tool
Blackboard Classic or Ultra: Adding openNCCC content to Courses with the LTI 1.3 Tool
Canvas: Adding openNCCC Content to Courses with the LTI 1.3 Tool