LTI 1.3 tool launch not receiving custom parameter not only custom parameter entire additional setting data not coming with launch request

[PraveenShukla]

When launching the LTI 1.3 we are not able to get whatever we have set in custom parameters. please help us how we get these values .

[chriscas]

Hi @PraveenShukla,

Are you looking at the "https://purl.imsglobal.org/spec/lti/claim/custom" area for the custom values?  Here's a screenshot from the LTI debugger extension showing custom values coming over for one of the LTI 1.3 tools we use at my institution.

-Chris

[PraveenShukla]

Hi @chriscas , Yes, I am looking the same.

are you using the additional setting of the developer key creation form or sending it through your LTI code? we are not getting anything from additional settings not even custom fields.

please help us with how we can get dynamic data with additional settings. We have added forcefully custom data in the LTI code but that only shows static values not recognizing canvas variables.

see the bellow token which shows you custom data but that's static data sent through out LTI code if we remove that code from LTI nothing comes in a custom field.

this is our id_token - 

eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6ImZjZWM0ZjE0LTI4YTUtNDY5Ny04N2MzLWU5YWMzNjFkYWRhNSJ9.eyJpc3MiOiJodHRwczpcL1wvY2FudmFzLmluc3RydWN0dXJlLmNvbSIsImF1ZCI6WyIyMjAwMzAwMDAwMDAwMDAxMDgiXSwic3ViIjoiMGFlODM2YjktN2ZjOS00MDYwLTAwNmYtMjdiMjA2NmFjNTQ1IiwiZXhwIjoxNzAxNjg5MzYxLCJpYXQiOjE3MDE2ODg3NjEsIm5vbmNlIjoibm9uY2U2NTZkYjViOTQyYmE3IiwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvZGVwbG95bWVudF9pZCI6IjIxNTpmYTZlMDNjNjJiMmM2YjdhOTRmZDQ3OTU3ZjhhZGM5ZWFiNzAxNTZmIiwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvbWVzc2FnZV90eXBlIjoiTHRpUmVzb3VyY2VMaW5rUmVxdWVzdCIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aVwvY2xhaW1cL3ZlcnNpb24iOiIxLjMuMCIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aVwvY2xhaW1cL3RhcmdldF9saW5rX3VyaSI6InN0YWdpbmdtbGpsdGl0b29sLm15bGVhcm5lcmpvdXJuZXkuY29tXC9zcmNcL3dlYlwvZ2FtZS5waHAiLCJodHRwczpcL1wvcHVybC5pbXNnbG9iYWwub3JnXC9zcGVjXC9sdGlcL2NsYWltXC9yb2xlcyI6WyJodHRwOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3ZvY2FiXC9saXNcL3YyXC9tZW1iZXJzaGlwI0luc3RydWN0b3IiXSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvcmVzb3VyY2VfbGluayI6eyJpZCI6IjE2NDc5Zjk5ZTgxMWJlZTI3YmQyM2FmZTg1YTAwODM4NDkyOTdiOTUifSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpLW5ycHNcL2NsYWltXC9uYW1lc3JvbGVzZXJ2aWNlIjp7ImNvbnRleHRfbWVtYmVyc2hpcHNfdXJsIjoiaHR0cHM6XC9cL215bGVhcm5lcmpvdXJuZXkuaW5zdHJ1Y3R1cmUuY29tXC9hcGlcL2x0aVwvY291cnNlc1wvMTE2XC9tZW1iZXJzaGlwX3NlcnZpY2UifSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvY3VzdG9tIjp7ImNvdXJzZWlkIjoiLmNvdXJzZS5pZCIsInVzZXJpZCI6IjUifSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpLWFnc1wvY2xhaW1cL2VuZHBvaW50Ijp7InNjb3BlIjpbImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aS1hZ3NcL3Njb3BlXC9saW5laXRlbSIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aS1hZ3NcL3Njb3BlXC9yZXN1bHQucmVhZG9ubHkiLCJodHRwczpcL1wvcHVybC5pbXNnbG9iYWwub3JnXC9zcGVjXC9sdGktYWdzXC9zY29wZVwvc2NvcmUiXSwibGluZWl0ZW1zIjoiaHR0cHM6XC9cL215bGVhcm5lcmpvdXJuZXkuaW5zdHJ1Y3R1cmUuY29tXC9hcGlcL2x0aVwvY291cnNlc1wvMTE2XC9saW5lX2l0ZW1zIn19.r7bYwzR3G8Kp4a_lV5zAf82Mc2zQWuTbydPSAEpo_YvUlpvvFd1kw7Vzjpk_SoXQspznAr-mBOfiYl9TQLK17-5RPDbI5b1PBe2dPtFw3asnvPDSsUuWgkSmFkrNcw8bixK6ucusSXNOtorv28gaFu-owTMP1BE35g8tzTw56F_TL5amNed8R3Uix3DU3LV9lD6Es9cyx5vY-Pk6d0Gmnifi7CiSQ6gOAFxIrvGow1sdT7nBRp8XfvL0M849o5AGA9NVQyBr474-LLhvW8P5ESP9CwU8bqgojBSL-eqeivRsSuYW-Mr8e8qn5k6MWeVXoq9Jf60yRW-HMQ_dyIUbig

I have also attached the image where are setting some custom variables. 

Thanks in Advance.

@chriscas

[matthew_buckett]

If you decode the JWT at https://jwt.ms then it outputs:

  "https://purl.imsglobal.org/spec/lti/claim/custom": {
    "courseid": ".course.id",
    "userid": "5"
  },

so you are getting some custom claims in the token, but I suspect that the developer key that you're editing isn't the one you took the screenshot of as there are lots of custom claims missing. The client ID embedded in the token is 220030000000000108, is that the one you're editing in the "Developer Keys" part of Canvas?

[chriscas]

@PraveenShukla ,

I noticed the same thing as @matthew_buckett .  The custom parameters in the JWT don't match the screenshot of the developer key at all, so I think there's a mismatch somewhere.  Seeing the exact developer key setup that matches the JWT output would be very helpful.  I think something as simple as an extra space in the setup can create unpredictable output like you're seeing.

-Chris

[PraveenShukla]

Hi @chriscas  and @matthew_buckett 

see this link https://prnt.sc/6rPDEXobkVjw using the same developer key.

this new token - 

eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6ImZjZWM0ZjE0LTI4YTUtNDY5Ny04N2MzLWU5YWMzNjFkYWRhNSJ9.eyJpc3MiOiJodHRwczpcL1wvY2FudmFzLmluc3RydWN0dXJlLmNvbSIsImF1ZCI6WyIyMjAwMzAwMDAwMDAwMDAxMDgiXSwic3ViIjoiMGFlODM2YjktN2ZjOS00MDYwLTAwNmYtMjdiMjA2NmFjNTQ1IiwiZXhwIjoxNzAxNzA2OTE1LCJpYXQiOjE3MDE3MDYzMTUsIm5vbmNlIjoibm9uY2U2NTZkZmE0YjBhYmUzIiwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvZGVwbG95bWVudF9pZCI6IjIxNTpmYTZlMDNjNjJiMmM2YjdhOTRmZDQ3OTU3ZjhhZGM5ZWFiNzAxNTZmIiwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvbWVzc2FnZV90eXBlIjoiTHRpUmVzb3VyY2VMaW5rUmVxdWVzdCIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aVwvY2xhaW1cL3ZlcnNpb24iOiIxLjMuMCIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aVwvY2xhaW1cL3RhcmdldF9saW5rX3VyaSI6InN0YWdpbmdtbGpsdGl0b29sLm15bGVhcm5lcmpvdXJuZXkuY29tXC9zcmNcL3dlYlwvZ2FtZS5waHAiLCJodHRwczpcL1wvcHVybC5pbXNnbG9iYWwub3JnXC9zcGVjXC9sdGlcL2NsYWltXC9yb2xlcyI6WyJodHRwOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3ZvY2FiXC9saXNcL3YyXC9tZW1iZXJzaGlwI0luc3RydWN0b3IiXSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpXC9jbGFpbVwvcmVzb3VyY2VfbGluayI6eyJpZCI6IjE2NDc5Zjk5ZTgxMWJlZTI3YmQyM2FmZTg1YTAwODM4NDkyOTdiOTUifSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpLW5ycHNcL2NsYWltXC9uYW1lc3JvbGVzZXJ2aWNlIjp7ImNvbnRleHRfbWVtYmVyc2hpcHNfdXJsIjoiaHR0cHM6XC9cL215bGVhcm5lcmpvdXJuZXkuaW5zdHJ1Y3R1cmUuY29tXC9hcGlcL2x0aVwvY291cnNlc1wvMTE2XC9tZW1iZXJzaGlwX3NlcnZpY2UifSwiaHR0cHM6XC9cL3B1cmwuaW1zZ2xvYmFsLm9yZ1wvc3BlY1wvbHRpLWFnc1wvY2xhaW1cL2VuZHBvaW50Ijp7InNjb3BlIjpbImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aS1hZ3NcL3Njb3BlXC9saW5laXRlbSIsImh0dHBzOlwvXC9wdXJsLmltc2dsb2JhbC5vcmdcL3NwZWNcL2x0aS1hZ3NcL3Njb3BlXC9yZXN1bHQucmVhZG9ubHkiLCJodHRwczpcL1wvcHVybC5pbXNnbG9iYWwub3JnXC9zcGVjXC9sdGktYWdzXC9zY29wZVwvc2NvcmUiXSwibGluZWl0ZW1zIjoiaHR0cHM6XC9cL215bGVhcm5lcmpvdXJuZXkuaW5zdHJ1Y3R1cmUuY29tXC9hcGlcL2x0aVwvY291cnNlc1wvMTE2XC9saW5lX2l0ZW1zIn19.f12R96mHmh24QSIHiJ7JuP_1-UlBw4fMOx2FNe5N2CyifA6dTRU_55IQnj1yaBMLOcKZRJMkYwvnBhnfsHwwniXkv9eail9b-p18qt_DRiBPyPMnFGkhpwXv7Hgxsda3LZRQmZS4gfj9Favi3Hb6kG5IV5HsAbNcr4GaLtG1sYy7ecgu38M0-cesUwVIhrEnMD--QBpLK8Dz4PVrR4MF8TtA0XF5RLXq2IFzl3vnbc60um2PBKKWTU_1Yt6II2aV5xGGDCHIeEmPFAi6FL8szezlqbZR8Fx-JnPJl6QQpZrXGC9e4bZS_yQFKWWTIX3W6AVOPmEXDqNNh038ykzBRg

this token has no any custom field as I just remove the custom field code from lti . Please let me what I am doing wrong.

the custom parameter you guys are getting after decoding the previous token was sent through LTI code we have added forcefully. it's not taking any custom value of the additional setting of the developer key form.

check this screenshot - https://prnt.sc/oDVCUroXHYFh