key-cape/registry/capabilities/capability.iam.key-cape.md
tegwick 61ee563b1f docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
2026-10-14 06:39:53 +02:00

138 lines
4.7 KiB
Markdown

---
id: capability.iam.key-cape
name: OIDC identity and assurance
summary: OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI.
owner: key-cape
status: draft
domain: infotech
tags:
- iam
- oidc
- netkingdom
- security
- framework-reuse
maturity:
discovery:
current: D4
target: D5
confidence: high
rationale: README documents a versioned canonical contract (net-kingdom canon/standards/iam-profile_v0.2.md),
explicit lightweight-vs-expanded (Keycloak) migration story, and a completed
implementation status (all 23 workplan tasks, 21 green test packages).
availability:
current: A4
target: A4
confidence: high
rationale: 'Source interface assessed 2026-10-14: OIDC code with PKCE, service
tokens, JWKS, MFA and caller CLI. Availability describes the delivery form,
not production acceptance. Current stack is Authelia, LLDAP and privacyIDEA;
service secrets remain static and recovery proof has open gates.'
external_evidence:
completeness:
level: C2
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- full v0.1 implementation per its own workplan (23/23 tasks)
- 21 test packages, all green
- documented lightweight-to-expanded (Keycloak) migration path
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R1
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- maturity claims rely on the repo's own workplan completion record, not independently
re-verified in this sweep
discovery:
intent: OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI
includes:
- OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI
excludes:
- Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static
and recovery proof has open gates
assumptions: []
use_cases:
- 'U02: Human signs in with MFA and manages account or factor recovery'
- 'U03: Application combines identity, tenant and resource facts and enforces a
bound decision'
- 'U04: Protected operation obtains and consumes exact human approval before its
side effect'
- 'U10: Operator recovers identity, custody or data with independently held recovery
material'
research_memos: []
availability:
current_level: A4
target_level: A4
current_artifacts:
- SCOPE.md
- README.md
target_artifacts: []
consumption_modes:
- HTTP API
- source
relations:
depends_on: []
supports: []
related_to:
- capability.identity.user-engine
- capability.identity.tenant-facts
- capability.authorization.policy-evaluate
evidence:
documentation:
- SCOPE.md
- README.md
tests:
- .gitea/workflows/
- .forgejo/workflows/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- Human signs in with MFA and manages account or factor recovery
- Application combines identity, tenant and resource facts and enforces a bound
decision
- Protected operation obtains and consumes exact human approval before its side
effect
- Operator recovers identity, custody or data with independently held recovery material
not_recommended_for:
- Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static
and recovery proof has open gates
known_limitations:
- Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static
and recovery proof has open gates
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history:
- date: '2026-10-14'
dimension: availability
from: A2
to: A4
rationale: Interface-form reassessment from current owner sources; no completeness/reliability
promotion.
author: codex
---
# OIDC identity and assurance
OIDC code with PKCE, service tokens, JWKS, MFA and caller CLI.
## Reuse boundary
Current stack is Authelia, LLDAP and privacyIDEA; service secrets remain static and recovery proof has open gates.
## Supported use cases
- U02: Human signs in with MFA and manages account or factor recovery
- U03: Application combines identity, tenant and resource facts and enforces a bound decision
- U04: Protected operation obtains and consumes exact human approval before its side effect
- U10: Operator recovers identity, custody or data with independently held recovery material
## Evidence and integration
- [SCOPE.md](../../SCOPE.md)
- [README.md](../../README.md)
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.