Azure / BatchExplorer

A client tool to help create, debug and monitor Azure Batch Applications
https://azure.github.io/BatchExplorer/
Other
206 stars 69 forks source link

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

Open PierreAtUptale opened 5 months ago

PierreAtUptale commented 5 months ago

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:

PierreAtUptale commented 5 months ago

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 commented 5 months ago

This seems related in some way to This Microsoft Storage Explorer issue: https://github.com/microsoft/AzureStorageExplorer/issues/5537

Or that one from Azure Data Studio: https://github.com/microsoft/azuredatastudio/issues/22716

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

PierreAtUptale commented 5 months ago

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.