You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using TableServiceClient with .NET Aspire, the recommended approach is to configure just the URI for the table and use RBAC to configure permissions to access the table.
However if the "connection string" is just a URI, the below fails as that is not a valid connection string:
For now I've stuck with using a storage connection string to both IdentityCloudContext and .NET Aspire work together with the same configuration setting. The ideal solution would be for IdentityCloudContext to allow a way to inject a TableServiceClient (e.g. a factory delegate property on IdentityConfiguration) so that the client registered with DI by .NET Aspire can be used instead of this library creating one itself.
The text was updated successfully, but these errors were encountered:
When using
TableServiceClient
with .NET Aspire, the recommended approach is to configure just the URI for the table and use RBAC to configure permissions to access the table.However if the "connection string" is just a URI, the below fails as that is not a valid connection string:
identityazuretable/src/ElCamino.AspNetCore.Identity.AzureTable/IdentityCloudContext.cs
Line 33 in f5cc8e3
.NET Aspire supports both connection strings and a service URI to create instances of
TableServiceClient
.For now I've stuck with using a storage connection string to both
IdentityCloudContext
and .NET Aspire work together with the same configuration setting. The ideal solution would be forIdentityCloudContext
to allow a way to inject aTableServiceClient
(e.g. a factory delegate property onIdentityConfiguration
) so that the client registered with DI by .NET Aspire can be used instead of this library creating one itself.The text was updated successfully, but these errors were encountered: