Skip to content
|
search
Plugin Hub
header icon

Upstream HTTP Basic Authentication

Kong Plugin to add HTTP Basic Authentication to the upstream request header.

Installation

  1. The LuaRocks package manager must be Installed.
  2. Kong must be Installed and you must be familiar with using and configuring Kong.
  3. Install the module kong-plugin-upstream-auth-basic. 
    luarocks install kong-plugin-upstream-auth-basic
  4. Add the custom plugin to the kong.conf file (e.g. /etc/kong/kong.conf) 
    custom_plugins = ...,upstream-auth-basic
  5. Restart kong

Configuration Reference

This plugin is compatible with DB-less mode.

Example plugin configuration

The following examples provide some typical configurations for enabling the upstream-auth-basic plugin on a service.

Make the following request:

curl -X POST http://localhost:8001/services/SERVICE_NAME|SERVICE_ID/plugins \
    --data "name=upstream-auth-basic"  \
    --data "config.username=kingkong" \
    --data "config.password=1-big-ape"

Replace SERVICE_NAME|SERVICE_ID with the id or name of the service that this plugin configuration will target.

First, create a KongPlugin resource:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: upstream-auth-basic-example
config: 
  username: kingkong
  password: 1-big-ape
plugin: upstream-auth-basic

Next, apply the KongPlugin resource to a service by annotating the service as follows:

apiVersion: v1
kind: Service
metadata:
  name: SERVICE_NAME|SERVICE_ID
  labels:
    app: SERVICE_NAME|SERVICE_ID
  annotations:
    konghq.com/plugins: upstream-auth-basic-example
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
    name: SERVICE_NAME|SERVICE_ID
  selector:
    app: SERVICE_NAME|SERVICE_ID

Replace SERVICE_NAME|SERVICE_ID with the id or name of the service that this plugin configuration will target.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: upstream-auth-basic
  service: SERVICE_NAME|SERVICE_ID
  config: 
    username: kingkong
    password: 1-big-ape

Replace SERVICE_NAME|SERVICE_ID with the id or name of the service that this plugin configuration will target.

The following examples provide some typical configurations for enabling the upstream-auth-basic plugin on a route.

Make the following request:

curl -X POST http://localhost:8001/routes/ROUTE_NAME|ROUTE_ID/plugins \
  --data "name=upstream-auth-basic"  \
    --data "config.username=kingkong" \
    --data "config.password=1-big-ape"

Replace ROUTE_NAME|ROUTE_ID with the id or name of the route that this plugin configuration will target.

First, create a KongPlugin resource:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: upstream-auth-basic-example
config: 
  username: kingkong
  password: 1-big-ape
plugin: upstream-auth-basic

Then, apply it to an ingress (route or routes) by annotating the ingress as follows:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ROUTE_NAME|ROUTE_ID
  annotations:
    kubernetes.io/ingress.class: kong
    konghq.com/plugins: upstream-auth-basic-example
spec:
  rules:
  - host: examplehostname.com
    http:
      paths:
      - path: /bar
        backend:
          service:
            name: echo
            port:
              number: 80

Replace ROUTE_NAME|ROUTE_ID with the id or name of the route that this plugin configuration will target.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: upstream-auth-basic
  route: ROUTE_NAME
  config: 
    username: kingkong
    password: 1-big-ape

Replace ROUTE_NAME|ROUTE_ID with the id or name of the route that this plugin configuration will target.

A plugin which is not associated to any service, route, or consumer is considered global, and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.

The following examples provide some typical configurations for enabling the upstream-auth-basic plugin globally.

Make the following request:

curl -X POST http://localhost:8001/plugins/ \
  --data "name=upstream-auth-basic"  \
    --data "config.username=kingkong" \
    --data "config.password=1-big-ape"

Create a KongClusterPlugin resource and label it as global:

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: <global-upstream-auth-basic>
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: \"true\"
config: 
  username: kingkong
  password: 1-big-ape
plugin: upstream-auth-basic

Add a plugins entry in the declarative configuration file:

plugins:
- name: upstream-auth-basic
  config: 
    username: kingkong
    password: 1-big-ape

Parameters

Here's a list of all the parameters which can be used in this plugin's configuration:

Form Parameter Description
name
required

Type: string		 The name of the plugin, in this case upstream-auth-basic.
service.name or service.id

Type: string		 The name or ID of the service the plugin targets.

Set one of these parameters if adding the plugin to a service through the top-level /plugins endpoint.

Not required if using /services/SERVICE_NAME|SERVICE_ID/plugins.
route.name or route.id

Type: string		 The name or ID of the route the plugin targets.

Set one of these parameters if adding the plugin to a route through the top-level /plugins endpoint.

Not required if using /routes/ROUTE_NAME|ROUTE_ID/plugins.
enabled

Type: boolean

Default value: true		 Whether this plugin will be applied.
api_id

Type: string		 The ID of the API the plugin targets.

Note: The API Entity is deprecated in favor of Services since CE 0.13.0 and EE 0.32.
config.username
required

The username to send in the Authorization header to the upstream service
config.password
required

The password to send in the Authorization header to the upstream service