Binding: Difference between revisions
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
The process of requesting and receiving a signed packet which uses cryptographic means to bind one identifier (the [[Subject]]) to other identifiers, attributes behaviors or | The process of requesting and receiving a signed packet which uses cryptographic means to bind one identifier (the [[Subject]]) to other identifiers, attributes, behaviors or declarations. | ||
==Context== | ==Context== | ||
* The most well | * The most well known type of a binding protocol is the Credential Service Request for a [[X.509 Certificate]]. | ||
== Problems== | == Problems== | ||
| Line 13: | Line 13: | ||
==References== | ==References== | ||
* [[X.509 Certificate Policy For The Federal Bridge Certification Authority]] | * [[X.509 Certificate Policy For The Federal Bridge Certification Authority]] | ||
* [https://www.w3.org/2017/vc/WG/ W3C Verifiable Claims.] | |||
[[Category:Binding]] | [[Category:Binding]] | ||
Latest revision as of 19:41, 27 September 2019
Full Title or Meme
The process of requesting and receiving a signed packet which uses cryptographic means to bind one identifier (the Subject) to other identifiers, attributes, behaviors or declarations.
Context
- The most well known type of a binding protocol is the Credential Service Request for a X.509 Certificate.
Problems
Solutions
- Consent to Create Binding is a JSON message format that provides consent to a Credential Service Provider or similar digital endpoint to create a binding.
- Binding Packet is a JSON message format that contains a signed certificate that binds the Subject of the certificate to the other fields in the packet.