SSO provider endpoints are not checked against the outbound-connection rule

未关闭
#971 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python

调研方向

Start at the Okta OIDC sign-in callback and the SSO configuration save flow, then find the outbound-connection check already used by warehouse connectors. Reuse that rule for sso_url when configuration is saved and when sign-in builds endpoint URLs. Add tests covering acceptance of a public HTTPS host and rejection of loopback or private hosts, with redirects still disabled.

由索引模型根据 Issue 内容生成。

描述

enhancement post-launch

The OIDC sign-in callback for the okta SSO provider builds its endpoint URLs from the provider's configured sso_url. The URL must be https:// and redirects are not followed, but the host is not checked against the outbound-connection rule the warehouse connectors apply (public addresses only, no loopback, link-local or private ranges).

The sso_url is set only by an ADMIN, so this is hardening rather than a defect anyone else can reach.

Expected: the SSO provider endpoints go through the same outbound-connection check as the warehouse connectors, both when the SSO configuration is saved and when a sign-in uses it, with a test that a loopback or private host is refused.

主要语言
Python
星标
0
派生
4
平均合并
5 小时 19 分钟
30 天内合并 PR
503

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。