didimitrie
commented
5 years ago New behaviour:
Client, when deserialising, will search through any existing accounts for one matching the server's api as well as the email address used (in case duplicate accounts on same computer). If one is found, it's going to use that.
If none are found, it will search for any account present at the client's server url. If some are found, it will use the first one. If no accounts are found at that specific server, it will throw an error.
Upon successful deserialisation, clients are ad-hoc migrated to incorporate the user's email instead of their token in the serialisation process.
Step 0:
Expected Behaviour
Clients, when deserialised, should use the current user's api token.
Actual Behaviour
They use the creator's api token (they get serialised with it).
Affected Projects
Will propagate through Speckle Rhino and co, but ideally on the dev side changes will be minimal.