Key Authentication

An API gateway's primary role is to connect API consumers and providers. For security reasons, it should authenticate and authorize consumers before allowing them to access upstream resources.

APISIX has a flexible plugin extension system and a number of existing plugins for user authentication and authorization. For example:

• Key Authentication
• Basic Authentication
• HMAC
• JSON Web Token (JWT) Authentication
• OpenID Connect
• Keycloak Authorization
• Casdoor Authorization
• Casbin Authorization
• Open Policy Agent (OPA)
• Wolf RBAC
• Central Authentication Service (CAS)
• LDAP
• Forward Authentication

In this tutorial, you will create a consumer, configure its credential with key authentication, and learn how to enable and disable key authentication.

Key Concepts

Consumer

A consumer is an application or a developer who consumes the API.

In APISIX, a consumer requires a unique username to be created. As part of the key authentication configuration, you would also add one of the authentication plugins from the list above to the consumer's plugin field.

Key Authentication

Key authentication is a relatively simple but widely used authentication approach. The idea is as follows:

1. Administrator adds an authentication plugin to the route.
2. API consumers attach the key to the query string or headers for authentication when sending requests.

Prerequisite(s)

1. Complete Get APISIX to install APISIX in Docker or on Kubernetes.
2. Complete Configure Routes.

Start a Sample Upstream Service

If you are running APISIX in Kubernetes, you will be deploying an httpbin application to your cluster in this section. Otherwise, skip to the next section where you will be using the hosted httpbin application as the upstream.

Start a sample httpbin application:

kubectl run httpbin --image kennethreitz/httpbin --port 80

You should see a pod/httpbin created response.

Expose the application's port 80 through a service:

kubectl expose pod httpbin --port 80

You should see a service/httpbin exposed response.

Configure Key Authentication

Admin API

Create a Consumer

Create a consumer tom:

caution

Please use a complex key in the production environment.

curl -i "http://127.0.0.1:9180/apisix/admin/consumers" -X PUT -d '
{
  "username": "tom"
}'

You will receive an HTTP/1.1 201 Created response if the consumer was created successfully.

Configure Consumer Credential

Configure the consumer key-auth credential for tom:

curl "http://127.0.0.1:9180/apisix/admin/consumers/tom/credentials" -X PUT -d '
{
  "id": "cred-tom-key-auth",
  "plugins": {
    "key-auth": {
      "key": "secret-key"
    }
  }
}'

You will receive an HTTP/1.1 201 Created response if the consumer credential was created created.

Enable Authentication

Update the getting-started-ip route from Configure Routes to add the key-auth plugin:

curl -i "http://127.0.0.1:9180/apisix/admin/routes/getting-started-ip" -X PATCH -d '
{
  "plugins": {
    "key-auth": {}
  }
}'

You will receive an HTTP/1.1 200 OK response if the route was updated successfully.

ADC

Create an ADC configuration file containing a consumer and a route:

adc.yaml

consumers:
  - username: tom
    plugins:
      key-auth:
        key: secret-key
services:
  - name: httpbin Service
    routes:
      - uris:
          - /ip
        name: getting-started-ip
        plugins:
          key-auth: {}
    upstream:
      type: roundrobin
      nodes:
        - host: httpbin.org
          port: 80
          weight: 1

Synchronize the configuration to APISIX:

adc sync -f adc.yaml

Ingress Controller

Create a Kubernetes manifest file to configure a consumer using the ApisixConsumer custom resource:

consumer.yaml

apiVersion: apisix.apache.org/v2
kind: ApisixConsumer
metadata:
  name: tom
  namespace: ingress-apisix
spec:
  authParameter:
    keyAuth:
      value:
        key: "secret-key"

Create another manifest file for a route, where key authentication is enabled:

httpbin-route.yaml

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: httpbin-route
  namespace: ingress-apisix
spec:
  http:
    - name: httpbin-route
      match:
        paths:
          - /ip
      backends:
        - serviceName: httpbin
          servicePort: 80
      authentication:
        enable: true
        type: keyAuth

Apply the configurations to your cluster:

kubectl apply -f httpbin-route.yaml -f consumer.yaml

You should see the following responses:

apisixconsumer.apisix.apache.org/tom created
apisixroute.apisix.apache.org/httpbin-route created

Verify

You will be verifying if the key authentication is successfully enabled in this section.

Send a Request without Any Key

Send a request without the apikey header.

curl -i "http://127.0.0.1:9080/ip"

Since the key is not provided, you will receive an unauthorized HTTP/1.1 401 Unauthorized response.

Send a Request with a Wrong Key

Send a request with a wrong key in the apikey header.

curl -i "http://127.0.0.1:9080/ip" -H 'apikey: wrong-key'

Since the key is incorrect, you will receive an HTTP/1.1 401 Unauthorized response.

Send a Request with the Correct Key

Send a request with the correct key in the apikey header.

curl -i "http://127.0.0.1:9080/ip" -H 'apikey: secret-key'

Since the correct key is provided, you will receive an HTTP/1.1 200 OK response.

Disable Authentication

Disable the key authentication plugin by setting the _meta.disable parameter to true.

Admin API

curl "http://127.0.0.1:9180/apisix/admin/routes/getting-started-ip" -X PATCH -d '
{
  "plugins": {
    "key-auth": {
      "_meta": {
        "disable": true
      }
    }
  }
}'

ADC

adc.yaml

consumers:
  - username: tom
    plugins:
      key-auth:
        key: secret-key
services:
  - name: httpbin Service
    routes:
      - uris:
          - /ip
        name: getting-started-ip
        plugins:
          key-auth:
            _meta:
              disable: true
    upstream:
      type: roundrobin
      nodes:
        - host: httpbin.org
          port: 80
          weight: 1

Synchronize the configuration to APISIX:

adc sync -f adc.yaml

Ingress Controller

Update the route configuration file as such:

httpbin-route.yaml

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: httpbin-route
  namespace: ingress-apisix
spec:
  http:
    - name: httpbin-route
      match:
        paths:
          - /ip
      backends:
        - serviceName: httpbin
          servicePort: 80
      authentication:
        enable: false
        type: keyAuth

Apply the configuration to your cluster:

kubectl apply -f httpbin-route.yaml

You should see the following response:

apisixroute.apisix.apache.org/httpbin-route configured

Send a request without any key to verify:

curl -i "http://127.0.0.1:9080/ip"

Since key authentication is disabled, you will receive an HTTP/1.1 200 OK response.

What's Next

You have learned how to configure key authentication for a route. In the next tutorial, you will learn how to configure rate limiting.