Implement RFC 7591 and 7592 (dynamic client registration)

[IvanAnishchuk]

Basically, in a project I'm working on that uses oauth-toolkit there's a need for api-based device registration and since there's a standard for that it seems to make sense to try and implement it here in a reusable manner.

https://tools.ietf.org/html/rfc7591
https://tools.ietf.org/html/rfc7592

Did anybody attempt anything like this before, does anybody have a similar need or any ideas regarding implementation? Any guidance or advice otherwise?

Basically, I'm prepared to do all the work myself but I'd prefer to make it generic and reusable as it feels like a nice feature for everyone.

[JonathanHuot]

Hi @IvanAnishchuk, the django-oauth-toolkit project is using https://github.com/oauthlib/oauthlib library where it contains all the RFC code.

I'll suggest to do in parallel the implementation of RFC7591 in oauthlib and also the oauthlib's wrapper in django-oauth-toolkit. It gives the best separation of concerns between the web framework and the protocol specification.

On oauthlib's side, we will be happy to review any PR and release new versions once integrated.