Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internalize more dependencies #127

Closed
ericchiang opened this issue Jan 12, 2017 · 8 comments
Closed

Internalize more dependencies #127

ericchiang opened this issue Jan 12, 2017 · 8 comments

Comments

@ericchiang
Copy link
Collaborator

ericchiang commented Jan 12, 2017

This package has several external imports. Namely

As we move forward we might try to internalize some of these dependencies. E.g. context is now part of the standard library, and we might try to see if we can implement some of the cachecontrol package internally.

cc @dghubble

@dghubble
Copy link
Member

This would make adding a go-oidc dependency more alluring. 👍

@ericchiang
Copy link
Collaborator Author

Random musing.

The OpenID Connect spec indicates that the Cache-Control: max-age header is the only really supported mechanism for caching. This might be easy to implement instead of using the full cachecontrol package, which interprets way more headers.

https://openid.net/specs/openid-connect-core-1_0.html#RotateEncKeys

I think golang.org/x/oauth2 is here forever, since it's exposed as part of the API.

I don't have a good answer about gopkg.in/square/go-jose.v2. I really don't want to implement a JWT library.

@ericchiang
Copy link
Collaborator Author

I think this would be a good effort for any v3 branch. Remove the oauth2 and cachecontrol imports. No other API changes.

@jackmcguire1
Copy link

bump, I don't need to download the google dependencies used in the example...

@ericchiang
Copy link
Collaborator Author

So realistically this would require a new major version of the package to drop the oauth2 import. The cachecontrol change would also probably be significant.

I'm totally fine with a v3, but I'd want to figure out the modules story.

@jackmcguire1
Copy link

I’m fine with any of those packages imo as it’s core functionality this module relies on, I just don’t want the bundled google dependencies, remove the example to a separate repo...

@ericchiang
Copy link
Collaborator Author

ericchiang commented Aug 2, 2019 via email

@ericchiang
Copy link
Collaborator Author

cachecontrol import has been removed in #259 for v3.

I don't think we'll be able to remove gopkg.in/square/go-jose.v2 or golang.org/x/oauth2 so going to call this fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants