-
Notifications
You must be signed in to change notification settings - Fork 203
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
sessionClaims content not getting added to the decoded token #1135
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Same happening for customClaims. It doesn't work. Can we get some help? |
We'll have a fix out soon (recently merged #1199). Thanks for your patience. |
As far as I can tell this is still broken. displayName overwrites correclty but any returned sessionClaims and customClaims are not available on the client. Has there been any progress on this issue? Thanks for any help you can provide. |
I found another bug that is possibly linked to this. I opened an issue for the same here: |
Putting this here - just in case it solves things for anyone like me:
I'd recommend the using the identity platform library approach though |
Related issues
N/A
[REQUIRED] Version info
node: 16.14.0
firebase-functions: 3.21.2
firebase-tools: 10.7.1
firebase-admin: 10.2.0
[REQUIRED] Test case
https://cloud.google.com/identity-platform/docs/blocking-functions#setting_custom_and_session_claims
Web App
Cloud Function
[REQUIRED] Steps to reproduce
The project was originally a GCP project and is using Identity Platform but I had to setup Firebase in it for various reasons.
beforeSignIn
Cloud Function viafirebase-tools
signInWithPopup
fromfirebase/auth
idTokenResult
[REQUIRED] Expected behavior
The
sessionsClaims
I returned from thebeforeSignIn
Cloud Function should be included in the decodedidToken
[REQUIRED] Actual behavior
Claims not getting added when I print the result of the codes below:
Were you able to successfully deploy your functions?
Yes. Also printing debug logs as expected.
The text was updated successfully, but these errors were encountered: