-
Notifications
You must be signed in to change notification settings - Fork 52
Blank error returned when using a key without Manage permission with SubscriptionManager.Get #229
Comments
Any news on this? |
@tomkerkhove looks like this is being handled as part of Azure/azure-sdk-for-go#15090 which has seen some very recent activity so hopefully still on the radar! |
I promise this is a coincidence, but I was actually just looking at this. @tomkerkhove, I've got a PR to fix this, needs to get reviewed and hopefully released next week. We just released beta 1 here: https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/messaging/azservicebus/ If you're interested there's a migration guide here as well: https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/messaging/azservicebus/migrationguide.md. We're still missing some functionality, but it's getting added fast :) |
…nagers" (#258) The various manager APIs all had their own error handling code, which would result in them occasionally obscuring the actual HTTP response error. We're now respecting the HTTP status codes and anything >= 400 causes us to fail with an actual error with text, rather than an empty error. Fixes #229
@MattJeanes - this fix has now been released in https://github.com/Azure/azure-service-bus-go/releases/tag/v0.11.3 |
Thank you @richardpark-msft - great work! |
Azure Service Bus Go version:
v0.10.12
(latest at time of writing)Go version:
go version go1.15.6 linux/amd64
As in the title, currently a blank error is returned when the call to
SubscriptionManager.Get
internally receives a 401 code (401 SubCode=40104: Invalid authorization token audience
)In my scenario, this was caused by using a service bus connection string without Manage permissions, only Send and Listen. I've had to debug right into the code in this package to have any idea of what was going on, and has caused difficult to diagnose downstream issues such as kedacore/keda#1499.
It would be fantastic if we could return a useful error here that could help users resolve the issue without having to resort to debugging in to see what's going on.
Minimal repro:
The text was updated successfully, but these errors were encountered: