Protect your Function with Basic Auth
Warning
This example uses headers and cookies, which are only accessible when your Function is running @twilio/runtime-handler
version 1.2.0
or later. Consult the Runtime Handler guide to learn more about the latest version and how to update.
When protecting your public Functions, and any sensitive data that they can expose, from unwanted requests and bad actors, it is important to consider some form of authentication to validate that only intended users are making requests. In this example, we'll be covering one of the most common forms of authentication: Basic Authentication.
If you want to learn an alternative approach, you can also see this example of using JWT for authentication.
Let's create a Function that will only accept requests with valid Basic Authentication, and reject all other traffic.
In order to run any of the following examples, you will first need to create a Function into which you can paste the example code. You can create a Function using the Twilio Console or the Serverless Toolkit as explained below:
If you prefer a UI-driven approach, creating and deploying a Function can be done entirely using the Twilio Console and the following steps:
- Log in to the Twilio Console and navigate to the Functions tab. If you need an account, you can sign up for a free Twilio account here!
- Functions are contained within Services. Create a Service by clicking the Create Service button and providing a name such as test-function.
- Once you've been redirected to the new Service, click the Add + button and select Add Function from the dropdown.
- This will create a new Protected Function for you with the option to rename it. The name of the file will be path it is accessed from.
- Copy any one of the example code snippets from this page that you want to experiment with, and paste the code into your newly created Function. You can quickly switch examples by using the dropdown menu of the code rail.
- Click Save to save your Function's contents.
- Click Deploy All to build and deploy the Function. After a short delay, your Function will be accessible from:
https://<service-name>-<random-characters>-<optional-domain-suffix>.twil.io/<function-path>
For example:test-function-3548.twil.io/hello-world
.
Your Function is now ready to be invoked by HTTP requests, set as the webhook of a Twilio phone number, invoked by a Twilio Studio Run Function Widget, and more!
First, create a new auth
Service and add a Public /basic
Function using the directions above.
Delete the default contents of the Function, and paste in the code snippet provided above.
Save the Function once it contains the new code.
Info
Remember to change the visibility of your new Function to be Public. By default, the Console UI will create new Functions as Protected, which will prevent access to your Function except by Twilio requests.
Next, deploy the Function by clicking on Deploy All in the Console UI.
We can check that authentication is working first by sending an unauthenticated request to our deployed Function. You can get the URL of your Function by clicking the Copy URL button next to the Function.
Then, using your client of choice, make a GET
or POST
request to your Function. It should return a 401 Unauthorized
since the request contains no valid Authorization header.
curl -i -L -X POST 'https://auth-4173-dev.twil.io/basic'
Result:
1$ curl -i -L -X POST 'https://auth-4173-dev.twil.io/basic'23HTTP/2 4014date: Tue, 03 Aug 2021 21:55:02 GMT5content-type: application/octet-stream6content-length: 127www-authenticate: Basic realm="Authentication Required"8x-shenanigans: none910Unauthorized
Great! Requests are successfully being blocked from non-authenticated requests.
To make an authenticated request and get back a 200 OK
, we'll need to generate and send a request with the example username and password encoded as the Authorization header credentials. Leverage one of the following methods to encode your Credentials:
First, open your browser's developer tools. Navigate to the Console tab, where you'll be able to execute the following JavaScript in the browser to generate your encoded credentials:
btoa("<username>:<password>");
The btoa method is a built-in browser method for conveniently converting a string to base64 encoding.
For example, with our example credentials, you would input the following into the browser console and get this result:
1btoa("twilio:ahoy!")2> "dHdpbGlvOmFob3kh"
Now that you have your encoded credentials, it's time to make an authenticated request to your Function by including them in the Authentication header.
Using cURL with our example credentials would look like this:
1curl -i -L -X POST 'https://auth-4173-dev.twil.io/basic' \2-H 'Authorization: Basic dHdpbGlvOmFob3kh'3
and the response would be:
1$ curl -i -L -X POST 'https://auth-4173-dev.twil.io/basic' \2-H 'Authorization: Basic dHdpbGlvOmFob3kh'34HTTP/2 2005date: Tue, 03 Aug 2021 22:15:37 GMT6content-type: text/plain; charset=utf87content-length: 28x-shenanigans: none9x-content-type-options: nosniff10x-xss-protection: 1; mode=block1112OK
At this point, Basic Authentication is now working for your Function!
To make this example your own, you could experiment with:
- Instead of defining the username and password directly in your Function's code, define other secure values and store them securely as Environment Variables. You could then access them using
context.USERNAME
andcontext.PASSWORD
respectively, for example. - Take things a bit further and establish a database of authenticated users with hashed passwords. Once you've retrieved the decoded username and password from the Authorization header, perform a lookup of the user by username and validate their password using a library such as bcrypt. Your hashing secret can be a secure Environment Variable.