iss: https://lti-ri.imsglobal.org (required, the issuer identifier identifying the learning platform)
login_hint:
DL1
target_link_uri: https://lti-ri.imsglobal.org/lti/tools/2630/deep_link_launches (required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint: 52242 (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: 12345 (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:
DL1
target_link_uri: https://lti-ri.imsglobal.org/lti/tools/2630/deep_link_launches (required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint: 68264 (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: 12345 (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)
Send Request