diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 53bdb3f696..5b2a8df629 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -161,7 +161,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/ A container's privacy policy defines whether a container may be invoked anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**). -### JWT Token +### JWT Token (legacy) JWT (JSON Web Token) is an access token you can create to enable an application to access your `private` container. [Find out how to restrict access to a container](/serverless-containers/how-to/secure-a-container/#restrict-access-to-your-containers). diff --git a/pages/serverless-containers/how-to/test-a-container.mdx b/pages/serverless-containers/how-to/test-a-container.mdx index dfce1d4bd1..14609f3c9d 100644 --- a/pages/serverless-containers/how-to/test-a-container.mdx +++ b/pages/serverless-containers/how-to/test-a-container.mdx @@ -35,9 +35,9 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons 7. Click **+ Advanced options** to add any required HTTP header or parameter to your container. -8. Click **Run**. +8. Copy the generated command, then execute it in a terminal. -The **Output** section displays the response from your container and the status code. +The output of your terminal displays the response from your container, and the status code. If you encounter a message error while testing your container, refer to the [dedicated troubleshooting](/serverless-containers/troubleshooting/tests-fail-on-container/) for more information. diff --git a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx index d1d8f022b3..9d36f25b66 100644 --- a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx +++ b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx @@ -13,7 +13,7 @@ I get error messages when testing Serverless Containers using the Scaleway Conso ## Cause -Testing **Private** Serverless Containers is not possible using the Scaleway console due to CORS limitations. +**Private** Serverless Containers require you use an authentication token. ## Possible solutions diff --git a/pages/serverless-functions/how-to/test-a-function.mdx b/pages/serverless-functions/how-to/test-a-function.mdx index b32de54a0c..756d2615dd 100644 --- a/pages/serverless-functions/how-to/test-a-function.mdx +++ b/pages/serverless-functions/how-to/test-a-function.mdx @@ -35,7 +35,9 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons 7. Click **+ Advanced options** to add any required HTTP header or parameter to your function. -8. Click **Run**. +8. Copy the generated command, then execute it in a terminal. + +The output of your terminal displays the response from your function, and the status code. The **Output** section displays the response from your function and the status code. diff --git a/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx b/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx index 7b4f5c5382..0154a29dce 100644 --- a/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx +++ b/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx @@ -13,7 +13,7 @@ I get error messages when testing Serverless Functions using the Scaleway Consol ## Cause -Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. +**Private** Serverless Functions require you use an authentication token. ## Possible solutions