Feature Request: Built-in User Authentication / Password Protection for Web UI
- Langage dominant
- Python
- Étoiles
- 133k
- Forks
- 15.7k
- Merge moyen
- 1 j 6 h
- PR mergées (30 j)
- 160
Description
### 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!
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par retracer comment ComfyUI expose l’interface web lorsqu’il est lancé avec --listen ; l’issue ne nomme aucun fichier du dépôt ni aucun test. Comparez le contrôle d’accès intégré demandé avec le contournement existant utilisant Nginx ou Caddy. La finalisation nécessiterait une conception d’authentification facultative validée, la configuration des identifiants, un accès web protégé et une couverture des chemins d’accès concernés.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- authentication, backend, security
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100