-
Notifications
You must be signed in to change notification settings - Fork 2
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
Disconnect from remote storage when logging out #42
Comments
This needs to be decided at the remoteStorage.js level – please don’t decide that in the app itself. Currently you need to log out of apps and storage separately because signing out of one app shouldn’t affect another. Signing out and switching users is mainly for development purposes, for that you can also use different browsers and incognito instances. The main use case will be one remoteStorage for everything. |
Preferably, I'd do this by giving the user an option to go to the remote storage provider and totally exit. |
Good point, this could be a general design pattern for unhosted apps: on the log out screen, give people a link to their storage, in case they want to log out of that too. If they don’t want to do that, they can just ignore it. |
connecting/disconnecting is no longer handled by the app code in 0.7, it's the app is informed of the session state, which can be anonymous, about the authorizations - there are 4 situations:
as Jan said, this behaviour is independent of whether you disconnect from On Tue, Aug 28, 2012 at 10:34 AM, Jan-Christoph Borchardt <
|
When logging out today, you are still (somehow, need to investigate) authorized in the remote storage. We need to put in an option somehow for disconnecting to the remote store as well.
Sometimes it is nice to be able to just logout to switch users back and forth, but sometimes I guess it is relevant not to be able to login again just providing the storage id.
The text was updated successfully, but these errors were encountered: