Skip to content

Fix/disallow confidential client implicit flow - Global switch - #362

Draft
ioigoume wants to merge 3 commits into
simplesamlphp:version-6from
ioigoume:fix/disallow-confidential-client-implicit-flow
Draft

ioigoume wants to merge 3 commits into
simplesamlphp:version-6from
ioigoume:fix/disallow-confidential-client-implicit-flow

Conversation

@ioigoume

@ioigoume ioigoume commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

On v6, this flag is the only way to stop confidential clients from using the implicit flow, because v6 has no per-client response_types or grant_types. v6 also has no Dynamic Client Registration, so the flag covers admin-created and federated clients. On v7, the flag adds to the existing controls (per-client response_types/grant_types and server-wide enabled_grant_types) rather than replacing them. Its main use there is as one server-wide switch for clients whose response_types are still empty: clients migrated from v6, or clients that registered themselves through DCR (off by default). A possible v7 follow-up: when the flag is on, DCR could reject confidential clients that ask for implicit response types, returning invalid_client_metadata, so registration and runtime behave the same.

@ioigoume
ioigoume marked this pull request as draft October 21, 2026 07:24
@ioigoume ioigoume changed the title Fix/disallow confidential client implicit flow Fix/disallow confidential client implicit flow - Global switch Oct 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant