[QUERY] SharedAccessSignature not working for Event Hubs with Java SDK v5.1.2. #14595
Closed
3 tasks done
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Event Hubs
feature-request
This issue requires a new behavior in the product in order be resolved.
Service Bus
Describe the bug
SharedAccessSignatures aren't working for event hubs for v5.1.2 of the Java SDK.
Exception or Stack Trace
java.lang.IllegalArgumentException: Illegal connection string parameter name: SharedAccessSignature
To Reproduce
Generate a SharedAccessSignature for an event hub and attempt to use that Signature in the ConnectionString.
In previous versions of the SDK, that connection string would look something like this:
Endpoint=sb://<namespacename>.servicebus.windows.net;EntityPath=<eventhubname>;SharedAccessSignature=SharedAccessSignature sr=sb%3A%2F%2F<namespacename>.servicebus.windows.net%2F<eventhubname>&sig=IciALS180<somecharsremoved>&se=159<somenumbersremoved>&skn=SendRule
In the new version of the SDK, ConnectionStringProperties doesn't except the SharedAccessSignature option and throws an exception. I was unable to find any other option that supports SharedAccessSignatures.
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
I would expect the new SDK to have feature parity with the old version and support SharedAccessSignatures. Also, it appears that ConnectionStringBuilder was removed?
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: