-
Notifications
You must be signed in to change notification settings - Fork 375
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
Slow response times when obtaining Domain Wide Delegation token and during inbound Authorization header validation #1756
Comments
We're planning to migrate to newer token endpoints upstream, which may resolve this issue (assuming their aren't any other networking issues, like proxies): |
@danielbankhead I see this PR updates the /token endpoint but don’t see any updates to the /cert endpoint? |
I've conducted an audit an see that there are a few endpoints in this library that will also need to be updated - I'll take care of this shortly. |
I have a PR up to resolve, however it will require us to upgrade to Node 16 (which includes JWK support): However, we may be able to release the following PR sooner, which may be more helpful as the |
Environment details
google-auth-library
version: 8.19.4Obtaining an Domain Wide Delegated Access Token
We have two issues when using the client library when trying to PATCH a subscription. When patching a subscription for a Chat Space we are obtaining a users Domain Wide Delegated token to use as the Authorization header for the PATCH operation.
We are using the
GoogleAuth
client to obtain the token and during the call togetAccessToken();
it makes a request to the Google endpoint https://www.googleapis.com/oauth2/v4/tokenWe have been experiencing slow response times when hitting this endpoint as show in the attachments.
Header Authorization
We have also noticed slow response times during validation of the JWT Authorization header that is sent as part of the push notification. In the library it makes a call to https://www.googleapis.com/oauth2/v1/certs. Occasionally we have seen slow response times from this request as show in the attachments.
The text was updated successfully, but these errors were encountered: