Skip to main content

Use Basic Auth to Protect Your APIs

Estimated reading time: 0 min read

You may want to protect your APIs or Applications by using API authentication. With the authentication requirement, API7 Cloud will only forward API requests with valid authentication credentials. Other requests (without credentials or with a wrong one) will be rejected and get a 401 Unauthorized response.

Basic Auth is an API authentication method that asks the API clients to provide a valid username and password pair.

This guide will introduce using Basic Auth to protect your APIs when using API7 Cloud. You can also safeguard Applications as long as you configure the application's authentication policy (instead of a specific API).


API7 Cloud uses the Consumer concept to implement fine-grained API authentication, so please learn what is Consumer before you go ahead.

Prepare the Environment

Deploy Apache APISIX

Please refer to How to Deploy Apache APISIX to learn how to deploy Apache APISIX and connect it to API7 Cloud. In this guide, we'll deploy an Apache APISIX instance on Docker.

Create Application and API

We'll create an Application with the following details in this guide.

  1. The Application name is basic-auth-app.
  2. The path prefix is /v1.
  3. The HTTP Host is
  4. The upstream URL is

Besides, we'll create an API inside the basic-auth-app Application.

  1. The API name is json.
  2. The path is /json (exact match).
  3. Accepted HTTP method is GET.

If you don't know how to configure an Application and API, please refer to the Getting Started guides first

Configure Authentication Policy on the API

You need to enable the Authentication policy on the json API as per the steps below:

  1. Enter the json API details page.
  2. Click on Add Policy and select the Authentication policy.
  3. Choose Basic Auth as the authentication method and fill out the form.

Authentication Policy Basic Auth


The checkbox StripCredentials controls if Apache APISIX should remove the authentication credentials before forwarding the requests to the backend. By default, it will be reserved.

Now let's try to access this API.

curl -H 'Host:' -i
HTTP/1.1 401 Unauthorized
Date: Thu, 09 Jun 2022 01:37:17 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
WWW-Authenticate: Basic realm='.'
Server: APISIX/2.13.1

{"message":"Missing authorization in request"}

Since we don't take any credentials, Apache APISIX will reject the request.

Configure Basic Auth Policy on Consumer

Now let's create a Consumer and enable the Authentication policy.

  1. The Consumer's name is alex.
  2. Enable the Authentication policy and choose Basic Auth as the authentication method.
  3. Fill in alex as the username and 123456 as the password.

Use the strong password in actual cases.

Test the Authentication

Let's send a request with the username and password.

curl -H 'Host:' -i -u alex:123456
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 429
Connection: keep-alive
Date: Mon, 13 Jun 2022 07:28:33 GMT
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Server: APISIX/2.13.1

"slideshow": {
"author": "Yours Truly",
"date": "date of publication",
"slides": [
"title": "Wake up to WonderWidgets!",
"type": "all"
"items": [
"Why <em>WonderWidgets</em> are great",
"Who <em>buys</em> WonderWidgets"
"title": "Overview",
"type": "all"
"title": "Sample Slide Show"

After taking the correct username and password, Apache APISIX will forward the request to the backend.

If we take the wrong username and password pair, the API request will also be rejected by Apache APISIX.

curl -H 'Host:' -i -u wrong-user:wrong-password
HTTP/1.1 401 Unauthorized
Date: Mon, 13 Jun 2022 07:36:47 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Server: APISIX/2.13.1

{"message":"Invalid user key in authorization"}
curl -H 'Host:' -i -u alex:wrong-password
HTTP/1.1 401 Unauthorized
Date: Mon, 13 Jun 2022 07:36:28 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Server: APISIX/2.13.1

{"message":"Password is error"}

What's Next