iss:
https://lti-ri.imsglobal.org
(required, the issuer identifier identifying the learning platform)
login_hint:
946328
target_link_uri:
https://62cc97eccac8.ngrok.io/api/v2/dispatch/destinations/3408e5a3-5d1f-4e1d-a80e-57c94eea044c/launches?externalConfig=pA6vD6kFu10ei1WQ4iLv3cJTV7kySlYKQW6Cjothc6nkdwycPUnt_meM-aPFqlv0_A48fAwIWA
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
39455
(required, this is an LTI specific parameter identifying the actual message to be executed. For example it may be the resource link id when the message is a resource link request.)
lti_deployment_id:
1
(optional, if included, MUST contain the same deployment id that would be passed in the https://purl.imsglobal.org/spec/lti/claim/deployment_id claim for the subsequent LTI message launch.)
client_id:
scorm2004
(optional, specifies the client id for the authorization server that should be used to authorize the subsequent LTI message request. This allows for a platform to support multiple registrations from a single issuer, without relying on the initiate_login_uri as a key)
iss:
https://lti-ri.imsglobal.org
(required, the issuer identifier identifying the learning platform)
login_hint:
946328
target_link_uri:
https://62cc97eccac8.ngrok.io/api/v2/dispatch/destinations/3408e5a3-5d1f-4e1d-a80e-57c94eea044c/launches?externalConfig=pA6vD6kFu10ei1WQ4iLv3cJTV7kySlYKQW6Cjothc6nkdwycPUnt_meM-aPFqlv0_A48fAwIWA
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
39455
(required, this is an LTI specific parameter identifying the actual message to be executed. For example it may be the resource link id when the message is a resource link request.)
lti_deployment_id:
1
(optional, if included, MUST contain the same deployment id that would be passed in the https://purl.imsglobal.org/spec/lti/claim/deployment_id claim for the subsequent LTI message launch.)
client_id:
scorm2004
(optional, specifies the client id for the authorization server that should be used to authorize the subsequent LTI message request. This allows for a platform to support multiple registrations from a single issuer, without relying on the initiate_login_uri as a key)