dmg/minecraft-account-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

feat(rcon): refine server console
CI / validate (push) Successful in 6m11s
Details
Release / release (push) Successful in 7m59s
Details

Browse Source
This commit is contained in:
dmg
2026-08-08 08:06:11 -04:00
parent 7f6d69e0a7
commit 3564d24a45
10 changed files with 58 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
design/us-021-rcon-connections.md
+4 -4
View File
@@ -1,9 +1,9 @@
---
type: User Story
title: Manage RCON server connections
description: Administrators manage encrypted connection settings for internal Minecraft RCON endpoints.
description: Administrators manage encrypted connection settings for Minecraft RCON server addresses.
tags: [admin, rcon, minecraft, security, operations]
timestamp: 2026-08-08T11:44:59Z
timestamp: 2026-08-08T12:05:37Z
story_id: US-021
status: verified
---
@@ -15,7 +15,7 @@ As an administrator, I want to manage one or more Minecraft RCON connections, so
# 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] Each connection has a unique display name, server address, 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.
@@ -30,7 +30,7 @@ The administrator RCON page and server actions manage endpoints without deployme
# 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.
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.
# Related Stories