2.4 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 internal Minecraft RCON endpoints. |
|
2026-08-08T01:36:00Z | 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 can list, add, edit, test, enable or disable, and delete RCON server connections.
- Each connection has a unique display name, internal hostname, 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.
- Connection host and port pairs must match a deployment-managed exact internal endpoint allowlist, and IP literals are rejected.
- Testing a connection authenticates through the server-side RCON proxy and reports a safe success or failure result.
- Deleting a connection requires explicit confirmation.
- 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 administrator RCON page and server actions manage allowlisted endpoints, 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; and a production Next.js build on 2026-08-08. Action tests confirm independent authorization, password preservation, enabled-state rechecks, safe failures, and command audit redaction.