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.

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

TypeError: invalid initialization vector preventing Entra sign in on 2.18.0-insider.813 #2905

Open
PierreAtUptale opened this issue May 16, 2024 · 3 comments

Comments

@PierreAtUptale
Copy link

PierreAtUptale commented May 16, 2024

Describe the bug
After updating to BatchExplorer 2.21.0-insider.995, upon opening the application, I was logged out of my Entra account and asked to sign in again. However, the sign in process fails with the following error after entering my credentials and completing 2FA:

TypeError: invalid initialization vector

Clicking 'OK' just keeps displaying the blue loading state with 'Prompting for user input' forever.

To Reproduce
Steps to reproduce the behavior:

  1. Open the application on Windows
  2. Complete the sign in process
  3. See error

Expected behavior
Completing the sign in process should have signed me in and let me access the application.

Screenshots
image

Logs
Please indicate how to access the logs when (Click profile > View Logs > app.log, client.log) is unavailable because I'm signed out.

Version:

  • OS: Windows
  • Version: 2.21.0-insider.995
@PierreAtUptale
Copy link
Author

Note that I've tried downgrading to version 2.20.0-stable.966 and I'm still unable to sign in due to the same error.

@PierreAtUptale
Copy link
Author

PierreAtUptale commented May 28, 2024

This seems related in some way to This Microsoft Storage Explorer issue: microsoft/AzureStorageExplorer#5537

Or that one from Azure Data Studio:
microsoft/azuredatastudio#22716

Though none of the proposed workarounds worked for Azure Batch Explorer.

@PierreAtUptale
Copy link
Author

After many more attempts, deleting the C:\Users\<USER>\AppData\Roaming\BatchExplorer and C:\Users\<USER>\AppData\Roaming\Batch Explorer folders did do the trick.

I'm now able to start the application again.

However, I'm leaving this issue open as I believe that the application should be able to auto-heal in this case.

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

1 participant