Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
createSessionCookie uses number when it should use a string
See original GitHub issueOriginally reported here https://github.com/firebase/firebase-tools/issues/2770#issuecomment-723364018
@samtstern I think this is a real issue, actually! I’m encountering it even though I’m executing createSessionCookie inside the function emulator. So I dug in, and I believe the validation schema is wrong. The auth emulator validation schema specifies validationDuration as a string, but firebase-admin-node constructs it as a number.
I note that the OpenAPI schema for createSessionCookie specifies the parameter as “string (int64 format)”. If that means it’s meant to be a string-encoded int64, then this is really a firebase-admin-node bug, although clearly the production auth server is accepting numbers for this parameter.
_Originally posted by @andymatuschak in https://github.com/firebase/firebase-tools/issues/2770#issuecomment-723364018_
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
FWIW: As of Firebase CLI v9.3.0, creating session cookie is now supported and we’ve also added coercion from number to string similar to production behavior (hat tip to @andymatuschak). Note that you need Node.js Admin SDK v9.5.0 to verify these cookies properly. (in reply to @aaronosher @muru)
Are there any news about this? Unfortunately, I haven’t found a workaround yet and the topic restricts local development considerably.