-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Any plans for Managed Identity authentication for Microsoft.Extensions.Caching.StackExchangeRedis? #54414
Comments
…edis (#526) It seems like we need to use a connection string to connect to the Redis library used by IDistributedCache. Until we can use managed identity, that is the case. dotnet/aspnetcore#54414
Thanks for contacting us. This doesn't seem to be something worth implementing in the framework layer. |
You could ask for https://github.com/Azure/Microsoft.Azure.StackExchangeRedis to implement |
Thanks for the suggestion @halter73 . I'll test it out |
This would be nice to get support for MI in this. It's a big gap in dev experience from a using Microsoft products all up perspective. They said they won't do |
@arealmaas @A-Stapleton - we were able to get check out this comment: Azure/Microsoft.Azure.StackExchangeRedis#12 (comment) |
Sample on how to use MSI with IDistributedCache, just add the following in startup:
|
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I am using IDistributedCache, and I want to use Redis as backing. Using the following library and guide it seems like we need to pass a connection string. We want to be able to use Managed Identity towards all our Azure services.
https://learn.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-8.0#distributed-redis-cache
Describe the solution you'd like
Being able to authenticate to Redis using Managed Identity like we can for this package: https://github.com/Azure/Microsoft.Azure.StackExchangeRedis. Are there any plans on implementing Managed Identity for this?
Additional context
No response
The text was updated successfully, but these errors were encountered: