iss:
lti-ri.imsglobal.org
(required, the issuer identifier identifying the learning platform)
login_hint:
567046
target_link_uri:
https://integration-testing-portal.mursion.com/lti13/launch/scenarios/9906b271-ce1b-462b-a5b6-ecc262939b04
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
70541
(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:
31-Aug
(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:
0dd531e2-5006-4af2-a6a8-7dde73df1466
(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:
lti-ri.imsglobal.org
(required, the issuer identifier identifying the learning platform)
login_hint:
567046
target_link_uri:
https://integration-testing-portal.mursion.com/lti13/launch/scenarios/9906b271-ce1b-462b-a5b6-ecc262939b04
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
70541
(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:
31-Aug
(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:
0dd531e2-5006-4af2-a6a8-7dde73df1466
(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)