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.

Sign up for GitHub

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

Jump to bottom

Changing server fail #237

Open
pixtron opened this issue Feb 17, 2020 · 1 comment
Open

Changing server fail #237

pixtron opened this issue Feb 17, 2020 · 1 comment
Labels
bug hasfix
Milestone
1.3.x

Comments

@pixtron
Copy link
Member

pixtron commented Feb 17, 2020

Describe the bug

Changing the server is only possible with a restart of the client

To Reproduce

1.) link an account on server1
2.) unlink account
3.) link account, enter server2
4.) login in with valid credentials

The whoami request is sent to server1 instead of server2 and therefore fails. Eventually when using oidc and both servers support the used idp it might be successfull (not tested).

Expected behavior

The whoami call should be successfull.

Environment

  • desktop client version: v1.2.x
@pixtron pixtron added the bug label Feb 17, 2020
@pixtron pixtron mentioned this issue Feb 17, 2020
Closed
@pixtron
Copy link
Member Author

pixtron commented Feb 17, 2020

Will be fixed with update to balloon-node-sync >= v0.6.5

@pixtron pixtron added this to the 1.3.x milestone Feb 17, 2020
pixtron added a commit that referenced this issue Feb 18, 2020
@pixtron
Update balloon-node-sync to v0.6.5
a9d7195 
Related to: #140, #237, #238
pixtron added a commit that referenced this issue Feb 18, 2020
@pixtron
Update changelog
3534d18 
Resolves: #140, #237
@pixtron pixtron added the hasfix label Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug hasfix
Projects
None yet
Milestone
1.3.x
Development

No branches or pull requests
1 participant
@pixtron