CLUI Deployement Descriptor for {{cluiAppName}}. You can bookmark it for later reuse.
LTI Deployement Descriptor for {{ltiAppName}}. You can bookmark it for later reuse.
LTI 1.3 only: as ZTest is stateless, there is no formal registration, so the client ID must be passed in the init login URL. So 1st deploy ZTest, get the client_id, then redeploy with the client id.
For inline activities: identifies which JS handler is in charge of rendering the activity in the Mindtap reader
Gating:
Privacy Settings:
The secret is ztest-secret, consumer key can be any value as long as it is unique per deployement.
For LTI certification, use: IMS Certification Deployement Descriptor with email, name, id, only id, only name and id, only email and id
Supported platforms are: moodle, mindtap for mindtap-soa. If no platform is passed, then it defaults to mindtap-classic.
3rd party login url{{lti13login}}client_id is required (as ZTest is stateless). "platform" is optional and for values, see supported platforms
Redirect URI{{lti13redirect}}ZTest uses the LTI end point as the redirect URI.
Public Key
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz0mJyluayxOAx3knAz5y
X7jevpyLhuVKs+Ib2lRF+j/omUrsEvdt93i2qOoB7Vy5Bq5Q9mN2ZKW63e932KZV
7Mu97RCozMgHGQZU6OeF8pQfk1dfRO3VayQwv5A0brC22LqFt3eo2ybN9iHifuUU
oSndRcHSVsa392okeH0oJuBSUzJX3brrzP5BNgUR1okap4KUp8oH3AyC/HEYe9RL
DkvqF/jMdH4z/AgNuYQ74s8d1MABk6FhaVgad0WRV0hCNsB+E/mQ+z0Fs+XsbPa1
ppuiYePAuf82eEB8KG/QwJAAGl4KRKEkBgE8oV1nPD1pKM9I/PjPCnEWgtgj6qpB
twIDAQAB
-----END PUBLIC KEY-----
launch url{{lti11url}}
consumer keyAny value
shared secretztest-secret