You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(adr): Amend ADR 0026 §12 with token-exchange scope #1365
ADR 0026 §12 reads as a feature roadmap for exchanging Keystone-native credentials (trust, application credential, EC2, Fernet) for OP JWTs, and ADR 0026 §13 Stage 4 presents Fernet-for-JWT exchange as the migration "long tail" tool. In practice:
Stage 3 moves machine identities away from application credentials to registered OAuth2Clients, and Stage 5 sunsets Fernet.
ADR 0036 (Proposed) supersedes trusts and defines on-behalf-of exchange (§6) as the delegation mechanism.
The ADRs therefore do not state which subject kinds the grant is meant to serve long-term, and the shipped AppCred-only implementation is described as the beginning of a roadmap rather than as a migration bridge.
What must be done
Add an amendment to ADR 0026 §12 stating the intended scope of the grant:
Legacy, migration-only: exchange of Fernet/JWS tokens and application-credential subjects. Frozen at its current feature set, sunset with Fernet (Stage 5). No Trust or EC2 subject support is added.
Amend §13 Stage 4 so it no longer implies Fernet exchange is a long-term feature.
Activity