Skip to content
Meddle Docs

Auth Connector

Overview

Section titled “Overview”

The Auth connector validates JWT (JSON Web Tokens) in data payloads.

Connector Type: MeddleAuth

JWT Secret Mode

Section titled “JWT Secret Mode”

Validate JWT using a shared secret:

{
  "type": "MeddleAuth",
  "config": {
    "mode": "JwtSecret",
    "jwtSecretConfig": {
      "key": "auth_token",
      "secret": "your-secret-key-here"
    }
  }
}

JWKS Mode

Section titled “JWKS Mode”

Validate JWT using JSON Web Key Set (JWKS):

{
  "type": "MeddleAuth",
  "config": {
    "mode": "Jwks",
    "jwksConfig": {
      "jwksUrl": "https://auth.example.com/.well-known/jwks.json",
      "key": "token"
    }
  }
}

How It Works

Section titled “How It Works”
  1. Connector extracts JWT from payload using specified key
  2. Validates JWT signature and expiration
  3. If valid, passes payload through
  4. If invalid, blocks payload

Example Payload

Section titled “Example Payload”

Input:

{
  "data": "sensor_reading",
  "auth_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

If token is valid, payload passes through.
If token is invalid, payload is blocked.

Configuration Parameters

Section titled “Configuration Parameters”

JWT Secret Mode

Section titled “JWT Secret Mode”
  • key: Payload field containing the JWT
  • secret: Shared secret for validation

JWKS Mode

Section titled “JWKS Mode”
  • key: Payload field containing the JWT
  • jwksUrl: URL to JWKS endpoint

Use Cases

Section titled “Use Cases”
  1. Secure API endpoints that receive data from external sources
  2. Validate user permissions before processing data
  3. Implement access control in data workflows
  4. Protect sensitive operations

Best Practices

Section titled “Best Practices”
  • Use JWKS for production environments
  • Rotate secrets regularly
  • Use HTTPS for JWKS URLs
  • Combine with other security measures
Section titled “Related Connectors”