-
Notifications
You must be signed in to change notification settings - Fork 382
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
Feature Request: Official support for integration with firebase-admin and google-auth-library ExternalAccountClient. #1322
Comments
@hiranya911, @lahirumaramba, I'm not very familiar with Would happily take a patch. |
Source-Link: googleapis/synthtool@6981da4 Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:3563b6b264989c4f5aa31a3682e4df36c95756cfef275d3201508947cbfc511e
Source-Link: googleapis/synthtool@6981da4 Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:3563b6b264989c4f5aa31a3682e4df36c95756cfef275d3201508947cbfc511e Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
????? @bcoe you literally work for Google. How do you not have a contact at the Firebase team that can help dive in and make things right? I've spent many many hours to diagnose and create the below issue, it seems like this lib and firebase's auth lib are on different planets, and for no good reason. |
Do we have an idea of when this is going to release? Also, I tried to implement the workaround that is mentioned in #1322 (comment).
Can someone please point me to the correct version for the provided workaround? |
Is your feature request related to a problem? Please describe.
firebase-admin
requires credential in STS response format, but it is not exposed:https://github.com/LumaKernel/google-auth-library-nodejs/blob/21a91c2c6e5317e6f6e2e8709bca2953999f98d4/src/auth/baseexternalclient.ts#L432-L432
We can calculate STS response from
cachedAccessToken
that is calculated from above, but it is private field.Describe the solution you'd like
Exposing cached STS response, and optionally, exposing
cachedAccessToken
.Describe alternatives you've considered
Only storing cached STS response and make
cachedAccessToken
getter.Additional context
Workaround:
It is real working workaround in our project.
The text was updated successfully, but these errors were encountered: