LTI 1.3 Response Issuer Exceptions

As we learned in the article entitled Creating an LTI 1.3 Adapter, the issuer value is automatically generated when you select the LTI 1.3 response type as your adapter endpoint. Sometimes, however, the issuer value within the LTI 1.3 response component will need to be adapted to accommodate a special use case. In particular, if you are using more than one LTI 1.3 adapter, even if they are each for different authentication protocols, you may have to modify the issuer of each additional adapter in order to ensure the correct adapter>external tool association.


For example, let's say your company or institution uses LTI for LMS authentication and SAML2 authentication within an employee portal. When using Apidapter as a middleware tool to ensure authentication from each access point into your application, you may need to adjust the response issuer to accommodate two separate LTI 1.3 consumers in your application. The following illustrates this point, using two adapters, "First Adapter" and "Second Adapter". These adapters are part of the same adapter property, called "Sample Property":



When creating more than one LTI 1.3 adapter within the same property, you should manipulate the issuer value that is auto-generated when you select the LTI 1.3 response type in a given adapter before clicking Save. The example below shows the values within each of our LTI 1.3 response components and their associated matching values within an LTI 1.3 deployment consumer within an external application:

First Adapter

Second Adapter


Keep in mind that regardless of the value within the Issuer field, the value must be recognized as a valid URL and must be unique to any other Issuer values within a given Apidapter property. Just make your desired edits to the autogenerated Issuer and click Save. Doing this will ensure that each Apidapter transaction is routed to the correct LTI 1.3 deployment consumer within your application. 


Questions? Comments? Compliments? Let us know by clicking here.



Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk