[azservicebus,azeventhubs] Allow custom endpoints #23668
Labels
Client
This issue points to a problem in the data-plane of the library.
Event Hubs
feature-request
This issue requires a new behavior in the product in order be resolved.
Service Bus
Milestone
Typical AMQP connections use the same value for the endpoint we connect to and the audience we use when requesting authentication tokens.
However, with TCP proxies, we can't do that - the endpoint we connect to (ex: localhost:5671) isn't the right endpoint to use for tokens (ex: ripark.servicebus.windows.net).
Other libraries have solved this by making it possible to pass a
CustomEndpoint
(or CustomEndpointAddress) - this would point to the proxy address (ex: localhost:5671).The text was updated successfully, but these errors were encountered: