RPF-WP-0054: key-cape confirms the client secret format; T01 and T03 done
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 469992@bnt-lap001 Assistant-Session: e4b8e420-df0a-441d-83ae-7f19130594d9
This commit is contained in:
parent
b96b86753c
commit
7ee2fa5a1b
2 changed files with 15 additions and 4 deletions
|
|
@ -61,8 +61,8 @@ CASE_TYPE = 'oidc-browser-relying-party@1.0'
|
|||
# oidc-browser-relying-party@1.0 parameter client_id.
|
||||
CLIENT_ID_RE = re.compile(r'^[a-z0-9][a-z0-9-]{1,62}$')
|
||||
CASE_REF_RE = re.compile(r'^[a-z0-9][a-z0-9-]*@sha256:[0-9a-f]{64}$')
|
||||
# Proposed 48 random bytes -> 64 URL-safe characters; key-cape confirmation
|
||||
# pending (RPF-WP-0054-T01).
|
||||
# 48 random bytes -> 64 URL-safe characters, confirmed by key-cape 2026-10-10
|
||||
# (message 4e0213b3; opaque constant-time comparison, no alphabet limit).
|
||||
SECRET_BYTES = 48
|
||||
TOKEN_TTL = '5m'
|
||||
SCHEMA = 'platform.keycape-client-secret-generate.v1'
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue