-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAPI2 profile support #317
Conversation
81c7234
to
25740e9
Compare
Pull Request Test Coverage Report for Build 132
💛 - Coveralls |
25740e9
to
c05c8d0
Compare
c05c8d0
to
39aa09e
Compare
That would probably be good. FAPI1 also has very different requirements between the specs. |
@paulswartz mTLS should be relatively simple to handle: The user can already supply So we can just verify that they either are set, |
After this minor correction good for merge. |
@paulswartz Can you open issues for all the TODOs that are missing for full compliance? (Like JARM and mTLS) |
Co-authored-by: Jonatan Männchen <jonatan@maennchen.ch>
@paulswartz Can you run |
Ref: #316
Open Questions
fapi2_security_profile
andfapi2_message_signing
? The latter seems to also require request objects and JARM (even if the conformance suite doesn't seem to).TODO