Files
sso/deploy/k8s/ipass-sso.yaml
T
adminandClaude Code ddc396c992 fix(iap): 4 处 IAP location 补 X-Auth-* 注头 + 文档同步 (v0.7.22)
影响:sso_iap 验签后只设 $auth_* nginx 变量, 不会自动给 proxy_pass 请求加
X-Auth-User 等 5 个头. v0.7.22 前 4 处 IAP location 全部漏, demo app 读
X-Auth-User 拿到空字符串; nginx access log 显示 auth_user=admin ≠ 头已注.
补 5 行后下游 request.headers 正常, /me 端到端返用户身份.

改动:
- deploy/nginx.conf:/proxy/app-crm/{callback,/} + /proxy/app-mobile/{callback,/}
  四段 IAP location 各加 5 行 proxy_set_header X-Auth-* $auth_*.
- deploy/k8s/ipass-sso.yaml:镜像 tag v0.7.21 → v0.7.22; 头部注释记录此坑.
- docs/iap.md §6 坑列表加 #0, 附 5 行注头示例 + 解释 access log 误导.
- docs/integrate-with-iap.md §2.2 注释提醒(不照搬 4 段示例避免冗长);
  §6 ipass-sso 端 checklist + 失败排查表各加一条.

设计:sso_iap 注头责任全在 nginx.conf(不打算让 sso 插件自动改请求头——
保持 $auth_* 变量语义纯粹, 不想动就 $auth_* 直接用; 想要头自己
proxy_set_header, 跟 $arg_XXX / $http_XXX 风格一致).

Co-Authored-By: Claude Code <[email protected]>
2026-10-12 10:52:01 +08:00

172 lines
6.9 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# ============================================================================
# ipass-sso K8s 部署清单(wuguirong 租户 ns)—— SSO-only 精简版
#
# 2026-10-12 升级 v0.7.21 → v0.7.22 (IAP 补 proxy_set_header X-Auth-* 注头):
# - v0.7.21 nginx.conf IAP location 块只有 sso_iap on, 缺 proxy_set_header
# X-Auth-User $auth_user 等 5 行, 导致 demo app 收不到 X-Auth-User 头
# - 源码确认: ipass-plugin-sso/src/lib.rs:140 sso_iap 模块只设 nginx 变量
# $auth_user/$auth_email/$auth_groups/$auth_sub/$auth_token, 不自动加 header
# - 必须在每个 IAP location 块显式 proxy_set_header (4 处, 覆盖 app-crm /
# app-mobile 的 callback + iap 主块, callback 虽无 sso_sid 也保持一致)
#
# 2026-10-12 升级 v0.7.20 → v0.7.21 (IAP upstream 改 K8s Service + 删 hostAliases):
# - nginx.conf upstream: host.docker.internal:18101/18102 → app-crm-svc:8000
# / app-mobile-svc:8000 (同 ns ClusterIP, 见 deploy/k8s/iap-demo.yaml)
# - 移除 hostAliases 占位 (集群 DNS 直接解析 Service 名)
# - 镜像: v0.7.20 → v0.7.21
#
# 2026-10-12 重建(v0.7.20,从本机 OrbStack docker 迁回 K8s):
# - 镜像:v0.6.1 (旧) → v0.7.20 (与 docker 一致)
# - NodePort:30082 (旧) → 30089 (新;用户要"动态可分配端口")
# - 数据:subPath sso/ 已从 ~/.ipass-sso-data 同步过来(含 /proxy/app-crm
# 等 IAP redirect URI、企微 verify/、active.jwk.json)
# - Secret ipass-sso-secrets 已重建(WXWORK_SECRET / OAUTH_SIGNING_SECRET)
#
# 集群约束(与 ipass-all 同源,2026-09-26 摸底结论):
# - 准入 tenant-storage-guard:容器级 securityContext.runAsUser=10106(pod 级无效)
# - SC nfs-wuguirong 已恢复(2026-10-07 实测),仍复用 nginx-data PVC(共享)
# - 无 Ingress → NodePort
# - replicas=1:运行期真源是进程内共享内存 + JSON 写穿,
# 多副本各自持 shm 互不可见(脑裂),架构上不允许横向扩
#
# ⚠️ IAP /proxy/app-crm/ 反代上游指向 host.docker.internal:18101/18102:
# K8s pod 里 host.docker.internal 不解析 → 这两个路径会 502。
# 核心 OAuth/WeChat Work/管理台 全部不受影响(走 sso_sid cookie 与
# proxy_pass 到本机进程的逻辑不依赖 IAP 上游)。如需 IAP 复活,
# 需把 demo app 也搬上 K8s(或用 Mac LAN IP 直连 + demo app 改绑 0.0.0.0)。
#
# 暴露:Mac 28889 = socat 18889→K8s NodePort(30089),路由器 WAN:88 → Mac:28889
# 应用:kubectl apply -f deploy/k8s/ipass-sso.yaml
# 验证:curl -fs http://192.168.1.26:30089/.well-known/openid-configuration
# ============================================================================
apiVersion: apps/v1
kind: Deployment
metadata:
name: ipass-sso
namespace: wuguirong
labels:
app: ipass-sso
spec:
replicas: 1
strategy:
type: Recreate # 共享 PVC RWX 但数据语义单写:滚动时新旧并存会双写 JSON
selector:
matchLabels:
app: ipass-sso
template:
metadata:
labels:
app: ipass-sso
spec:
# 2026-10-12 移除 hostAliases 占位: IAP upstream 已从 host.docker.internal
# 改为 K8s Service app-crm-svc:8000 / app-mobile-svc:8000 (deploy/k8s/iap-demo.yaml),
# 同 ns 集群 DNS 直接解析, 不再需要 hostAliases.
# 之前占位理由 (nginx -t 拒启) 已不适用.
securityContext:
runAsUser: 10106
runAsNonRoot: true
fsGroup: 10106
# 数据子目录 bootstrap:subPath 目录必须预先存在且属主 10106
# (kubelet 对不存在的 subPath 按 root 属主建,10106 写不进——挂载成功
# 之后业务写盘才炸,最难查)。幂等,每次滚动都会跑。
initContainers:
- name: init-data-dir
image: crpi-yscq976uwza88qap.cn-shenzhen.personal.cr.aliyuncs.com/ssw188/nginx:ipass-sso-v0.7.22
imagePullPolicy: IfNotPresent
command: ["bash", "-c", "mkdir -p /persist/sso && ls -la /persist"]
securityContext:
runAsUser: 10106
runAsNonRoot: true
allowPrivilegeEscalation: false
volumeMounts:
- name: data
mountPath: /persist
containers:
- name: ipass-sso
image: crpi-yscq976uwza88qap.cn-shenzhen.personal.cr.aliyuncs.com/ssw188/nginx:ipass-sso-v0.7.22
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 18098
env:
# issuer 必须与浏览器/第三方实际访问地址逐字一致
# iPhone 走 i28868828dm.mayishangshu.cn:188 → 路由器 :188 NAT
# → 192.168.1.26:30089(K8s control plane NodePort)→ pod:18098
# (旧 i96772757dm.mayishangshu.cn:88 + Mac socat 链路 2026-10-12 废弃)
- name: OAUTH_ISSUER
value: "https://i28868828dm.mayishangshu.cn:188"
- name: OAUTH_COOKIE_DOMAIN
value: "mayishangshu.cn"
# 固定签名密钥:保证 docker → K8s 迁移后已签发 token 仍能验签
- name: OAUTH_SIGNING_SECRET
valueFrom:
secretKeyRef:
name: ipass-sso-secrets
key: oauth-signing-secret
# 企微 OAuth
- name: WXWORK_ENABLED
value: "true"
- name: WXWORK_CORP_ID
value: "wwac71328171b889cb"
- name: WXWORK_AGENT_ID
value: "1000015"
- name: WXWORK_SECRET
valueFrom:
secretKeyRef:
name: ipass-sso-secrets
key: wxwork-secret
- name: WXWORK_REDIRECT
value: "https://i28868828dm.mayishangshu.cn:188/portal/wxwork/callback"
securityContext:
runAsUser: 10106
runAsNonRoot: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: "1"
memory: 512Mi
readinessProbe:
httpGet:
path: /admin/
port: 18098
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /admin/
port: 18098
initialDelaySeconds: 10
periodSeconds: 20
failureThreshold: 3
volumeMounts:
- name: data
mountPath: /usr/local/nginx/data
subPath: sso
volumes:
- name: data
persistentVolumeClaim:
claimName: nginx-data
---
apiVersion: v1
kind: Service
metadata:
name: ipass-sso
namespace: wuguirong
labels:
app: ipass-sso
spec:
type: NodePort
selector:
app: ipass-sso
ports:
- name: http
port: 18098
targetPort: http
nodePort: 30089