API Key Authentication

Secure Your Kitura API with API Keys

The Zuplo API Gateway protects your backend API from unauthorized access, abuse, and overload. Add API key authentication to your Kitura API in minutes.

Secure Access

Authenticate every request before it reaches your backend.

Control Costs

Set rate limits and quotas to prevent runaway usage.

Ensure Reliability

Shield your backend from overload with traffic management.

How it works

The Zuplo API Gateway sits between your clients and your Kitura backend, providing a secure layer of protection and control.

Client

Zuplo API Gateway

Customer VPC

Backend

Step-by-step tutorial

It takes only a few minutes to put Zuplo in front of your Kitura backend, adding API key authentication, and configuring your origin to trust requests from Zuplo using shared secrets.

Create a Route in Zuplo

First, create a new route in your Zuplo project that will proxy requests to your Kitura backend. This route will be the entry point for your API consumers.

Learn how to create routes

📄 OpenAPI native. Import your existing OpenAPI spec to instantly create routes and power your API documentation .

Add API Key Authentication Policy

Add the API Key Authentication policy to your route. This policy validates incoming API keys and ensures only authorized consumers can access your API.

Adding API Key Authentication policy in Zuplo

API Key Authentication docs

🔐 Leaked key? No problem. As a GitHub Secret Scanning partner, Zuplo can automatically revoke exposed keys before they can be exploited.

Add Set Header Policy

Add the Set Header policy to your route. This policy sets the shared secret header on requests to ensure only requests from Zuplo are accepted by your API.

Set Header Policy docs

Secure Your Kitura API with the Shared Secret

Configure your Kitura backend to validate the shared secret header set by Zuplo. This ensures that only requests coming through your Zuplo gateway are accepted.

Swift

 import Kitura
import Foundation
import LoggerAPI
import SwiftJWT

// Middleware to validate shared secret header
func validateSharedSecret(request: RouterRequest, response: RouterResponse, next: @escaping () -> Void) {
    guard let expectedSecret = ProcessInfo.processInfo.environment["SHARED_SECRET"] else {
        Log.error("Server configuration error: SHARED_SECRET not set")
        response.status(.internalServerError).send(json: ["error": "Server configuration error"])
        return
    }

    guard let secret = request.headers["X-Shared-Secret"] else {
        response.status(.unauthorized).send(json: ["error": "No secret provided"])
        return
    }

    // Use timing-safe comparison to prevent timing attacks
    if secret.count != expectedSecret.count || !CryptoUtils.constantTimeEquals(expectedSecret, secret) {
        response.status(.unauthorized).send(json: ["error": "Invalid secret"])
        return
    }

    next()
}

// Setup Kitura router
let router = Router()

// Example protected route
router.get("/protected", handler: validateSharedSecret) { request, response, next in
    response.send(json: ["message": "Access granted"])
    next()
}

// Start the Kitura server
Kitura.addHTTPServer(onPort: 8080, with: router)
Kitura.run() 

Call Your API Through Zuplo

Now you can call your API through Zuplo using an API key. The request will be authenticated at the gateway, and securely forwarded to your Kitura backend.

bash

 curl -X GET \
  'https://your-api.zuplo.dev/your-route' \
  -H 'Authorization: Bearer YOUR_API_KEY' 

Ready to secure your API?

Get started with Zuplo for free and add API key authentication to your Kitura API in minutes.

Start for Free Read the Docs