Repository navigation
FAPI-CIBA: inherit TLS and algorithm requirements - #867
Open
davetonge-mh wants to merge 3 commits into
Open
davetonge-mh wants to merge 3 commits into
davetonge-mh wants to merge 3 commits into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Sep 16, 2026
FAPI-CIBA shall be inheriting these sections from a chosen security profile (FAPI 1 or FAPI 2)?
#675
Open
davetonge-mh
commented
Sep 16, 2026
The section covers both the old TLS text and the JWS/JWE algorithm text, so the heading should say so. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
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.
CIBA should not duplicate TLS and algorithm requirements — follow whichever FAPI security profile you are using.
Closes #675