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
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):
Check-in a thin / simple code sample project to our sdk repo.
Share the sample with the Azure Redis team so that they can then share the sample with customers, publish updated docs, and also validate the service handles credential revocation and similar scenarios to test with the provided sample.
Possible Outcome 2: ~1 week of extra work (significant sample code is required to enable the experience):
Discuss the investigation results with the Identity SDK and Redis teams before proceeding
Based on the discussion, decide on whether we should be building a sample or an extension library that is shipped instead.
Possible Outcome 3: (using AAD Auth with the client is blocked until code changes are first made to the OSS Redis client):
Discuss the investigation results with the Identity SDK and Redis teams.
File GitHub issue with 3rd party project. Provide as much details as possible, including any code samples, gists, etc.
The text was updated successfully, but these errors were encountered:
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.
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: