Repository navigation
v0.30.0
Minor release (breaking for literal construction). New public fields:
TokenEntry.device_selectors,CallerCtx.verified_proposer,Attribution.verified_proposer,
ChangeSetRecord.owner_verified,TokenAction::Add.device_selector,
VerifiedApproverArgs.require_verified_proposer; new variant
VerifiedApproverArgsError::ProposerRequiresIssuer. Behaviour is unchanged unless the new
options are used. Upgrade every binary that rewritestokens.jsonbefore adding
device_selectors: an older binary drops the field ontoken rotate/set-scopes,
widening the token.
Added
- Static
tokens.jsonentries acceptdevice_selectors, the same grammar and semantics as
the OAuth scope map (narrowsdevices;nullrefused; one attribute snapshot per
authentication; an unlabelled device never matches). Opt in with
CallerCtx::from_entry_with_attributes;CallerCtx::from(&entry)grants no devices to a
selector entry.token add --device-selector(repeatable) and
TokenStoreFile::add_with_selectors(#400). - Approver roles are selector-scoped through the same field: approval already checks the
approver's device scope against the change set's one device, so asite=lab-*approver
cannot approve a prod change set. Pinned by an integration test; no new flag (#400). ChangesetCoordinator::approve_change_set_within: approves only if every device in the
change set'stargets()passes the caller's scope check, so asite=lab-*approver cannot
approve a multi-target set that also names a prod device. Servers' approve handlers should
call it instead ofapprove_change_set(#400).Mecmcp-Proposer-Assertionstep-up header (#400): a fresh IdP assertion whose subject equals
the proposing token's boundoidc_subject, bound withbind_proposer, which needs neither a
humantoken nor the approver role. A separate header and a separate field
(CallerCtx::verified_proposer,Attribution::verified_proposer) so it is never approval
evidence; it shares thejtireplay set, so one assertion is good once in either role.
A server with no verifier answers the header 400, as for the approver header. Both
assertion headers are now removed from the request once verified, so the JWT never reaches
tool extensions.--require-verified-proposer(VerifiedApproverArgs, requires--oidc-issuer) and
ChangesetCoordinator::with_require_verified_proposer: a proposal must carry an
IdP-verified proposer (ProposerIdentity, built byfrom_attribution; an OAuth principal
counts), proposed through the newcreate_change_set_as. The change set records
owner_verifiedand approval refuses one without it, so the two-person rule compares two
IdP-verified subjects. A verified record makes the state file version 9; nothing changes
for a deployment that leaves the flag off. Under the mode, both waiver transitions and
apply_change_setalso refuse a record whose owner was not verified at propose time, so a
change set proposed before the mode was on cannot skip it (#400).
Changed
- Every audit line gains
identity_mechanism(token,oauth,oidc-step-up,none), and an
approval's evidence record carriesmetadata.approver_mechanism(token/oidc, plus the
verified issuer and subject), via the newEvidenceRecorder::approval_with_identity. The
plainapprovalis unchanged (#400).
Documentation
docs/OAUTH.mdsection 9: Client ID Metadata Documents are the authorization server's
concern, what the resource server already provides for them, and what to configure at the
IdP. The OIDC human-identity spec's Phases 1-4 carry status notes (#400).