-
Notifications
You must be signed in to change notification settings - Fork 34
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
Clear PasswordVault when resetting the app #50
Comments
I've seen that this is already done in the SettingsPageViewModel. I wouldn't expect it here, think this should happen in the settings class. So maybe it's a good idea to terminate the app after the reset (maybe with a message box telling the user that the app will close). |
No, from a user view this is a terrible behavior. Like "you must restart your PC to finish the update". 😏 But a good catch! Thanks for the report! ❤️ |
Maybe also a good idea to put the vault.Retrieve in a try-catch block. I had some problems while debugging. When no credentials are available, vault.Retrieve will throw an exception which prevents the following up code to be executed. |
While working on #55, I've tracked the real problem: As a possible fix in #55, I've changed the CheckUserLogin method, so we're doing an API call for the user attributes. This will always fail when the invalid credentials are specified. |
Is the PasswordVault working? I got errors while using the last commits on the retrive function?! I already added try catch to prevent it, but the combase.dll from the emulator throws unexpected error... I'm using the emulator 10.0.10586, any ideas? |
No problems on 10.0.10586 (with pull request #55). |
I got this problem direct after login. |
UPDATE: there is a maybe problem in the PasswordVault with mail addresses as username. |
PasswordVault retrieve will fail, if there's a dot |
I can't find the root cause for this bug. But I have an idea how to change the implementation a bit, so that I can work around this. Basically, I will retrieve all credentials for a domain and iterate over them to find the one with the right username. Should work like this. |
After app reset you can log in with any password as long as server URl and user name are the same as before the reset.
When resetting the app we should call PasswordVault.Remove.
The text was updated successfully, but these errors were encountered: