Files
kestrelos/test/unit/cotServer.spec.js
Keli Grubb e61e6bc7e3
All checks were successful
ci/woodpecker/push/push Pipeline was successful
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

48 lines
2.0 KiB
JavaScript

/**
* Tests that the CoT parse-and-store path behaves as when a fake ATAK client sends TAK stream frames.
* Uses the same framing and payload parsing the server uses; does not start a real TCP server.
*/
import { describe, it, expect, beforeEach } from 'vitest'
import { buildTakFrame, buildPositionCotXml } from '../helpers/fakeAtakClient.js'
import { parseTakStreamFrame, parseCotPayload } from '../../server/utils/cotParser.js'
import { updateFromCot, getActiveEntities, clearCotStore } from '../../server/utils/cotStore.js'
describe('cotServer (parse-and-store path)', () => {
beforeEach(() => {
clearCotStore()
})
it('stores entity when receiving TAK stream frame with position CoT XML', async () => {
const xml = buildPositionCotXml({ uid: 'device-1', lat: 37.7, lon: -122.4, callsign: 'Bravo' })
const frame = buildTakFrame(xml)
const parsedFrame = parseTakStreamFrame(frame)
expect(parsedFrame).not.toBeNull()
const parsed = parseCotPayload(parsedFrame.payload)
expect(parsed).not.toBeNull()
expect(parsed.type).toBe('cot')
await updateFromCot(parsed)
const active = await getActiveEntities()
expect(active).toHaveLength(1)
expect(active[0].id).toBe('device-1')
expect(active[0].lat).toBe(37.7)
expect(active[0].lng).toBe(-122.4)
expect(active[0].label).toBe('Bravo')
})
it('updates same uid on multiple messages', async () => {
const xml1 = buildPositionCotXml({ uid: 'u1', lat: 1, lon: 2 })
const xml2 = buildPositionCotXml({ uid: 'u1', lat: 3, lon: 4, callsign: 'Updated' })
const frame1 = buildTakFrame(xml1)
const frame2 = buildTakFrame(xml2)
const p1 = parseCotPayload(parseTakStreamFrame(frame1).payload)
const p2 = parseCotPayload(parseTakStreamFrame(frame2).payload)
await updateFromCot(p1)
await updateFromCot(p2)
const active = await getActiveEntities()
expect(active).toHaveLength(1)
expect(active[0].lat).toBe(3)
expect(active[0].lng).toBe(4)
expect(active[0].label).toBe('Updated')
})
})