iss:
ddavis36@xula.edu
(required, the issuer identifier identifying the learning platform)
login_hint:
814848
target_link_uri:
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA503N9KQgdPd3a2VCkD/y caokCt1AOfn5Og/LBditEWft0Lve6svTlTtLWy99zrUCHfsnBmMSrnkbe/qYB9wI 4bB8AOET6RT1L+5K4SEWQnT9gnTd7Npe+LPRMBTFk/+2jWB44QEXWgMv+J0j5IXf kuhluu83wFwdlZRhpbkOfixyfOe5nQ9+Y4qzUx/kN+KGK5UqeWzq1OZH7YKOiwhw sfYc4pmYFRp+Lxcg2oxDvM8p9rSt3Bc+BIcSlJ8FEsybkMj38vDZC/SR4sjy1Wi9 HQU+cRHjTsMLU1zSYIofQd+5M/BF33IdAw2+ih86teLgMbvkHDpiAS/6wZvCnmt4 LQIDAQAB
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
77083
(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:
235458
(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:
ddavis36@xula.edu
(required, the issuer identifier identifying the learning platform)
login_hint:
814848
target_link_uri:
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA503N9KQgdPd3a2VCkD/y caokCt1AOfn5Og/LBditEWft0Lve6svTlTtLWy99zrUCHfsnBmMSrnkbe/qYB9wI 4bB8AOET6RT1L+5K4SEWQnT9gnTd7Npe+LPRMBTFk/+2jWB44QEXWgMv+J0j5IXf kuhluu83wFwdlZRhpbkOfixyfOe5nQ9+Y4qzUx/kN+KGK5UqeWzq1OZH7YKOiwhw sfYc4pmYFRp+Lxcg2oxDvM8p9rSt3Bc+BIcSlJ8FEsybkMj38vDZC/SR4sjy1Wi9 HQU+cRHjTsMLU1zSYIofQd+5M/BF33IdAw2+ih86teLgMbvkHDpiAS/6wZvCnmt4 LQIDAQAB
(required, the actual end point that should be executed at the end of the OIDC authentication flow)
lti_message_hint:
77083
(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:
235458
(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)