-
Notifications
You must be signed in to change notification settings - Fork 190
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
[firebase/auth] Unmaintained #912
Comments
Also, there is another package that uses X509 instead of JWK https://www.npmjs.com/package/@fiboup/hono-firebase-auth |
Will wait for @Code-Hex to respond. Otherwise, I might be able to help with |
@hls-app I didn't notice that. I will check it |
@hls-app Now that I have released the latest version with everything you want, you can contribute to @hono/firebase-auth, do you want a challenge? https://github.com/Code-Hex/firebase-auth-cloudflare-workers/releases/tag/v2.0.5 |
Thanks @Code-Hex . I have kind of already implemented this using https://github.com/fiboup/edgelibs/blob/main/packages/hono-firebase-auth/src/middleware.ts I think it is super simple and works perfect for my use case. I only need to validate the token and nothing more. It has got a validation issue but otherwise, looks super straightforward. |
@hls-app I'm not sure, but I think @hono/firebase-auth would be just as simple if it didn't deal with cookies. Can you give me an example of how you feel it's complicated? Anyway, I'm waiting for your @hono/firebase-auth PR! |
@Code-Hex Like I said, I think there is no need for JWK setup or KV setup in my use case. All I want to check is if the provided token is valid for a given project id. The package I mentioned only needs a project id and it just validates the token using the Google Public Key. I might be happy to create a new fork to simplify a few things in that package but so far for my use case, that package serves well for now. |
Which middleware is the feature for?
@hono/firebase-auth
What is the feature you are proposing?
The core package firebase-auth-cloudflare-workers seems not maintained and Cloudflare Workers now support node:crypto X509Certificate
There is an active issue and there is a fork that fixes this issue.
Auth seems to be a critical part and would be great if this will have first party support.
The text was updated successfully, but these errors were encountered: