Repository navigation
Enable authentication when a non-default api_endpoint is set (just like the googleapis/nodejs-storage) #895
Description
Issue we're facing:
After version 2.1.0, authorization bearer token is stopped being sent to the custom endpoints (non-default api_endpoint), we forcefully needed to downgrade to the version 2.0.0 to make things work on our end. We had other option like explicitly passing credentials while instantiating the storage client, but this change was needed to be done in all places wherever the client is instantiated, so we just went to downgrade to the version 2.0.0.
Feature request:
Since this change feat: avoid authentication with storage emulator was intentional, can you please add a flag to enable the auth for custom endpoints something like in the googleapis/nodejs-storage?
A flag named useAuthWithCustomEndpoint was added in the nodejs storage client library to support the auth with custom endpoints. Just fyi, here are the code changes related to that flag.
Allow authentication with custom endpoint
Add support for useAuthWithCustomEndpoint option
Activity
cojenco commentedon Nov 8, 2022
Hi @MadhuPolu thanks for filing this issue. Could you please describe your use case in more detail?
If I understand correctly, the desire is for the client to detect the default credentials for the current environment while using a non-default api_endpoint, instead of explicitly passing in credentials. Is my understanding correct? The current design will not bypass auth if you pass in credentials when instantiating a client.
MadhuPolu commentedon Nov 8, 2022
Yes @cojenco, you're correct, we need the client to detect the default credentials while using a non-default api_endpoint. And we don't want to pass any credentials explicitly when instantiating a client as we heavily depend on ADC (Application Default Credentials).
Please let me know if you need any more details.
Trivials:
ADC is a strategy used by Cloud Client Libraries and Google API Client Libraries to automatically find credentials based on the application environment, and use those credentials to authenticate to Google Cloud APIs.
cojenco commentedon Nov 10, 2022
Thank you for the additional context👍 I'm working with our team to address this.
cojenco commentedon Dec 7, 2022
Hi @MadhuPolu the fix is now ready in v2.7.0 Thanks again for reporting!