Skip to content

Commit

Permalink
Update BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Ravi Prakash authored Dec 2, 2022
1 parent 9fb647a commit 76d3f63
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ X-Gateway-Authorization:Signature keyId="{subscriber_id}|{unique_key_id}|{algori
The KeyID is a string that uniquely identifies a subscriber's key(s) on the network. It has three components.

1. `subscriber_id`: It is by default the FQDN of the subscriber endpoint. However, for platforms that do not have an FQDN, a different identifier may be recommended by the network policy.
2. `unique_key_id` : It is an ID generated by the registry when an entry is created on the registry. The recommended format for `unique_key_id` is `uuid`.
2. `unique_key_id` : It is an ID generated by the registry when an entry for a subscriber is created in its database. The recommended format for `unique_key_id` is `uuid`.
3. `algorithm` : The signing algorithm used. Its value is same as the value in the `algorithm` attribute as per recommendations in [Signing HTTP Messages](https://tools.ietf.org/id/draft-cavage-http-signatures-12.html)

#### algorithm:
Expand Down

0 comments on commit 76d3f63

Please sign in to comment.