-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update JWS documentation to reflect mandatory use of certificates for embedding JWS public keys #110
Comments
@elnyry-sam-k to raise this with CCB and report back to DA at next available opportunity. |
CCB have agreed, FSPIOP SIG will be approached next. |
FSPIOP SIG is OK with the suggestion above. |
henrka
added a commit
to mojaloop/mojaloop-specification
that referenced
this issue
Sep 19, 2024
Change as per suggestion in mojaloop/design-authority-project#110. Bumped version of PKI Best Practices to 1.0.1. Not considered a breaking change in any way as it is a best practices document and the use of certificates is industry standard.
Update expected in v2.0 of docs site; coming soon. |
v2.0 update is pending ILPv4 change. Publishing expected in coming weeks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current documentation here: https://docs.mojaloop.io/api/fspiop/pki-best-practices.html#json-web-signature says that certificates should be used for handling JWS public keys. At the DA meeting on 2024-05-08 it was agreed by those present to update this wording thus:
The text was updated successfully, but these errors were encountered: