Skip to content

Sync is success even after password is changed #9520

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

Closed
SagarGi opened this issue Mar 16, 2022 · 3 comments
Closed

Sync is success even after password is changed #9520

SagarGi opened this issue Mar 16, 2022 · 3 comments

Comments

@SagarGi
Copy link
Member

SagarGi commented Mar 16, 2022

Description

Even if i change the password from the server given that the use is already logged in in desktop client, syncing activity can still be performed without re authenticating the desktop client.

Steps to Reproduce

  • Log in to desktop client as u1
  • Change the password of the u1 from the server
  • Add/Delete some files/folders for u1 via server

Expected Behaviour

The client should ask for re authentication before syncing

Actual Behaviour

The files/folders syncs successfully without reauthentication

@SagarGi SagarGi mentioned this issue Mar 16, 2022
55 tasks
@michaelstingl
Copy link
Contributor

What login? Basic Auth or OAuth 2.0 ?

@fmoc
Copy link
Contributor

fmoc commented Mar 16, 2022

This is not an issue of the desktop client. The client just continues to use the existing session because the server permits it. The server is in control of the session, not the client.

In case you change the password, the server should invalidate existing sessions and thus revoke existing clients' access. It doesn't do in this case, though. The client cannot know that the passphrase has changed. It's the server's job to revoke access and force the client to reauthenticate. If it doesn't do so, there is nothing we can do, as this is clearly out of the client's scope.

You may want to open an issue with the server.

@TheOneRing
Copy link
Contributor

The oauth token is independent of the users password.
The server could decide to invalidate the token on a password change.
In general the issue is unrelated to the desktop client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants