This page is only for testing purposes. Never use this page for accessing Emended except when testing the integration. Never use a non-production instance of Emended for doing your work, or you will lose your materials.
This is a static page explaining the purpose of the various parameters used when performing a LTI launch request from your product to Emended. It also helps you validate your implementation by showing how a valid signature is calculated.
Please note that this page is provided as a static file only for demonstration purposes. Your implementation must always calculate the signature server-side, in order to protect your consumer secret.
The basics of the LTI integration are as follows:
The consumer key is matched to a LTI integration configuration in Emended, which belongs to a team.
The signature of the request is verified using the consumer secret.
The user id in your system is matched against known Emended users for the LTI configuration.
If the user id already matches a user in Emended, they are simply logged in.
If the user id does not match a user in Emended, they are prompted to create a new account. That account is then linked to the user id in your system.
If the user is an instructor in your system, they are given the instructor role in Emended and they are added to the team as an instructor.
If the user is not an instructor in your system, they are simply logged in.
Make sure of the following:
The user id must remain the same for the same user between requests when using the same consumer key.
The user id must not be the same for two users when using the same consumer key. Use different consumer keys if you have multiple source systems with different user ids.
The launch URL is the endpoint receiving the LTI launch request from your product.
For the production environment, this is always https://app.emended.com/lti/launch. You may use other values for testing.
The consumer secret is used for signing and therefore securing your request. The secret must always be handled securely by your server and must never be passed to clients.
You receive the secret either by logging in to your team in Emended or directly from Emended staff.