Skip to content

Secondary Authentication fails in Production style URL #2208

@vigneashs

Description

@vigneashs

Which service(blob, file, queue, table) does this issue concern?

Blob, queue, table, all of them fail.

Which version of the Azurite was used?

V3.26.0

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

NuGet - custom built

What's the Node.js version?

V18 LTS

What problem was encountered?

In Authentication string to sign, Authentication Path is not formed correctly when using Production style URL for secondary requests.

Steps to reproduce the issue?

Take any storage client, use production style URL with -secondary suffix for secondary read operation on Azurite.

You can observe the string to sign is malformed for these requests.

Have you found a mitigation/solution?

Yes, I have fixed the error. Until it gets merged use non-production style URL for secondary requests.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions