From c359066f57e3748e976270818d5b6155b235a79c Mon Sep 17 00:00:00 2001 From: Jonas Wanke Date: Thu, 23 May 2024 19:52:09 +0200 Subject: [PATCH] Add bearer token example --- docs/s3-api-docs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/s3-api-docs.md b/docs/s3-api-docs.md index 080912c..85b551f 100644 --- a/docs/s3-api-docs.md +++ b/docs/s3-api-docs.md @@ -45,7 +45,7 @@ curl --location --request POST 'http://api-url/posts' \ ## Authentication -The API uses a simple authentication mechanism. The user must provide a valid username to access the API. The username is sent as a JSON object in the request body. The API will respond with a JSON Web Token (JWT) that must be included in the `Authorization` header of all subsequent requests using the `Bearer` scheme. Additionally, the API will respond with the user's ID, which is required to access the authenticated user's profile. +The API uses a simple authentication mechanism. The user must provide a valid username to access the API. The username is sent as a JSON object in the request body. The API will respond with a JSON Web Token (JWT) that must be included in the `Authorization` header of all subsequent requests using the `Bearer` scheme (`Authorization: Bearer `, e.g., `Authorization: Bearer ey…`). Additionally, the API will respond with the user's ID, which is required to access the authenticated user's profile.
View details