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.

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

Provide more details for SENDER_ID_MISMATCH if I have permission to see across projects #5545

Closed
denkc opened this issue Nov 13, 2023 · 2 comments

Comments

@denkc
Copy link

denkc commented Nov 13, 2023

What feature would you like to see?

As a developer, I'd like to be able to verify an ID token across all projects that I have access to in Firebase. There is an existing API to do so today but requires specifying a project ID and providing the correct credentials for each project.

https://firebase.google.com/docs/auth/admin/verify-id-tokens#verify_id_tokens_using_the_firebase_admin_sdk

How would you use it?

During debugging, the SENDER_ID_MISMATCH response tells you that a token is registered against a different project than it's being used for, but does not tell you what project it is. Since the Firebase portal knows which projects I already have access to, it would be helpful to have this built into the Firebase portal where, if I have access to the project, it can tell me the project it is registered to. Often, we will have dev/prod Firebase projects and provide the config during build time; this would help us debug the issue if they got mixed up.

@google-oss-bot
Copy link
Contributor

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@argzdev
Copy link
Contributor

argzdev commented Nov 14, 2023

Hi @denkc, thanks for reaching out. It seems to me that you might want this feature on the Admin SDK. Could you reach out to our Firebase Admin SDK team and file this feature request? Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants