-
Notifications
You must be signed in to change notification settings - Fork 350
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
Cannot call getSignedUrl
when using authorized_user default credentials locally
#2413
Labels
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Derrreks
changed the title
Cannot call
Cannot call Dec 14, 2023
getSignedUrl
when using default service account locallygetSignedUrl
when using authorized_user default credentials locally
We have the same issue. It would be great to see a proper solution to this. As a workaround we made a special cloud function (that is always running in the cloud) that generates signed urls that we call instead of the normal getSignedUrl functions when running in the emulator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[READ] Step 1: Are you in the right place?
template.
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
I'm initializing like:
but when I do that am unable to call
Bucket.file().getSignedUrl()
with the error:Looking into my local Firebase credentials, I notice there is no
client_email
there, but there is when using service accounts. I've found some issues around that seem to say this isn't possible with a personal service account (example).If that's true, is it not possible at all to use my personal service account to work with files? Or is there a workaround that will enable this to work?
The text was updated successfully, but these errors were encountered: