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.

Sign up for GitHub

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

Jump to bottom

Epic: making did:x509-backed credential feature production-ready #3582

Open

6 tasks

reinkrul opened this issue Nov 29, 2024 · 0 comments

Open

6 tasks

Epic: making did:x509-backed credential feature production-ready #3582

reinkrul opened this issue Nov 29, 2024 · 0 comments

Member

reinkrul commented Nov 29, 2024 •

edited

Loading

TODOs:

Write RFC
Docs: TLS truststore configuration is relevant for did:x509, but docs state it's only relevant for did:nuts/gRPC
This makes it hard to find.
Check if all documentation is up-to-date, given the latest insights
- https://nuts-node.readthedocs.io/en/latest/pages/deployment/certificates.html#did-x509

Things up for discussion:

@stevenvegt's remark regarding credential subject structure: Change credentials to did:x509-backed credentials Zorgbijjou/scp-homemonitoring#7 (comment)
How are parties going to issue their UZI server certificate? This highly depends on the environment, e.g.: tool that connects to a key vault, or uses an on-disk private key. A locally run CLI tool, or a container that you can start, issues the certificate and loads it into the Nuts node, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment