Skip to content
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

feat: support separate authentication for Sentinel and Redis #888

Merged
merged 4 commits into from
Nov 26, 2024

Conversation

EquentR
Copy link
Contributor

@EquentR EquentR commented Nov 25, 2024

feat: support separate authentication for Sentinel and Redis

  • Add support for distinct username and password for Sentinel and Redis.
  • Resolve issues with connecting when Sentinel has no authentication but Redis does.
  • Handle scenarios where Sentinel and Redis have different authentication configurations.
  • Improve client logic to dynamically manage authentication based on configuration.

BREAKING CHANGE: Requires configuration update to specify separate Sentinel and Redis credentials.

功能:支持 Sentinel 和 Redis 的单独身份验证

  • 为 Sentinel 和 Redis 添加对不同用户名和密码的支持。
  • 解决当 Sentinel 没有身份验证而 Redis 有身份验证时的连接问题。
  • 处理 Sentinel 和 Redis 具有不同身份验证配置的情况。
  • 改进客户端逻辑,以便根据配置动态管理身份验证。

重大变更:需要更新配置以指定独立的 Sentinel 和 Redis 的身份验证。

EquentR and others added 4 commits November 25, 2024 11:50
- Add support for distinct username and password for Sentinel and Redis.
- Resolve issues with connecting when Sentinel has no authentication but Redis does.
- Handle scenarios where Sentinel and Redis have different authentication configurations.
- Improve client logic to dynamically manage authentication based on configuration.

BREAKING CHANGE: Requires configuration update to specify separate Sentinel and Redis credentials.
@suxb201 suxb201 merged commit d621053 into tair-opensource:v4 Nov 26, 2024
7 checks passed
@EquentR EquentR mentioned this pull request Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants