From 8f63cc82e6f22308c7ed48f3cd2120d466a1dd6f Mon Sep 17 00:00:00 2001 From: Michael Feldstein Date: Thu, 15 Aug 2019 14:36:29 -0700 Subject: [PATCH] [SEP6] Clarify jwt usage (#376) Clarify that jwt should always be in a header, and the only use case for query params should be in the case of the interactive webapp. --- ecosystem/sep-0006.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ecosystem/sep-0006.md b/ecosystem/sep-0006.md index 2ce158c6f..9f37e842b 100644 --- a/ecosystem/sep-0006.md +++ b/ecosystem/sep-0006.md @@ -54,7 +54,7 @@ The JWT should be included in all requests as request header: Authorization: Bearer ``` -Alternatively, if the client cannot add the authorization header. The JWT should be passed as a jwt query parameter: +In the case of the [interactive webapp](#customer-information-needed-interactive), since the client cannot add the authorization header, The JWT should be passed as a jwt query parameter: ``` ?jwt= ```