microsoft / microsoft/AzureStorageExplorer

Can't open blob container

Open
#9,050 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: blobs :gear: sign-in :grey_question: need logs
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

April 2026 (Version 1.43.0)

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

All

OS Version

No response

Bug Description

Unable to retrieve child resources.

It only happened on Azure storage explorer. When I open it on web browser, it works fine.

ProducerError:{
"name": "RestError",
"message": "{"name":"RestError","code":"InvalidAuthenticationInfo","statusCode":401,"details":{"errorCode":"InvalidAuthenticationInfo","content-length":"402","content-type":"application/xml","date":"Thu, 23 Apr 2026 20:46:51 GMT","server":"Microsoft-HTTPAPI/2.0","www-authenticate":"Bearer authorization_uri=https://login.microsoftonline.com/891a05bd-506b-48d8-b3ed-60f458010688/oauth2/authorize resource_id=https://storage.azure.com\",\"x-ms-request-id\":\"60bd0725-701e-00b0-5162-d31413000000\",\"message\":\"Server failed to authenticate the request. Please refer to the information in the www-authenticate header.\nRequestId:60bd0725-701e-00b0-5162-d31413000000\nTime:2026-04-23T20:46:51.6062045Z","code":"InvalidAuthenticationInfo","authenticationErrorDetail":"Issuer validation failed. Issuer did not match."}}"
}

Resource Types

No response

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Launch storage explorer.
  2. Expand a blob container
    It only happened on Azure storage explorer. When I open it on web browser, it works fine.
Actual Experience

It only happened on Azure storage explorer. When I open it on web browser, it works fine.

You will see an error message below

Unable to retrieve child resources

ProducerError:{
"name": "RestError",
"message": "{"name":"RestError","code":"InvalidAuthenticationInfo","statusCode":401,"details":{"errorCode":"InvalidAuthenticationInfo","content-length":"402","content-type":"application/xml","date":"Thu, 23 Apr 2026 20:50:49 GMT","server":"Microsoft-HTTPAPI/2.0","www-authenticate":"Bearer authorization_uri=https://login.microsoftonline.com/891a05bd-506b-48d8-b3ed-60f458010688/oauth2/authorize resource_id=https://storage.azure.com\",\"x-ms-request-id\":\"99124c21-701e-006e-6562-d3c7f4000000\",\"message\":\"Server failed to authenticate the request. Please refer to the information in the www-authenticate header.\nRequestId:99124c21-701e-006e-6562-d3c7f4000000\nTime:2026-04-23T20:50:49.8696774Z","code":"InvalidAuthenticationInfo","authenticationErrorDetail":"Issuer validation failed. Issuer did not match."}}"
}

Expected Experience

No response

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the blob-container expansion path in Azure Storage Explorer and reproduce the reported “Unable to retrieve child resources” error. Compare the desktop request and authentication details with the browser behavior; done means expanding the container retrieves its child resources without the 401 InvalidAuthenticationInfo issuer-mismatch error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
authentication, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.