We currently store configuration based on the clientId. With LTI 1.3 we also need to store some URL endpoints that are environment specific. This may make it difficult to use the LTI in a staging LMS environment as the client Id will be the same, but the URL for auth and keys will change. Instead we probably need to structure the config by the issuer value or allow multiple configs to be saved under the same client ID and checked against the issuer to match.
We currently store configuration based on the clientId. With LTI 1.3 we also need to store some URL endpoints that are environment specific. This may make it difficult to use the LTI in a staging LMS environment as the client Id will be the same, but the URL for auth and keys will change. Instead we probably need to structure the config by the
issuervalue or allow multiple configs to be saved under the same client ID and checked against the issuer to match.