Open
Description
- Package Name: @azure/data-tables
- Package Version: 13.3.0
- Operating system: Any
- [* ] nodejs
- version: 18.X
- browser
- name/version:
- typescript
- version:
- Is the bug related to documentation in
- README.md
- source code documentation
- SDK API docs on https://learn.microsoft.com
Describe the bug
Since 13.3.0 and the introduction of the CosmoDB table support, it is impossible to start the azurite emulator on custom ports for the table service and make table access with a SAS key anymore.
To Reproduce
Steps to reproduce the behavior:
- Start Azurite table service on a custom port (for example 20002)
- Instantiate a table client with a SAS key (note: in our case the SAS key was generated with a service that was still using @azure/[email protected])
- Try to use that client to access the table: you get a "AuthorizationPermissionMismatch" error.
Expected behavior
Accessing the table should match the authorizations from the SAS key.
Additional context
This happens because of this line:
Which basically assumes that if this is not the default emulator port it must be CosmoDB...
In our local setup we have cases where we want to emulate locally our data separation in multitenant mode by accessing different azure storage servers depending on tenant. So we need to be able to run multiple azurite instances on custom ports to achieve that.
Metadata
Metadata
Assignees
Labels
This issue points to a problem in the data-plane of the library.Workflow: This issue is responsible by Azure service team.This issue requires a change to an existing behavior in the product in order to be resolved.Issues that are reported by GitHub users external to the Azure organization.Workflow: This issue needs attention from Azure service team or SDK team