[Community-Contributed]: Add an Authenticator to handle Proxy OAuth token endpoints that expect specific request headers/body
Summary
I recently made a change to an SDK tap to allow us to use our Proxy OAuth server to refresh user’s Google OAuth credentials, and this required specific headers and body to make the request.
I'm not sure if this is just a Proxy OAuth use case, but token end points requiring specific (different to the general api requests) headers and bodies would be able to utilize this new authenticator.
Proposed benefits
Chances are anyone who uses Proxy OAuth will run into the issues of the Proxy endpoint requiring different than normal headers and body to make the request.
Proposal details
Add an Authenticator that handles auth_token_headers and auth_token_body, alongside the usual auth_headers and auth_bodies.
Best reasons not to build
More authenticator choices could cause confusion about which you should use when. (More or less solved by adding docs/examples I think?)
Would be great to hear if anyone else has run into something like this, or other ways to go about solving it?
Like I mentioned, I’m not sure if Proxy OAuth Authenticator is the correct name, or if there is something more general for other use cases as well?