Files

ci/woodpecker/push/push Pipeline was successful

Details

major: kestrel is now a tak server (#6 )

## Added

- CoT (Cursor on Target) server on port 8089 enabling ATAK/iTAK device connectivity
- Support for TAK stream protocol and traditional XML CoT messages
- TLS/SSL support with automatic fallback to plain TCP
- Username/password authentication for CoT connections
- Real-time device position tracking with TTL-based expiration (90s default)
- API endpoints: `/api/cot/config`, `/api/cot/server-package`, `/api/cot/truststore`, `/api/me/cot-password`
- TAK Server section in Settings with QR code for iTAK setup
- ATAK password management in Account page for OIDC users
- CoT device markers on map showing real-time positions
- Comprehensive documentation in `docs/` directory
- Environment variables: `COT_PORT`, `COT_TTL_MS`, `COT_REQUIRE_AUTH`, `COT_SSL_CERT`, `COT_SSL_KEY`, `COT_DEBUG`
- Dependencies: `fast-xml-parser`, `jszip`, `qrcode`

## Changed

- Authentication system supports CoT password management for OIDC users
- Database schema includes `cot_password_hash` field
- Test suite refactored to follow functional design principles

## Removed

- Consolidated utility modules: `authConfig.js`, `authSkipPaths.js`, `bootstrap.js`, `poiConstants.js`, `session.js`

## Security

- XML entity expansion protection in CoT parser
- Enhanced input validation and SQL injection prevention
- Authentication timeout to prevent hanging connections

## Breaking Changes

- Port 8089 must be exposed for CoT server. Update firewall rules and Docker/Kubernetes configurations.

## Migration Notes

- OIDC users must set ATAK password via Account settings before connecting
- Docker: expose port 8089 (`-p 8089:8089`)
- Kubernetes: update Helm values to expose port 8089

Co-authored-by: Madison Grubb <madison@elastiflow.com>
Reviewed-on: #6

2026-02-17 16:41:41 +00:00

1.5 KiB

Raw Blame History

Map and Cameras

KestrelOS shows a map with devices, POIs, live sessions (Share live), and ATAK/iTAK positions. Click markers or use Cameras page to view streams.

Map Layers

Devices - Fixed feeds (IPTV, ALPR, CCTV, NVR, etc.) added via API
POIs - Points of interest (admin/leader can edit)
Live sessions - Mobile devices streaming via Share live
CoT (ATAK/iTAK) - Amber markers for connected TAK devices (position only)

Cameras

A camera is either:

A device - Fixed feed with stream URL
A live session - Mobile device streaming via Share live

View via map markers or Cameras page (sidebar).

Device Types

device_type	Use case
`alpr`, `nvr`, `doorbell`, `feed`, `traffic`, `ip`, `drone`	Labeling/filtering

source_type: mjpeg (MJPEG over HTTP) or hls (HLS .m3u8 playlist)

Stream URLs must be http:// or https://.

API: Devices

Create: POST /api/devices (admin/leader)

{
  "name": "Main gate ALPR",
  "device_type": "alpr",
  "lat": 37.7749,
  "lng": -122.4194,
  "stream_url": "https://alpr.example.com/stream.m3u8",
  "source_type": "hls"
}

List: GET /api/devices
Update: PATCH /api/devices/:id
Delete: DELETE /api/devices/:id

Cameras endpoint: GET /api/cameras returns devices + live sessions + CoT entities.

POIs

Admins/leaders add/edit from POI page (sidebar). POIs appear as map pins (reference only, no stream).

1.5 KiB Raw Blame History