40 lines
2.6 KiB
Markdown
40 lines
2.6 KiB
Markdown
---
|
|
type: User Story
|
|
title: Manage RCON server connections
|
|
description: Administrators manage encrypted connection settings for internal Minecraft RCON endpoints.
|
|
tags: [admin, rcon, minecraft, security, operations]
|
|
timestamp: 2026-08-08T11:44:59Z
|
|
story_id: US-021
|
|
status: 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
|
|
|
|
- [x] Existing account-manager administrators can list, add, edit, test, enable or disable, and delete RCON server connections.
|
|
- [x] Each connection has a unique display name, internal hostname, port, enabled state, and write-only password.
|
|
- [x] 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.
|
|
- [x] Updating a connection preserves its password unless an administrator explicitly supplies a replacement.
|
|
- [x] Administrators can save any syntactically valid DNS hostname and port without deployment-managed endpoint configuration; IP literals remain rejected.
|
|
- [x] Testing a connection authenticates through the server-side RCON proxy and reports a safe success or failure result.
|
|
- [x] Deleting a connection requires explicit confirmation.
|
|
- [x] Connection mutations independently recheck administrator authorization and create credential-safe audit events.
|
|
- [x] Database changes use a generated versioned Drizzle migration rather than schema push.
|
|
|
|
# Implementation
|
|
|
|
The administrator RCON page and 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 DNS hostname and port pairs 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.
|
|
|
|
# Related Stories
|
|
|
|
- [Operate servers through an RCON console](us-022-rcon-console.md)
|
|
- [Authenticate administrators with SSO](us-011-admin-sso.md)
|
|
- [Deploy and operate securely](us-015-platform-operations.md)
|