forked from TrueCloudLab/frostfs-http-gw
[#53] Fixed bearer cookie key in README.md
Signed-off-by: Denis Kirillov <denis@nspcc.ru>
This commit is contained in:
parent
b2cd6d8862
commit
b93fa7048a
1 changed files with 1 additions and 1 deletions
|
@ -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:
|
documentation for more details). There are two options to pass them to gateway:
|
||||||
* "Authorization" header with "Bearer" type and base64-encoded token in
|
* "Authorization" header with "Bearer" type and base64-encoded token in
|
||||||
credentials field
|
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
|
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
|
data in NeoFS. When user authorizes in mobile app, the backend issues a NeoFS
|
||||||
|
|
Loading…
Reference in a new issue