Merging changes from our fork back to upstream

[stefanfoulis]

This Ticket tracks our progress to bring changes from our fork back to the main releases.

We've been successfully using django-oidc-provider for many years now. We have a few special requirements that needed changes to django-oidc-provider. At the time we were not sure if our changes would be generally useful. And we had to move fast and didn't have the capacity to make PRs to the upstream repo. Once we had forked, even small improvements ended up on our fork, rather than the upstream repo 😬 .
We're tackling this technical debt now.

The main new capabilities:

• more extend-ability when creating the various tokens: we used this to add tracking of "devices" and be able to associate every token/code with a specific device
• support to customize key generation and making it work with larger keys (we use this for JWT access tokens)

All changes on the outdated base: stefanfoulis#10
All changes, squashed and cleand up a bit on the outdated base: stefanfoulis#13
Work in-progress rebasing the changes on current develop: stefanfoulis#7

Individual PRs and commits still to be rebased:

• Replace ResponseType model with a json field (1) #432
• Customizeable Code, Token and UserConsent (2) stefanfoulis/django-oidc-provider#8
• Support for tokens larger than 255 chars (3) stefanfoulis/django-oidc-provider#9
• Allow altering expires at dynamically (4) stefanfoulis/django-oidc-provider#11
• Allow dynamic login_url
• Allow dynamic redirect_uris
• Allow OPTIONS request to userinfo without auth
• Customizable session management key
• Added support for django 3.0, django 3.1 and django 3.2 and python 3.9 (skip)
• Update to Django 4.2 (skip)
• Skip consent if client.require_consent is False
• Don't advertize HS256 as supported id_token signature algorithm (TODO: make configurable)

Useful links

• everything that has changes upstream since the fork diverged: 628def9...develop