Authentication workflow for Processing Service V2

[carlosgjs]

Suggested Authentication Token Management Workflow

The worker currently expects:

ANTENNA_API_BASE_URL: The base URL of the Antenna Django application
ANTENNA_API_TOKEN: The authentication token for API access

Antenna Admin

1. Creates user for the Worker
2. Generates a token via /admin/authtoken/tokenproxy/add/
3. Communicates token to Worker Admin

Worker Admin:

# Set environment variables
export ANTENNA_API_BASE_URL="https://antenna.yourorg.com"
export ANTENNA_API_TOKEN="your-generated-token-here"

# Or create a .env file
echo "ANTENNA_API_BASE_URL=https://antenna.yourorg.com" > .env
echo "ANTENNA_API_TOKEN=your-generated-token-here" >> .env

Run the worker:

ami worker --pipelines moth_binary

Recommend manually rotating tokens periodically (quarterly/annually)

[carlosgjs]

@mihow what do you think of this workflow?

[mihow]

Claude says: Related in-flight work: PR #1194 (API key auth + identity for processing services) and #1201 (key management UI), with ADC #136 — these implement the PSv2 worker authentication workflow this issue describes. Linking for tracking.