With 3.0.0 support of user -> Azure Managed Identity support for Redis? #401
Replies: 5 comments
-
|
Update: I guess the nub of the matter is how the token is refreshed given the |
Beta Was this translation helpful? Give feedback.
-
|
You can pass in a configured ConnectionMultiplexer if you need anything this abstraction cannot configure already. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply Michael. Looking at CacheManager, it seems you use the Connection string from the passed Given that is the case, I think this will be good to go. If however another mux was created from that derived connection string and used instead then that would break (from my understanding of what is happening under the covers of the mux). Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
No, if you pas in a mux, the library will not instantiate its own. |
Beta Was this translation helpful? Give feedback.
-
|
Cool thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Per title, we are looking to move to Azure Managed Identities and are investigating support by CacheManager. I think this is the case but I am unsure how the
IConnectionMultiplexer-> Connection string works.So with the 3.0.0 release adding support for the
useroption does that mean that if we pass anIConnectionMultiplexercreated with theStackExchange.Redis.ConfigurationOptionsobject that is hammered with theConfigureForAzureWithTokenCredentialAsync()call we should be good?Of course it might be also (transparently) supported in 2.0.0 due to the Redis Connection string conversion?
Thanks for keeping the library up to date!
Beta Was this translation helpful? Give feedback.
All reactions