Repository navigation
Conversation
reinkrul
force-pushed
the
docs/rtd-move-policy
branch
from
November 5, 2026 08:55
c45fde1 to
9b2c7d4
Compare
reinkrul
marked this pull request as ready for review
November 5, 2026 09:30
reinkrul
requested review from
Dirklectisch,
JorisHeadease,
gerardsn,
stevenvegt and
woutslakhorst
as code owners
November 5, 2026 09:30
reinkrul
force-pushed
the
docs/rtd-move-policy
branch
from
November 6, 2026 11:25
9b2c7d4 to
ff2beb0
Compare
reinkrul
force-pushed
the
docs/rtd-move-policy
branch
from
November 6, 2026 13:07
f388e23 to
f88eb08
Compare
Assisted by AI
Assisted by AI
…e format Assisted by AI
reinkrul
force-pushed
the
docs/rtd-move-policy
branch
from
November 6, 2026 15:57
f88eb08 to
c019226
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the Read the Docs → wiki move (stacked on #4676).
After review,
deployment/policy.rstkeeps its content (it explains how the feature works, not how to use it in a use case). Changes:organization,service_provider,userandscope_policyfields (profile-only,passthrough,dynamic), and the load rules (at least one PD, PD validated against the PE v2 schema, scope defined once, one profile scope per request)service_providerandusermarked experimental (auth.experimental.jwtbearerclient;useronly in the OpenID4VP authorization code flow,auth.authorizationendpoint.enabled), both defaultfalseFixed: the page described a
presentation_definitionobject and awallet_owner_typefield, which don't exist; the scope holdsorganization,service_provideranduserdirectly (policy/local.go).scope_policywas not documented.Assisted by AI