Jakub Zych 90752beb87 feat(08-03): implement exact authorize validation and pending creation in wristband ...

- Server.Authorize ports OAuthAuthorizeController::authorize's exact
  validation order: usable client, exact redirect, response_type=code,
  code_challenge_method=S256, challenge length, scope parsing/ceiling
  truncation, resource check, then opaque pending-request creation
- Unknown client/unregistered redirect are local text/plain 400s with no
  Location; every later failure is an ordered RFC3986 redirect with
  error/error_description/iss[/state], built via a dedicated encoder
  (never url.Values.Encode, which sorts keys and space-encodes as '+')
- Options gains Resource and PendingRequestTTL (both PHP-parity defaults)
  so authorize's resource check and 600s pending expiry are configurable

2026-09-23 20:08:37 +02:00

..

authorize_test.go

feat(08-03): implement exact authorize validation and pending creation in wristband

2026-09-23 20:08:37 +02:00

authorize.go

feat(08-03): implement exact authorize validation and pending creation in wristband

2026-09-23 20:08:37 +02:00

crypto.go

test(08-02): add failing RFC 7591 registration RED test in wristband

2026-09-23 19:37:03 +02:00

register.go

feat(08-02): implement exact RFC 7591 registration in wristband

2026-09-23 19:37:54 +02:00

registration_test.go

test(08-02): add failing RFC 7591 registration RED test in wristband

2026-09-23 19:37:03 +02:00

server_test.go

feat(08-01): implement exact RFC 8414 metadata writer in wristband

2026-09-23 19:10:26 +02:00

server.go

feat(08-03): implement exact authorize validation and pending creation in wristband

2026-09-23 20:08:37 +02:00

stores.go

test(08-02): add failing RFC 7591 registration RED test in wristband

2026-09-23 19:37:03 +02:00