As an admin, you can use this guide to identify and resolve common LTI 1.3 integration issues.
Performing Standard Checks in Lumina
As an admin, you can perform standard checks to ensure the configuration parameters match between Lumina and your Learning Management System (LMS), since LTI 1.3 requires a two-way setup.
- Contact your Account Manager to ensure that your institution has LTI 1.3 enabled.
- Log in to Lumina as an admin.
- Click the Main Menu button > Admin Panel.
- In the sidebar, select Integrations.
- Ensure that all the parameters match with the information generated by your LMS.
Resolving Common Errors
As an admin, you can use this to find common LTI 1.3 integration errors and the steps to resolve them.
- Your LMS YuJa Integration for LTI 1.3 did not provide a valid ISS: Ensure the ISS and Client ID are correct. To check this, go to Admin Panel > Integrations > LMS via LTI 1.3.
- Your LMS YuJa Integration for LTI 1.3 did not Initiate Login with all the Information. Error is - A signing key must be specified if the specified JWT is digitally signed: Ensure the Deployment ID and JWKS Endpoint are correct. To check this, go to Admin Panel > Integrations > LMS via LTI 1.3.
- Authentication scheme not configured for your Organization for LTI 1.3: Contact your YuJa Account Manager to enable LTI 1.3 integration for your organization.
- Your LMS YuJa Integration for LTI 1.3 did not initiate Login with all the information: This happens when some mandatory tags for LTI 1.3 are missing during Launch request. Please check for compatibility between the current version of your LMS and LTI 1.3.
- LTI Version claim missing in the Launch request: This happens when the Version Claim is missing. Contact your LMS support team to resolve this issue.
- Incorrect LTI Version passed to LTI 1.3 Launch request: This happens when the Version Claim is incorrect. Contact your LMS support team to resolve this issue.
- Invalid JWT. Critical claims of LTI 1.3 missing in request: This happens when Sub claim is missing. Contact your LMS support team to resolve this issue.
-
One or more of the Required Claims are missing in the LTI 1.3 Launch request:
- Message type
- LTI
- Deployment ID
- Target link URI
- Resource link ID
- LTI user ID
- LTI roles
- Invalid IAT and/or EXP values passed in the LTI 1.3 request /Invalid IAT and/or exp fields in the LTI 1.3 Launch request: This happens when the request carries an expired timestamp.
- KID not set in the header: This happens when the signing key is missing during the Launch request. Contact your LMS support team to resolve this issue.
- Incorrect KID provided: KID is used to retrieve the matching key to decrypt messages sent by LMS to Lumina. Incorrect KID could be due to incorrect Deployment ID within the LMS. Some LMS has decoupled Deployment ID and KID. If this is the case, it will require further investigation from both LMS and YuJa.
- Incorrect Signature - Unable to Validate JWT: This happens when the JWT key URL is incorrectly configured. Make sure all other parameters including ISS, Deployment ID and Client ID are correct.
- RSA Public key not found for the given ISS: This happens when the JWT key URL is incorrectly configured. Make sure all other parameters including ISS, Deployment ID and Client ID are correct.
- Incorrect Signature unable to validate state JWT: This happens when the JWT key URL is incorrectly configured. Make sure all other parameters including ISS, Deployment ID and Client ID are correct.
-
YuJa URL refused to connect: This happens when the integration cannot identify a user account to connect. There are two common reasons for this.
- If this is a new user, navigate to Admin Panel > Integrations > LMS via LTI 1.3 page to check if automatic provisioning of a new user account is enabled.
- If this is to link an existing user by using the user's email, check if there are multiple users that share the same email address. Contact your YuJa Account Manager to resolve this issue.