Ready to Go reverse proxy server that injects client secret to one or more configurable OAuth 2.0 token endpoints. This way the client secret is never exposed to the end user machine.
Custom Provider construction that is then added to the Registry. Some providers will be hardcoded (optionally not included, or not). Find a concise way of construction of an arbitrary provider.
Currently the Provider struct does not know it's ProviderID and is thus handled by the Registry. Maybe the IDs should be included in the Provider itself and the registry only pools the Provider-s to check their identification, given a request (maybe provider specific and not registry level thing).
After a successful token retrieval over the proxy, the client can call two static endpoints (or one that behaves as one) which displays a not_successful retrieval.