From 76d3f63b6b2ad116d37b1341fa86e0590576dc18 Mon Sep 17 00:00:00 2001 From: Ravi Prakash Date: Fri, 2 Dec 2022 16:09:28 +0530 Subject: [PATCH] Update BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md --- docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md b/docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md index 8cddff7c..0e93d554 100644 --- a/docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md +++ b/docs/BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md @@ -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: