Repository Issue Activity (beta)

#338 Support for Workload Identity Federation?

#359 Support login on hosts without the GCP metadata server (AWS, other clouds)

#356 `refreshServerCookies` no longer works, `getTokens` returns stale custom claims

#350 Nextjs 16 support

#352 User logs out after updating custom claims with refreshNextResponseCookies

#351 Node.js 24+ support

#310 handleLoginWithGoogleUsingRedirect not working

#348 Failed to getTokens after browser refresh or navigation. error: INVALID_SIGNATURE

#349 Starter example does not work

#347 Failed to determine project ID: TypeError: fetch failed

#346 How to pass the jwt token to a client-side fetch

#327 [Suggestion] New cookie-based persistence supported by Firebase

#322 How to use getValidIdToken?

#324 refreshCredentials isn't working on middleware

#331 TypeError: Key for the RS256 algorithm must be one of type CryptoKey or JSON Web Key. Received an instance of Uint8Array

#333 MISSING_CREDENTIALS with next-typescript-starter deployed to Firebase App Hosting.

#273 Private Paths

#344 Increased errors in refreshTokenPath since upgrading to 1.10.0

#339 'firebase/auth' signIn with action in Vercel Edge

#341 Calling refreshCredentials removes the customToken

#330 Feature Request: Add support for `privatePaths` in `redirectToLogin` to better handle error pages

#336 Question: tenantId config vs. inferring the tenant from the FirebaseAuth UserCredential object

#340 Firebase Newuser redirect

#337 ⚠️ [next-firebase-auth-edge] Called `getTokens`, but the request cookies were not verified by Middleware. Ensure that this route is included in the matcher config of your Next.js Middleware so that tokens remain up-to-date.

#329 next-firebase-auth-edge does not capture /api/login