VPC中针对OpenSearch域的SAML身份验证

发布于 2025-01-29 03:31:34 字数 216 浏览 3 评论 0原文

我已经在VPC内部的私人子网中部署了AWS OpenSearch cluster。另外,可以使用公共IP中的公共子网中的代理服务器访问相同的操作。 有多个文档可访问带有代理和AWS Cognito服务的OpenSearch仪表板。但是我想设置SAML以供公众访问。对于此用例,该文档还不够清楚。

有没有办法,我们可以使用Azure作为身份提供商的代理服务器为OpoenSearch域设置SAML身份验证?

I have deployed a AWS Opensearch cluster in a private subnet inside a VPC. Also, can access the same with a Proxy server in a public subnet with its public IP.
There are multiple docs for accessing Opensearch Dashboard with Proxy and AWS Cognito Service. But I want to setup SAML for public access. The documentation isn't clear enough for this use case.

Is there a way, we can setup SAML authentication for Opoensearch Domain with Proxy server with Azure as Identity Provider?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

帅哥哥的热头脑 2025-02-05 03:31:34

我想使用AWS自己的SSO解决方案来执行此操作,该解决方案也支持SAML身份验证。但是,我在文档中遇到了这一说明,这似乎很重要。

您无法从其服务提供的值中更改SSO URL,因此SAML的openSearch dashboards不支持代理服务器。

https:// https:///docs.aws.aws.aws.aws.amazon.com/opensearch-earpensearch-earpensearch-epensearch-cearch-popensearch-empensearch-epensearch-empensearch-empensearch-empensearch-ement-服务/最新/developerguide/saml.html

可悲的是,目前,您要么必须公开OpenSearch域,使用AWS Cognito,要么坚持使用基本的身份验证进行OpenSearch。

I wanted to do this with AWS's own SSO solution, which also supports SAML authentication. However, I came across this note in the documentation, which seems relevant.

You can't change the SSO URL from its service-provided value, so SAML authentication for OpenSearch Dashboards does not support proxy servers.

https://docs.aws.amazon.com/opensearch-service/latest/developerguide/saml.html

Sadly it seems that, for now, you would either have to make the OpenSearch Domain public, use AWS Cognito, or stick with basic authentication for OpenSearch.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文