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.

Sign up for GitHub

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

Jump to bottom

Enhancement: Reduce verify latency w/ cache-control #2

Open
kestred opened this issue May 18, 2018 · 1 comment
Open

Enhancement: Reduce verify latency w/ cache-control #2

kestred opened this issue May 18, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@kestred
Copy link
Collaborator

kestred commented May 18, 2018 •
edited
Loading

For high-volume sign-ins, Google recommends caching their client certificate according to cache-control headers on the HTTPS request used to fetch them.

We should switch the main verify function to use this flow instead of the slower "debug" flow using the tokenid endpoint.

See https://developers.google.com/identity/sign-in/web/backend-auth for more details.
@kestred kestred added the enhancement New feature or request label May 18, 2018
@kestred kestred changed the title Enhancement: Reduce verification latency by caching Google's certificate per the cache control headers. Enhancement: Reduce verification latency using cache-control. May 18, 2018
@kestred kestred changed the title Enhancement: Reduce verification latency using cache-control. Enhancement: Reduce verify latency w/ cache-control May 18, 2018
@kestred kestred added help wanted Extra attention is needed and removed help wanted Extra attention is needed labels May 18, 2018
@da-x da-x mentioned this issue Feb 7, 2020
Merged
@SeanOMik
Copy link

Wasn't this implemented with #4? Or maybe I'm misunderstanding what #4 actually did

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kestred @SeanOMik