-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
bug: user has to re-login every time chrome sidepanel opens #5297
Comments
To resolve the issue of the user having to re-login every time the Chrome sidepanel opens, you can implement a solution that checks for an existing authentication token in Chrome's storage and uses it to verify the user's session automatically. Here are the specific steps to implement this solution:
By implementing these changes, the extension will be able to maintain the user's authentication state across sidepanel sessions, eliminating the need for repeated logins. Referencestwentyhq/twenty/packages/twenty-chrome-extension/src/background/index.ts |
If the issue is still open, I would like to work on it! |
Bug Description
Chrome sidepanel doesn't persist state in the background, every time we close/open sidepanel it loses its previous state and restarts again. So we end up having to login everytime.
Screen.Recording.2024-05-06.at.8.29.23.AM.mov
Expected behavior
Ideally need to bypass login automatically and directly route to desired page
Technical inputs
One way could be to use our
/verify
route withauthToken
as query parameter, like/verify?authToken=....
similar tologinToken
query parameter which is already present. We can get our authToken from chrome's storage, verify it on backend and return if its valid, then set the required state for the app to load and then redirect it to our desired routeThe text was updated successfully, but these errors were encountered: