Does Google’s OAUTH2 implementation support dynamic client registration, as described in RFC7591? If so, I’ve been unable to find anything which says it does (or does not,) and in particular can’t find any mention of a client registration endpoint to use. I would like to use it for a desktop (native) application.
>Solution :
Google does not allow for programmatically creating Oath clients on their authorization server.
Creating and configuring of your project on google cloud console as well as creating client credentials, configuring the oauth2 consent screen and the clients themselves
must be done manually by the developer on google cloud console.
I’ve been unable to find anything which says it does (or does not,)
Typically one does not document what is not possible only what is possible. Documentation would be very large indeed if they tried to mention everything that they don’t allow.
By that logic normally if you cant find something its because its not supported. Wouldn’t it be great if it was though 😁