Demo · Step 1
Operations console sign-in
- Public landing page makes the promise explicit: mock integrations active, no RTSP credentials exposed.
- Administrators sign in to a separate, authorized-personnel console.
- Password hashed with Argon2. Session is an opaque HTTP-only, SameSite=Strict cookie.
- Every state-changing request is origin-checked.
Landing page
Operations console sign-in
GOAA Secure Video · POC05
Demo · Step 2
The operational picture
- Active alert, provisioned users (pilot cap of 20), active viewers and camera status at a glance.
- Starts idle: "No active alert. Run a test alert to begin the demo."
- Camera status reads 10/12, with one camera offline per zone by design, to show status monitoring.
- The Run test alert panel is where we'll trigger the full email → alert → SMS flow.
GOAA Secure Video · POC06
Demo · Step 3
Zones & cameras
- Pilot covers Zone 1 and Zone 2 with six cameras each: gates, door, ramp, concourse and service corridor.
- A placement map shows live (green) and offline (red) cameras.
- Operators can mark a camera live or offline, and viewers pick up the change on reload.
- RTSP endpoints stay server-side. The browser only ever sees camera names.
GOAA Secure Video · POC07
Demo · Step 4 · Simulated Everbridge
Run a test alert for Zone 1
- One click generates an Everbridge-format email and sends it through real validation and parsing.
- An incident goes ACTIVE with its Everbridge ID, and any previous alert is closed automatically.
- All three enabled responders are notified: 3 delivered, 0 queued, 0 failed.
- Last successful ingestion updates, confirming the pipeline ran end to end.
POST /admin/test-alert → ingestEmail → processSmsQueue08
Demo · Step 5 · Simulated SMS
What the responder receives
- The notification outbox tracks every message: recipient, safe message, status, attempts.
- Preview shows the SMS exactly as it lands on the phone.
- The message carries no incident details, zone or camera information, only a unique secure link.
- Failed sends retry automatically (+30 s, +60 s) and can be retried manually.
- Alerts → Secure links lists every responder's link for the active alert, with Copy link, Open and Copy all.
Notification outbox
Phone preview of the delivered message
Link tokens: 32 random bytes · stored only as peppered SHA-25609
Demo · Step 6 · Invited responder
Identity check on the GOAA-issued phone
- Tapping the link validates it server-side before anything is shown.
- Incident details stay hidden until the 4-digit PIN is verified.
- A wrong PIN is rejected and logged as
PIN_FAILED. - The correct PIN creates a server-side session. It is never stored in the link.
PIN entry
Incorrect PIN rejected
GOAA Secure Video · POC10
Demo · Step 7
Six live views of the affected zone
The responder sees only the active incident and its zone's cameras. The offline Service Corridor camera is shown as unavailable.
Same view on the phone
GET /viewer/context → POST /video/token → POST /viewer/playback11
Demo · Step 8
Fullscreen camera review
- Any live tile opens a fullscreen view, with ‹ › or the arrow keys to move between cameras.
- Each open requests a fresh video token, logged as
CAMERA_FULLSCREEN_OPENED. - The on-screen timer shows the 5-minute authorization window.
- If access is revoked meanwhile, the feed is refused and the viewer closes.
Video token TTL: 300 s · validated by the gateway on every request12
Demo · Step 9 · Security control
Instant revocation
- In People & phones, the admin sees each responder's device and last access.
- Disable revokes all of the user's sessions at once: "User disabled and sessions revoked."
- The responder's next request is refused, and the link now shows "Link unavailable".
- Enable, Reset PIN and Revoke sessions are one click each, and all are audited.
Admin disables GOAA User A
Responder is locked out immediately
USER_DISABLED · SESSION_REVOKED · VIDEO_TOKEN_REJECTED13
Demo · Step 10 · Security control
PIN lockout & alert lifecycle
5 wrong PINs → locked for 15 min
- Brute force is stopped: five failed PINs lock the account for 15 minutes (
PIN_LOCKED). An admin can Reset PIN to clear it. There is also a per-IP limit of 20 attempts per 15 minutes. - One active incident at a time: a new Zone 2 alert automatically closes the Zone 1 alert, and every Zone 1 link and session stops working.
GOAA Secure Video · POC14
Demo · Step 11
A complete, immutable audit trail
Every step of the flow is recorded, from the email arriving to the moment a responder opens a camera. That gives a defensible record for incident review.
EMAIL_RECEIVEDEMAIL_VALIDATEDEMAIL_REJECTEDEMAIL_PARSEDDUPLICATE_EMAIL_IGNORED
ALERT_CREATEDALERT_ACTIVATEDALERT_CLOSEDALERT_EXPIREDTEST_ALERT_CREATED
SMS_QUEUEDSMS_SENTSMS_DELIVEREDSMS_FAILED
SECURE_LINK_OPENEDPIN_VERIFIEDPIN_FAILEDPIN_LOCKEDSESSION_CREATEDSESSION_REVOKED
VIDEO_TOKEN_ISSUEDVIDEO_TOKEN_REJECTEDCAMERA_GRID_OPENEDCAMERA_VIEWEDCAMERA_FULLSCREEN_OPENED
USER_DISABLEDUSER_ENABLEDADMIN_CHANGE
Highlighted: the happy-path chain from one alert to one camera view.
28 audit event types · packages/shared15
Demo · Step 12
Integration readiness
- The full workflow already runs end to end on adapters. Going live means swapping in vendor credentials, not rebuilding.
- A live health strip covers the API, database, email worker, SMS and video providers.
- The state shows Degraded only because of the two deliberately offline demo cameras.
- Each vendor card lists exactly what we need from them.
Vendor adapters fail closed until configured16