Question

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

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?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer