Customized Response for Initial Login Route /login. feat: Customizable error handling.

Is your feature request related to a problem? Please describe. We are looking to use this as a framework for multiple platforms (multiple universities - primary Canvas and Blackboard) to register with our Tool. While registration should be handled via dynamic registration OR out-of-band with the university via a custom setup page on our end, university admins and instructors will miss steps and will end-up hitting our endpoints somehow incorrectly… Currently this library responds with a JSON msg and HTTP 400 with unregistered platforms.

Describe the solution you’d like To do deal with incorrect setups we will need to respond to unregistered platforms with friendly messages (instead of the default JSON msg with a HTTP 400 error) and potentially a link to a registration form. So the solution would be to inject a generic handler for this error “UNREGISTERED_PLATFORM” - example: onUnregisteredPlatform.

Describe alternatives you’ve considered May errors handled prior to on onInvalidToken, have a more generic handler.

Additional context

While in a perfect world this wouldn’t be an issue, but LMS admins and instructors are not often trained enough and struggle with these setups. With over 100 university setups and many of them being LTI 1.1 configured, we have seen this!

We absolutely can fork and create a PR also for changes.

[scalebig]

Hello @scalebig! I just released a version of Ltijs with the new onUnregisteredPlatform method. Please let me know if this solves your issues.

@Cvmcosta this looks like a great approach! we will give it a shot. Thanks again for digging into that!

[scalebig]

BTW - great job from I can see so far! If we integrate this, it will be used by our product that serves over over 50K students currently 😃