Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions schema/OpenTDF/assertion_binding.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,13 @@ The `binding` object, nested within an [Assertion Object](./assertion.md), conta
```json
"binding": {
"method": "jws",
"signature": "eyJhbGciOiJSUzI1NiJ9..." // Base64URL encoded JWS string
"signature": "eyJhbGciOiJSUzI1NiJ9..." // JWS string
}
```

## Fields

| Parameter | Type | Description | Required? |
| --------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| method | String | The cryptographic method used for the signature. jws (JSON Web Signature) is commonly used, implying standard JWS processing rules apply. | Yes |
| signature | String | The Base64URL encoded signature value (e.g., a JWS Compact Serialization string). The signature calculation MUST include the assertion content and sufficient TDF context (like policy or key info hash) to prevent replay. | Yes |
| method | String | Cryptographic binding format. The only supported value is `"jws"` (JSON Web Signature using JWS Compact Serialization as per RFC 7515). | Yes |
| signature | String | JWS compact serialization string binding the assertion to the `scope` target (`tdo` or `payload`), providing integrity and replay protection. | Yes |