Skip to content

docs: v0.41.0 staleness sweep #468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
osanderson merged 1 commit into from
Sep 30, 2026
Merged

docs: v0.41.0 staleness sweep #468

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions GETTING_STARTED.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,6 +250,18 @@ read it back with `server.ParseInteractionHandle` when the form is
submitted, and protect that form with your usual CSRF defence. See
`server.InteractionHandle`'s doc comment.

**Keep the interaction until the form comes back.** The submission
needs `a.Interaction` again: the scope, the requested claims and any
authorization details the user is approving. Encode it with
`a.Interaction.MarshalText()` and keep it with the handle, somewhere only
your application can write: a server-side session, or a cookie you
sign. Restore it with `server.ParseInteractionRequest`. Then any
instance can handle the submission, not only the one that began the
authorization. A modified copy can't widen the grant, since
`CompleteAuthorization` checks it against the request the server
stored. `examples/federated-union` keeps both in a signed cookie
(`union/interaction_cookie.go`).

`cmd/conformance-as/authorize.go` is a complete, working version of
exactly this — read it for the full picture of the GET (render the
form) and POST (handle the submission) halves of a real HTTP flow. Its
Expand Down
4 changes: 3 additions & 1 deletion conformance/server/oidf-config/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -874,7 +874,9 @@ its own `conformance-as-client-auth-mtls-and-mtls` container
`expected-skips-client-auth-mtls-and-mtls.json` stay empty, matching
every other clean profile above.

## Client Credentials Grant (`{baseline,mtls,client-auth-mtls,client-auth-mtls-and-mtls}-client-credentials.config.json`)
## Client Credentials Grant

Configs: `{baseline,mtls,client-auth-mtls,client-auth-mtls-and-mtls}-client-credentials.config.json`.

`server.RequestClientCredentialsToken` (RFC 6749 §4.4) has no
PAR/authorize/redirect_uri/browser hop at all — a direct
Expand Down
3 changes: 2 additions & 1 deletion server/doc.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,8 @@
//
// The package exposes workflow methods — PushAuthorizationRequest,
// BeginAuthorization, CompleteAuthorization, ExchangeAuthorizationCode,
// RefreshAccessToken, the CIBA trio BeginBackchannelAuthentication,
// RefreshAccessToken, the CIBA methods BeginBackchannelAuthentication,
// LookupBackchannelInteraction (which reads a pending request back),
// CompleteBackchannelAuthentication and ExchangeBackchannelAuthentication,
// RequestClientCredentialsToken, SignUserInfoResponse, Metadata,
// PublicJWKS and (for OpenID Federation) EntityConfiguration — that
Expand Down
Loading