search

Qabel / qabel-core

(B2C) :cloud: Implementation of Qabel-Core in Java
Other
20 stars 17 forks source link

Couple identities and accounts #629

Open audax opened 8 years ago

audax commented 8 years ago

An Identity should know to which account it belongs. This way, users cannot import identities that don't "belong" to their account.

julianseeger commented 8 years ago

Actually, one could have a single identity and one account per provider .. like a qabel.org account and a myHomeServer.dyndns.org account and an onpremise.mycompany.com account ... not that it's currently supported but maybe binding the identity to one account per provider is semantically more plausible.

Imho that's a more probable use case than one person hanging around with a bunch of identities on a single device...

julianseeger commented 8 years ago

ftr.: https://github.com/Qabel/qabel-core/pull/631 adds account-usernames to prefixes. If they are exported with the identity, one could check if the imported user has a prefix with an account-username and if so, compare that username to the currently used username. For future BC (sounds yagni^^) it might be useful to add providers to these usernames before exporting them

thechauffeur commented 8 years ago

Users are confused that after changing the account but keeping the identity the users' files are gone. We have to discuss this, about how we want the behavior to be.

thechauffeur commented 7 years ago

@audax and I talked about this and I further discussed this with Britta. The proposed solution is as follows.

julianseeger commented 7 years ago

We currently store the identities prefixes with the Accounts username. That means we can detect an Account switch but not if an imported identity has been previously used with another Account. It could be achieved by exporting the identity together with it's prefixes and their accounts.

Oliver Weidner notifications@github.com schrieb am Di., 13. Dez. 2016 13:27:

@audax https://github.com/audax and I talked about this and I further discussed this with Britta. The proposed solution is as follows.

  • Do not allow import of identity if it does not fit to the account currently logged in / used.
    • Question: Which are the possibilities to check this?
  • Instead refer to forgot password function with explanation. Explanation because: Users tend to just create another account if they lost their old one and import the old identity. They must understand that they should instead use password forgotten function.
    • If this is not the problem the user ran into we should encourage him to get in touch with our support.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Qabel/qabel-core/issues/629#issuecomment-266726132, or mute the thread https://github.com/notifications/unsubscribe-auth/ADG5iiJAWKvX21GgaZNhBLFxIQL_084Xks5rHo8ygaJpZM4KTl9S .