fix: align Markdown guidance and live interop reporting - #47
Merged
Conversation
- remove metadata frontmatter from regular Markdown files - enforce the repository Markdown convention - fail closed on unsupported live challenge requirements 📝 - Generated by Copilot
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.
This PR aligned regular Markdown files with the repository authoring convention
and made the external live interoperability sample distinguish complete draft-10
success from partial compatibility.
Changes
Live interoperability
Accept-Signatureas a structured-field dictionary containing therequired covered components
identity JSON before a live mode could pass
person-tokenresponse as an unsupported draft-10requirement without contacting the Person Server
interoperability was incomplete
missing claims, and valid responses
unsatisfied and did not mutate client state
Markdown authoring
files that require machine-readable metadata
where needed
Related Issues
None.
Validation
dotnet test AAuth.slnx: 2,906 passedlegacy
person-tokenrequirement; Mode 3 was skipped; exit code 2git diff --check: passedNotes
whoami.aauth.devcurrently returns the pre-draft-10person-tokenrequirementfor scoped access. The SDK did not add a compatibility fallback. Full external
Person Server authorization will become testable when the resource emits
requirement=auth-tokenwith a validresource-tokenparameter.