Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / awinogrodzki/next-firebase-auth-edge issues and pull requests
#27 - Refreshing `customClaims`
Issue -
State: closed - Opened by steve-marmalade almost 2 years ago
- 6 comments
#27 - Refreshing `customClaims`
Issue -
State: closed - Opened by steve-marmalade almost 2 years ago
- 6 comments
#26 - Migration to v0.4.0
Issue -
State: closed - Opened by awinogrodzki almost 2 years ago
- 19 comments
#26 - Migration to v0.4.0
Issue -
State: closed - Opened by awinogrodzki almost 2 years ago
- 19 comments
#25 - feat: authentication middleware
Pull Request -
State: closed - Opened by awinogrodzki almost 2 years ago
#25 - feat: authentication middleware
Pull Request -
State: closed - Opened by awinogrodzki almost 2 years ago
#24 - Works perfectly in dev mode with an emulator but fails on Vercel and local build
Issue -
State: closed - Opened by yasaad about 2 years ago
- 2 comments
#24 - Works perfectly in dev mode with an emulator but fails on Vercel and local build
Issue -
State: closed - Opened by yasaad about 2 years ago
- 2 comments
#23 - Chore/static page example
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#23 - Chore/static page example
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#22 - fix: throw invalid credential error on refresh token expired
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#22 - fix: throw invalid credential error on refresh token expired
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#21 - Getting occasional `TOKEN_EXPIRED` errors in the middlewere when refreshing expired token
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 3 comments
Labels: bug
#21 - Getting occasional `TOKEN_EXPIRED` errors in the middlewere when refreshing expired token
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 3 comments
Labels: bug
#20 - Current example forces dynamic rendering on all pages
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 5 comments
#20 - Current example forces dynamic rendering on all pages
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 5 comments
#19 - Firebase Hosting only permits a single cookie
Issue -
State: closed - Opened by matthewlongpre about 2 years ago
- 7 comments
#19 - Firebase Hosting only permits a single cookie
Issue -
State: closed - Opened by matthewlongpre about 2 years ago
- 7 comments
#18 - fix: disable signature verification for Emulator tokens
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#18 - fix: disable signature verification for Emulator tokens
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#17 - createAuthMiddlewareResponse returns error Too big integer
Issue -
State: closed - Opened by vladgardus about 2 years ago
- 2 comments
#17 - createAuthMiddlewareResponse returns error Too big integer
Issue -
State: closed - Opened by vladgardus about 2 years ago
- 2 comments
#16 - Sign in with google
Issue -
State: closed - Opened by vladgardus about 2 years ago
- 1 comment
#16 - Sign in with google
Issue -
State: closed - Opened by vladgardus about 2 years ago
- 1 comment
#15 - error - Too big integer
Issue -
State: closed - Opened by seanaguinaga about 2 years ago
- 5 comments
#15 - error - Too big integer
Issue -
State: closed - Opened by seanaguinaga about 2 years ago
- 5 comments
#14 - Expired token not getting refreshed in Firebase Authentication Emulator environment
Issue -
State: closed - Opened by seanaguinaga about 2 years ago
- 17 comments
Labels: bug
#14 - Expired token not getting refreshed in Firebase Authentication Emulator environment
Issue -
State: closed - Opened by seanaguinaga about 2 years ago
- 17 comments
Labels: bug
#13 - [Next 13.1.1] [next.config.js] allowMiddlewareResponseBody is no longer available
Issue -
State: closed - Opened by atanaskanchev about 2 years ago
- 2 comments
Labels: enhancement
#13 - [Next 13.1.1] [next.config.js] allowMiddlewareResponseBody is no longer available
Issue -
State: closed - Opened by atanaskanchev about 2 years ago
- 2 comments
Labels: enhancement
#12 - Question: Using custom jwt over a package like jose
Issue -
State: closed - Opened by websiddu about 2 years ago
- 7 comments
#12 - Question: Using custom jwt over a package like jose
Issue -
State: closed - Opened by websiddu about 2 years ago
- 7 comments
#11 - Question: How to get the db from `const db = getFirestore(app);`
Issue -
State: closed - Opened by mxswat about 2 years ago
- 6 comments
#11 - Question: How to get the db from `const db = getFirestore(app);`
Issue -
State: closed - Opened by mxswat about 2 years ago
- 6 comments
#10 - feat: handle user not found error during token refresh
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#9 - Error in middleware when refreshing an expired token
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 4 comments
Labels: enhancement
#8 - feat: firebase authentication emulator support
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
- 1 comment
#7 - fix: rotating keys buffer length
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
#6 - Error in middleware running on Vercel
Issue -
State: closed - Opened by steve-marmalade about 2 years ago
- 1 comment
Labels: bug
#5 - Bump node engine to current LTS
Issue -
State: closed - Opened by ghost about 2 years ago
- 1 comment
Labels: enhancement
#4 - Emulator Issues
Issue -
State: closed - Opened by seanaguinaga about 2 years ago
- 5 comments
Labels: bug
#3 - Does not support [email protected]
Issue -
State: closed - Opened by abdelrahman-osama about 2 years ago
- 2 comments
Labels: bug
#2 - fix: fixed invalid character error when decoding base64 string encoded json
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago
- 2 comments
#1 - Feat/add next13 app example
Pull Request -
State: closed - Opened by awinogrodzki about 2 years ago