Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Web UI: Auth and deployment boundary #435

New Issue
Closed
opened 2026-07-07 12:21:03 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-07 12:21:03 -05:00
Owner
Copy Link
Copy Source

Problem statement

An internal operator UI must not be exposed as a public unauthenticated service. Deployment assumptions need documentation and basic enforcement.

Scope

Document and implement internal-only serving model:

  • local/internal deployment only in MVP
  • recommend Cloudflare Access/WARP/VPN if exposed beyond localhost
  • no public unauthenticated access
  • no secrets in frontend
  • document environment variables and runtime assumptions

Acceptance criteria

  • Documentation explains local/internal deployment only for MVP
  • Recommends Cloudflare Access/WARP/VPN (or equivalent) if exposed beyond trusted network
  • Server refuses or warns on unsafe public bind configurations
  • No secrets in frontend bundle or client-side storage
  • Documents required environment variables and runtime assumptions (repo root, profile config path, Gitea host)

Non-goals

  • Building full SSO in MVP
  • Hosting on public internet without access controls
  • Embedding Gitea tokens in the UI

Relation to tracker

Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows.

Dependencies

Depends on #426. Can proceed in parallel with other read-only pages.

Notes

Treat the UI as an operator console, not a customer-facing app.

## Problem statement An internal operator UI must not be exposed as a public unauthenticated service. Deployment assumptions need documentation and basic enforcement. ## Scope Document and implement internal-only serving model: - local/internal deployment only in MVP - recommend Cloudflare Access/WARP/VPN if exposed beyond localhost - no public unauthenticated access - no secrets in frontend - document environment variables and runtime assumptions ## Acceptance criteria - Documentation explains local/internal deployment only for MVP - Recommends Cloudflare Access/WARP/VPN (or equivalent) if exposed beyond trusted network - Server refuses or warns on unsafe public bind configurations - No secrets in frontend bundle or client-side storage - Documents required environment variables and runtime assumptions (repo root, profile config path, Gitea host) ## Non-goals - Building full SSO in MVP - Hosting on public internet without access controls - Embedding Gitea tokens in the UI ## Relation to tracker Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows. ## Dependencies Depends on #426. Can proceed in parallel with other read-only pages. ## Notes Treat the UI as an operator console, not a customer-facing app.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#435