coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/docs/ops-sso-access.md
tegwick f885697e96
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 54s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m47s
Details
Activate ACTIVITY-WP-0025: Authelia SSO ingress for ops and Temporal UI 
Mark workplan active. Add Traefik ForwardAuth middleware and Ingress
manifests for activity.coulomb.social and activity-temporal.coulomb.social.
Prefer Authelia SSO identity for ops mutations; document DNS gate and
fleet pattern (docs/ops-sso-access.md).
2026-07-22 00:47:29 +02:00

2.9 KiB
Raw Blame History

Ops console + Temporal UI — SSO access design (ACTIVITY-WP-0025)

Audience

Founders / platform operators who already have Authelia accounts under coulomb.social SSO (LLDAP → Authelia → KeyCape MFA path).

Hostnames (locked)

Host Backend Purpose
activity.coulomb.social actcore-api:8010 Ops console /ops/ui, JSON /ops/*, existing API
activity-temporal.coulomb.social actcore-temporal-ui:8080 Temporal Web UI

Both resolve to the railiance01 Traefik LB (92.205.62.239) once DNS A records exist (same pattern as forgejo.coulomb.social).

Auth edge (fleet pattern)

Component Location
Ingress controller Traefik (ingressClassName: traefik)
TLS cert-manager ClusterIssuer/letsencrypt-prod
Login portal Authelia https://auth.coulomb.social
IAM / MFA KeyCape https://kc.coulomb.social (post-password)
Forward auth Traefik Middleware forwardAuth → Authelia /api/verify

Not oauth2-proxy — the live railiance01 stack already runs Authelia in namespace sso. Reuse it.

Middleware

Middleware/authelia-forwardauth in activity-core calls:

http://authelia.sso.svc.cluster.local:9091/api/verify?rd=https://auth.coulomb.social/

Response headers trusted into the app:

  • Remote-User
  • Remote-Groups
  • Remote-Name
  • Remote-Email

Access control policy

Authelia global default_policy: one_factor currently applies. MVP accepts any authenticated Authelia user. Follow-up (T06): LLDAP group activity-core-operators + Authelia domain rules (net-kingdom config change).

Mutation identity

Priority for ops mutations (POST /ops/...):

  1. SSO principal from Authelia headers (preferred)
  2. Shared ACTIVITY_CORE_OPERATOR_TOKEN (break-glass)
  3. Else 401/403 fail-closed

DNS (operator)

Create A records (or CNAME to the forgejo host pattern):

activity.coulomb.social           A  92.205.62.239
activity-temporal.coulomb.social  A  92.205.62.239

Until DNS exists, cert-manager Certificate will stay Pending and HTTPS will not serve. Manifests can still be applied.

Break-glass

Port-forward remains documented in docs/runbook.md if Ingress/SSO is down.

Manifests

  • k8s/railiance/30-authelia-middleware.yaml
  • k8s/railiance/31-ingress-ops-sso.yaml
  • k8s/railiance/32-ingress-temporal-sso.yaml

Apply after DNS:

export KUBECONFIG=~/.kube/config-hosteurope
kubectl apply -f k8s/railiance/30-authelia-middleware.yaml
kubectl apply -f k8s/railiance/31-ingress-ops-sso.yaml
kubectl apply -f k8s/railiance/32-ingress-temporal-sso.yaml
# set public Temporal URL on API after cert Ready:
kubectl -n activity-core set env deploy/actcore-api \
  ACTIVITY_CORE_TEMPORAL_UI_URL=https://activity-temporal.coulomb.social
kubectl -n activity-core set env deploy/actcore-temporal-ui \
  TEMPORAL_CORS_ORIGINS=https://activity-temporal.coulomb.social