Report this

What is the reason for this report?

Should docs for Secure Web Functions use X-Require-Whisk-Auth header?

Posted on October 9, 2022

I want to activate the Secure Web Function feature on serverless functions. In the Functions docs it says to use the header X-Function-Auth and this is also what it says on my function’s settings page.

To require authentication, enable Secure Web Function. This prompts you to enter a secret token, which you will then need to provide in the X-Function-Auth header for each request

However I get a 401 response when I use this header. Instead, the example curl command uses the header X-Require-Whisk-Auth and using this header gives me access to my function.

Should the docs be updated to reflect that X-Require-Whisk-Auth is the correct header?

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.