Replies: 1 comment 1 reply
-
I agree, it sounds doable to support custom claims. I initially didn't include them because I was uncertain if the same claims data and data structure was available from both the Firebase admin SDK and web JS SDK. However, the docs suggest that shouldn't be a problem. I'm actually not too concerned about the cookie size overhead, because Firebase already limits the size of claims, and managing claims data is up to each developer. More, I want to make sure:
It looks like this should be achievable just using the fields from Feel free to discuss approaches and/or open a PR. Thanks for opening this discussion! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What is the difficulty, if any, in supporting custom claims? I'm sure you don't want to dump in all the claim data into the cookie, but could we either set a flag or pass in an array of keys when initializing to include the custom claims?
If we were to use a flag, you could include all the claims that result from the call to customClaims from the admin server-side?
Or could we pass in an array of keys to include in the cookie?
Happy to help out! Really like your library, but need custom claims before I can rely on it instead of client-side-tokens atm.
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions