-
Notifications
You must be signed in to change notification settings - Fork 465
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
Update all other Azure components to use the common auth layer (and support Azure AD auth) #1103
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
👋 bot! |
It is pinned now. |
Azure Service Bus pubsub and bindings are handled in: #1201 This was done as part of the GAing process for the binding and I figured while I was there I'd get pubsub too. |
With #1290 I'm adding support for authenticating against the new "track 2" SDKs and I've updated the Key Vault secret store component. Support for the new auth library is required for all new SDKs, including Table Storage and the upcoming Cosmos DB. |
Needs to be implemented in EventHubs. Probably together with this issue: #2101 |
Is there support for using Azure CLI to retrieve credentials when running locally? |
At this point, it seems all Azure components support Azure AD. Almost all have also been updated to the "track 2" SDKs, with the only exception being Azure Storage Queues. That SDK is expected in a few weeks / months, so we'll do the upgrade once it's available. Probably safe to close this issue @berndverst |
Is there a plan to include support for MSI for Event Grid as well anytime soon? |
@ana-cozma Event Grid should work with MSI in Dapr 1.10 |
This is now complete in Dapr 1.11 (Storage Queues was upgraded as well) |
Hi Team! We are trying to use "state.sqlserver" component configured to use User-Managed-Identity to connect to Azure SQL Server Database instance. Is that supported? I'm facing this issue when trying to connect to SQL: SqlConnectionString: We are deploying via Bicep Tempalte: Appreciate any help, thanks! |
@giovanidecusati thanks for the report. I've created a new issue for this #2726 |
This is a "spin-off" from #972 given how it was merged with only 2 components updated.
Goal of this issue is to track what Azure components still need to be updated to support authentication via the "common auth layer" (implemented in #972). This enables components to authenticate with Azure using Azure AD, including support for service principals and MSI.
While updating components to use the common Azure auth layer, we have been making sure (where appropriate/relevant) to also support for other Azure clouds (Azure China, Azure Germany, Azure Gov, and also Azure Stack) and even emulators when appropriate.
Here's the list of components that use Azure and their status:
bindings/azure/blobstorage
- Uses keysbindings/azure/cosmosdb
bindings/azure/eventgrid
- Currently supports client credentials auth but with its own logicbindings/azure/eventhubs
- Uses keysbindings/azure/servicebusqueues
bindings/azure/signalr
- Uses "connection strings"bindings/azure/storagequeues
- Uses keyspubsub/azure/eventhubs
- Uses keyspubsub/azure/servicebus
secretstores/azure/keyvault
state/azure/blobstorage
state/azure/cosmosdb
state/azure/tablestorage
- Uses keysThe text was updated successfully, but these errors were encountered: