2.9 KiB
type, title, description, tags, timestamp, story_id, status
| type | title | description | tags | timestamp | story_id | status | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| User Story | Manage RCON server connections | Administrators manage encrypted connection settings for Minecraft RCON server addresses. |
|
2026-08-08T13:40:43Z | US-021 | verified |
User Story
As an administrator, I want to manage one or more Minecraft RCON connections, so that server operations can be reached from the existing protected console.
Acceptance Criteria
- Existing account-manager administrators use the terminal header to select, add, edit, test, enable or disable, and delete RCON server connections.
- Each connection has a unique display name, server address, port, enabled state, and write-only password.
- RCON passwords are encrypted with an authenticated cipher using a deployment-managed master key and are never returned to the browser, audit events, or application logs.
- Updating a connection preserves its password unless an administrator explicitly supplies a replacement.
- Administrators can save any syntactically valid DNS hostname and port without deployment-managed endpoint configuration; IP literals remain rejected.
- Testing a connection authenticates through the server-side RCON proxy and reports a safe success or failure result.
- Add and edit use accessible modal forms, and deleting a connection requires an explicit danger-confirmation modal.
- Connection mutations independently recheck administrator authorization and create credential-safe audit events.
- Database changes use a generated versioned Drizzle migration rather than schema push.
Implementation
The unified terminal header selects connections and exposes add, test, enable or disable, edit, and delete controls. Add and edit use reusable accessible modal forms, while delete uses a danger-confirmation modal. Server actions manage endpoints without deployment-managed endpoint configuration, preserve write-only passwords, encrypt credentials with connection-bound AES-256-GCM, and emit credential-safe audit events. The rcon_servers table is delivered through generated migration 0006_curious_lester.sql.
Validation
Verified with RCON validation, encryption, gateway, component, and server-action tests; full workspace tests and type checks; web lint; OKF validation; Semgrep; dependency audit; and a production Next.js build on 2026-08-08. Validation confirms arbitrary valid internal or external DNS server addresses and ports no longer require deployment configuration while IP literals and malformed hostnames remain rejected. Action tests confirm independent authorization, password preservation, enabled-state rechecks, safe failures, and command audit redaction.