Version: 3.10

Consumer

Description#

For an API gateway, it is usually possible to identify the type of the requester by using things like their request domain name and client IP address. A gateway like APISIX can then filter these requests using Plugins and forward it to the specified Upstream.

It has the highest priority: Consumer > Route > Plugin Config > Service.

But this level of depth can be insufficient on some occasions.

An API gateway should know who the consumer of the API is to configure different rules for different consumers. This is where the Consumer construct comes in APISIX.

Configuration options#

The fields for defining a Consumer are defined as below.

Field	Required	Description
`username`	True	Name of the consumer.
`plugins`	False	Plugin configuration of the Consumer. For specific Plugin configurations, please refer the Plugins.

Identifying a Consumer#

The process of identifying a Consumer in APISIX is described below:

The first step is Authentication. This is achieved by Authentication Plugins like key-auth and JWT.
After authenticating, you can obtain the id of the Consumer. This id will be the unique identifier of a Consumer.
The configurations like Plugins and Upstream bound to the Consumer are then executed.

Consumers are useful when you have different consumers requesting the same API and you need to execute different Plugin and Upstream configurations based on the consumer. These need to be used in conjunction with the user authentication system.

Authentication plugins that can be configured with a Consumer include basic-auth, hmac-auth, jwt-auth, key-auth, ldap-auth, and wolf-rbac.

Refer to the documentation for the key-auth authentication Plugin to further understand the concept of a Consumer.

note

For more information about the Consumer object, you can refer to the Admin API Consumer object resource introduction.

Example#

The example below shows how you can enable a Plugin for a specific Consumer.

note

You can fetch the admin_key from config.yaml and save to an environment variable with the following command:

admin_key=$(yq '.deployment.admin.admin_key[0].key' conf/config.yaml | sed 's/"//g')

Create a Consumer, specify the authentication plugin key-auth, and enable the specific plugin limit-count.

curl http://127.0.0.1:9180/apisix/admin/consumers \
-H "X-API-KEY: $admin_key" -X PUT -d '
{
    "username": "jack",
    "plugins": {
        "key-auth": {
            "key": "auth-one"
        },
        "limit-count": {
            "count": 2,
            "time_window": 60,
            "rejected_code": 503,
            "key": "remote_addr"
        }
    }
}'

Create a Router, set routing rules and enable plugin configuration.

curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H "X-API-KEY: $admin_key" -X PUT -d '
{
    "plugins": {
        "key-auth": {}
    },
    "upstream": {
        "nodes": {
            "127.0.0.1:1980": 1
        },
        "type": "roundrobin"
    },
    "uri": "/hello"
}'

Send a test request, the first two return to normal, did not reach the speed limit threshold.
```
curl http://127.0.0.1:9080/hello -H 'apikey: auth-one' -I
```
The third test returns 503 and the request is restricted.
```
HTTP/1.1 503 Service Temporarily Unavailable
...
```

We can use the consumer-restriction Plugin to restrict our user "Jack" from accessing the API.

Add Jack to the blacklist.

curl http://127.0.0.1:9180/apisix/admin/routes/1 \
-H "X-API-KEY: $admin_key" -X PUT -d '
{
    "plugins": {
        "key-auth": {},
        "consumer-restriction": {
            "blacklist": [
                "jack"
            ]
        }
    },
    "upstream": {
        "nodes": {
            "127.0.0.1:1980": 1
        },
        "type": "roundrobin"
    },
    "uri": "/hello"
}'

Repeated tests, all return 403; Jack is forbidden to access this API.

curl http://127.0.0.1:9080/hello -H 'apikey: auth-one' -I

HTTP/1.1 403
...