You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we remove the OAuth token acquisition logic from the core library and delegate OAuth token retrieval to a third-party library like https://godoc.org/golang.org/x/oauth2 as it handles things like refresh tokens, password credentials token, etc.?
The text was updated successfully, but these errors were encountered:
FYI we will not likely support refresh tokens, nor the password credentials token. We only support the Code grant flow.
Therefore, the OAuth2 lib may be overkill. I see a value to provide a simple implementation that covers what we offer in our API, since we will likely also have something similar in other clients.
This implementation follows the most common best practices around using a RoundTripper for authentication, rather than passing a credential and modifying the Do to apply the credential headers.
Definining a RoundTripper is a more flexible, powerful, and elengant approach.
This change requires to bump to 1.7 (given we add the dependency to golang/x/oauth2 that uses the context package).
ClosesGH-15
…e a new Client) (#69)
This implementation follows the most common best practices around using a RoundTripper for authentication, rather than passing a credential and modifying the Do to apply the credential headers.
Defining a RoundTripper is a more flexible, powerful, and elegant approach.
This change requires to bump to 1.7 (given we add the dependency to golang/x/oauth2 that uses the context package).
ClosesGH-15
Should we remove the OAuth token acquisition logic from the core library and delegate OAuth token retrieval to a third-party library like https://godoc.org/golang.org/x/oauth2 as it handles things like refresh tokens, password credentials token, etc.?
The text was updated successfully, but these errors were encountered: