Repository navigation
Rebuild the PQC migration use case around Keycloak - #52
Merged
Merged
Conversation
The use case described a hypothetical product while the worked example used Keycloak 26.7.3, so the two read as unrelated. The page now carries Keycloak throughout: its thirteen interfaces and how they layer, the baseline and extended profiles as two depths of one family (draft decision 0022), Keycloak's values under each, what a planner concludes, how the example is expressed in CycloneDX, and the four example documents. The method sections, the availability argument and the exclusions are kept. The use-case index row is updated to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MnJLrvXEqZUu5D2YTZQGfo
3 tasks
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.
Carries the Keycloak 26.7.3 example through the PQC migration use case: its interfaces and layering, the baseline and extended profiles (draft decision 0022), what a planner concludes, and the CycloneDX encoding. The rules files and example documents follow in a separate PR.