Michael Wheeler

An [article from Unicon](https://www.unicon.net/insights/articles/lti-1.3-dynamic-registration-or-how-i-met-your-platform) describing how dynamic registration works.

Work happening upstream at https://github.com/dmitry-viskov/pylti1.3/pull/114

> Here's a Gist with a clip of the relevant code: https://gist.github.com/cmurtaugh/6a08cc2d3c717e2570ce7ca47d2ba9aa Thanks for sharing @cmurtaugh. Really excited to check this out!

One approach to this at https://github.com/Harvard-University-iCommons/django-lti-dynamic-registration

It looks like [CSP support is coming to Django](https://code.djangoproject.com/ticket/15727), so it probably makes sense for `django-lti` to align with that work as much as possible.

> I put together a first pass at this patterned after Django's RemoteUser backend and middleware: [#136](https://github.com/academic-innovation/django-lti/pull/136) Thanks @cmurtaugh I'll be taking a look at this soon.

Hi @cmurtaugh! I think I was imagining a much simpler authentication backend that only returns the user associated with the current `LtiLaunch` (if one exists). This leaves all decisions around...

@cmurtaugh Sounds great, thanks for the update! > I'd be happy to meet with you and your team at some point! I'm not sure of the best way to get...

> Pulling pylti1p3 code into django-lti would work, but UMich would miss an opportunity to give back to the open source community. That is, unless the pulling in would also...

Folks are actively discussing creating a maintained fork in https://github.com/dmitry-viskov/pylti1.3/issues/155. Hopefully it will pick up steam. I still think that there may be value in working to eliminate the dependency,...