-
Notifications
You must be signed in to change notification settings - Fork 879
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
go-redis/redis - Microsoft Entra Auth Sample #17384
Comments
Hi @joshfree, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
go-redis v9.5.2 added an Options.CredentialsProviderContext feature that supports Microsoft Entra authN. Let's add a code sample to this repo. Once completed, add a new table row to this Learn doc section with a link to the sample. |
The example is live in the package docs for v1.8.0-beta.2. I'll leave this issue open to track updating the Learn doc after the stable v1.8.0 release. |
Tracking issue for dogfooding and creating code samples (or documentation) to show best practices for how to use AAD Auth with popular 3rd party OSS Redis clients when connecting to Azure.
Depending on the outcome of the dogfooding:
Possible Outcome 1: 0-1 days of extra work (minimal sample code is required to enable the experience):
Possible Outcome 2: ~1 week of extra work (significant sample code is required to enable the experience):
Possible Outcome 3: (using AAD Auth with the client is blocked until code changes are first made to the OSS Redis client):
The text was updated successfully, but these errors were encountered: