You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firebase auth uses JWT tokens for authentication, not cookies. JWT tokens are short live so if we pass that in to the server through cookies and verify it, there's a high chance that it's already expired.
Service workers might work although I haven't tried this solution yet.
Here's the flow of I think FastBoot auth could work:
Have a service worker that intercepts fetch and modify to add the result of getIdToken()
In FastBoot server, verify the token through verifyIdToken().
Once the verification succeeds, we generate a custom token through createCustomToken().
We then pass-in the custom token in the request header to Ember FastBoot (maybe in Authorization header?)
This addon can support points 1 and 5 although I'm still contemplating if we should have 1 built-in. Points 2, 3, and 4 would have to be done in the FastBoot server which is out of our control.
The text was updated successfully, but these errors were encountered:
Firebase auth uses JWT tokens for authentication, not cookies. JWT tokens are short live so if we pass that in to the server through cookies and verify it, there's a high chance that it's already expired.
Service workers might work although I haven't tried this solution yet.
Here's the flow of I think FastBoot auth could work:
fetch
and modify to add the result ofgetIdToken()
verifyIdToken()
.createCustomToken()
.restore()
hook. We'll be usingsignInWithCustomToken()
to finally sign in the user.This addon can support points 1 and 5 although I'm still contemplating if we should have 1 built-in. Points 2, 3, and 4 would have to be done in the FastBoot server which is out of our control.
The text was updated successfully, but these errors were encountered: