draft: introduce distribute-only-peer #22
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.
A Distribute-Only-Peer is a Peer who will only send requests but is unable to receive them.
This Peer is introduced for the usecase of organizations who will want to participate as Delegator
but are missing the IT knowledge to deploy an entire FSC setup.
By adding a Peer that will only send requests new implementation possibilities are created.
For example a mobile app for signing contracts.
This is a breaking change because Peers will have to send the entire certificate when
signing Contracts instead of only the certificate thumbprint.
This is needed because Distribute-Only-Peers are unable to provide key material through a JWKS endpoint.