Feature Request: Built-in User Authentication / Password Protection for Web UI
- Lingua principale
- Python
- Stelle
- 133k
- Fork
- 15.7k
- Merge medio
- 1g 6h
- PR unite (30g)
- 155
Descrizione
### Feature Idea
Is your feature request related to a problem? Please describe.
Currently, when running ComfyUI with remote access enabled (e.g., using the --listen flag or running on a publicly accessible server), the web interface is accessible to anyone who knows the IP and port, as there is no built-in mechanism for user authentication or password protection. This poses a significant security risk for users who host their instance on a shared network or cloud environment.
Describe the solution you'd like
I propose adding a built-in, optional user authentication feature to the ComfyUI core. This could be implemented via:
Command-line arguments: E.g., --username and --password .
Configuration file: Allowing users to define one or more user accounts.
The feature should require users to enter credentials before accessing the main workflow interface.
### Existing Solutions
Currently, the recommended workaround is to use a reverse proxy (like Nginx or Caddy) to implement basic HTTP authentication. While effective, this requires additional software setup and technical knowledge, making it a barrier for less experienced users who simply need basic access control. A built-in feature would greatly simplify deployment and enhance security out of the box.
### Other
Implementing this would greatly improve the security and usability of ComfyUI for users running instances outside of a strictly local environment. Thank you for considering this feature!
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia tracciando il modo in cui ComfyUI espone l’interfaccia web quando viene avviato con --listen; l’issue non indica file del repository né test. Confronta il controllo degli accessi integrato richiesto con il workaround esistente basato su Nginx o Caddy. Per considerarlo completato sarebbero necessari un design di autenticazione opzionale concordato, la configurazione delle credenziali, l’accesso web protetto e la copertura dei percorsi di accesso pertinenti.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- authentication, backend, security
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100