密码更改后ElasticSearch连接状态
我们仅在 api 启动时使用用户名密码初始化 RestHighLevelClient （spring-boot 应用）。
密码可以在外部更改/重置的可能性很小（也许通过人为错误）稍后当我们的 api 仍在运行时。
我的问题是，即使密码稍后更改，弹性连接在初始化后仍然保持活动状态吗？也许只检查了一次？如果没有，有什么优雅的方法可以在运行时（通过 Elastic API）更新此密码，而无需使用新密码销毁和重新初始化所有 bean？
注意：我还看到 RestHighLevelClient 已被弃用，如果有解决方案，我们也可以优先迁移到新版本
We initialize the RestHighLevelClient with username-password only at our api startup (spring-boot app)
There is a small chance that the password can be changed/resetted externally (maybe by mistake of a human) later while our api is still running.
My question is, does the Elastic connection still stays active after initialization even the password changes later? Maybe it's only checked one time? And if not, what is an elegant way to update this password at runtime (via Elastic API), without needing to destroy and re-initiliaze all our beans with new password?
Note: I also see that RestHighLevelClient is deprecated, We can also make it a priority to migrate to the newer version if there is a solution for this
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
RestClient 或通过 HTTP 进行通信的任何其他客户端将通过 基本身份验证标头。调用之间不会保留任何身份验证状态，这意味着如果在应用程序运行时密码发生更改，您将需要某种方法来更新应用程序代码中的密码（可能通过重新启动应用程序）。
不过，其他人可以更改密码听起来很奇怪。我强烈建议使用 另一种身份验证适合您的应用程序的机制（令牌或 API 密钥）。你会过得更好。
The RestClient or any other client communicating over HTTP will authenticate each calls via the Basic authentication header. No authentication state is kept between calls, which means that if the password changes while your application is running, you'll need some way to update the password in your application code (probably via restarting the application).
That someone else could change the password sounds weird, though. I would strongly suggest to use another authentication mechanism (tokens or API keys) that are proper to your application. You'd be way better off.