-
-
Notifications
You must be signed in to change notification settings - Fork 931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication with Azure AD against Azure Service Bus #1345
Comments
Hey @Centzilius 👋, We also offer priority support for our sponsors. |
Any update on this feature request? |
no. contributions are welcome |
Hi PR #1641 solved this issue I think. I don't know if I should open a new issue, but I noticed an inconsistency in the mentioned PR. The new documentation states to use one of these formats:
While the code checks for one of these formats:
(DefaultAzureIdentity vs DefaultAzureCredential) |
It seems there is also another error in the code. When using DefaultAzureCredential azureservicebus.py
|
thanks for the report and new fix |
One more issue with this. The documentation suggests the following url formats: azureservicebus://SAS_POLICY_NAME:SAS_KEY@SERVICE_BUSNAMESPACE However, only the SAS auth allows you to use only the namespace, the other auth types require the full endpoint name, as implemented in this code: kombu/kombu/transport/azureservicebus.py Lines 144 to 154 in 9f4fd68
I assume we'd want them to all operate the same way... |
Hi,
could you please consider implementing an alternative authentication method for Azure Service Bus that is not SAS.
I'd like to use Azure Managed Identites to authenticate to reduce keeping secrets on my machine.
A way to implement this would probably look similar to this:
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/servicebus/azure-servicebus/samples/sync_samples/client_identity_authentication.py (Replacing EnvironmentCredential with either DefaultAzureCredential or ManagedIdentityCredential from the python package azure.identity).
The problem with this would probably be, how to identify that you want to authenticate with something else than a SAS but that could maybe be handled by providing specific dummy usernames in the connection string?
What do you think?
The text was updated successfully, but these errors were encountered: