Allow injecting `searchBase` and `searchFilter` via a SecretClass in ldap AuthenticationClass
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- kubernetes, rust
调研方向
该 payload 没有指出任何实现文件或测试。首先定位 LDAP CRD AuthenticationClass 和 SecretClass 的解析路径；将现有的 bindCredentials 处理方式与提议的 searchBase 和 searchFilter 字段进行比较，然后定义 CRD 兼容性以及证明使用了 namespace 作用域值的测试。
由索引模型根据 Issue 内容生成。
描述
A customer reached out about enabling dynamic searchBase and searchFilter configuration of AuthenticationClasses for LDAP.
They are currently deploying NiFi clusters per team, that use a central ldap provider for authentication. Every team has an individual bind user that is only allowed to access ldap structures which are relevant for that team - which means that every team needs an individual 'searchBase' setting.
For the bindUser setting, we allow to configure that per namespace via a secretclass, so this is not an issue.
For the searchBase, this is hardcoded in the AuthenticationClass as a String, which at the moment means that the user has to have a dedicated authenticationclass per group that targets the same ldap.
One possible solution could be to allow specifying the searchBase and searchFilter via a SecretClass as well, this would allow the admininstrator in charge of maintaining the SecretClass to optionally delegate the searchBase (and searchFilter) to the users of this AuthenticationClass. Since these SecretClasses can be scoped to look in the namespace of a pod starting up, this would allow configuring a different searchBase per namespace, instead of just one global one.
An idea for how this could look in the CRDs is shown below, but this would most probably be breaking..
---
apiVersion: authentication.stackable.tech/v1alpha1
kind: AuthenticationClass
metadata:
name: ldap-simple
spec:
provider:
ldap:
hostname: my.ldap.server
port: 389
searchBase:
secretClass: openldap-searchbase
bindCredentials:
secretClass: openldap-bind-credentials
---
apiVersion: secrets.stackable.tech/v1alpha1
kind: SecretClass
metadata:
name: openldap-searchbase
spec:
backend:
k8sSearch:
searchNamespace:
pod: {}
---
apiVersion: v1
kind: Secret
metadata:
name: my-admin-credentials
namespace: userns1
labels:
secrets.stackable.tech/class: openldap-searchbase
stringData:
searchBase: blablabla
The need for this in this specific case arises out of the organizational practice of not having a global ldap bind user but rather "team specific" bind users that cannot access user objects from different teams.
An organizational solution for this issue would be to change this - but that is not always possible, so the question would be if making this configurable is something we want to add.
- 主要语言
- Rust
- 星标
- 13
- 派生
- 8
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/secret-operator 的其他 Issue
-
type/bug
难度 4/5 3-5 天 新手友好度 45/100
stackabletech/secret-operator#754 ·
维护者通常 3 天内回复
-
难度 3/5 1-2 天 新手友好度 48/100
stackabletech/secret-operator#753 · 1 条评论 ·
维护者通常 3 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
stackabletech/secret-operator#720 · 1 条评论 ·
维护者通常 3 天内回复
-
customer-request type/bug
难度 3/5 1-2 天 新手友好度 38/100
stackabletech/secret-operator#666 · 2 条评论 ·
维护者通常 3 天内回复
-
Allow certificates to contain subjects with allowed external names可能重新可做 @NickLarsenNZ 于 402 天前认领，目前没有进行中的 PR。 未关闭customer-request type/feature-improvement
stackabletech/secret-operator#630 · 7 条评论 · 已指派 1 人 ·
维护者通常 3 天内回复
查看 stackabletech/secret-operator 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
app documentation remote windows-os
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
oxidecomputer/dendrite#380 ·
维护者通常 5 天内回复
-
area:cli bug good first issue priority:high
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复