From b93fa7048a7bdc30bd5204cf42900ee23922b2c7 Mon Sep 17 00:00:00 2001 From: Denis Kirillov Date: Thu, 3 Jun 2021 15:18:27 +0300 Subject: [PATCH] [#53] Fixed bearer cookie key in README.md Signed-off-by: Denis Kirillov --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ccbba33..3534306 100644 --- a/README.md +++ b/README.md @@ -355,7 +355,7 @@ NeoFS Bearer Token basically is a container owner-signed ACL data (refer to NeoF documentation for more details). There are two options to pass them to gateway: * "Authorization" header with "Bearer" type and base64-encoded token in credentials field - * "__context_bearer_token_key" cookie with base64-encoded token contents + * "Bearer" cookie with base64-encoded token contents For example you have a mobile application frontend with a backend part storing data in NeoFS. When user authorizes in mobile app, the backend issues a NeoFS