Skip to content
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

Better UI when tokens expire #915

Closed
astigsen opened this issue Aug 24, 2018 · 1 comment · Fixed by #1067
Closed

Better UI when tokens expire #915

astigsen opened this issue Aug 24, 2018 · 1 comment · Fixed by #1067

Comments

@astigsen
Copy link
Contributor

astigsen commented Aug 24, 2018

Right now if you leave Studio running, the Realm Cloud JWT will at some point expire, and then when you try to use Studio to connect to a server or open a Realm from a server Studio will just tell you that that your user is invalid.

If this happens after you used to Cloud dashboard to login, the only way to refresh it is to go all the way back to the webpage and re-login there and then use that to re-open Studio, which is not at all intuitive.

We should have a better UI here and at least allow users to login again (or even better, make sure their tokens are refreshed in the background so they never expire).

Aha! Link: https://realmio.aha.io/features/ROS-105

@kraenhansen
Copy link
Member

I updated the description above. I believe users experiencing this could restart Studio and then it would realize the expired token and ask the user to re-authenticate.

With regards to automatically refreshing the token, this is tracked by https://github.com/realm/raas/issues/322

@roberhofer roberhofer added this to the Sprint Week 37-18 milestone Sep 10, 2018
@kraenhansen kraenhansen removed their assignment Sep 10, 2018
@roberhofer roberhofer modified the milestones: Sprint 39-18, 4Q-18 Oct 23, 2018
@kraenhansen kraenhansen removed their assignment Dec 3, 2018
@roberhofer roberhofer modified the milestones: 4Q-18, 1Q-19 Dec 7, 2018
@kraenhansen kraenhansen self-assigned this Jan 2, 2019
@roberhofer roberhofer modified the milestones: 1Q-19, 3Q-19 Mar 19, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants