[GH-ISSUE #4692] [feature]: Support Username/Password Login for Offline Deployment in Hoppscotch #1748

New issue

Open

opened 2026-03-16 21:36:38 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 21:36:38 +03:00

Owner

Originally created by @XiEdAotonG on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4692

Is there an existing issue for this?

I have searched the existing issues

Summary

Hoppscotch currently relies on external authentication mechanisms that require internet access. To support fully offline deployments in internal networks, Hoppscotch should be enhanced to allow username/password-based authentication. This would enable users to operate Hoppscotch in environments without external connectivity, such as secure internal networks systems.

Why should this be worked on?

Offline Deployment: Many organizations operate in secure or isolated environments where internet access is restricted. Supporting username/password login ensures Hoppscotch can be used in such scenarios without compromising security.
Flexibility: Adding this feature broadens Hoppscotch's usability, making it suitable for a wider range of deployment scenarios, including government, healthcare, and financial sectors with strict compliance requirements.
User Convenience: For teams managing internal systems, a simple username/password login is often more practical and easier to manage compared to complex authentication mechanisms.
Competitive Advantage: Many similar tools already support offline authentication. Adding this feature would make Hoppscotch more competitive and appealing to potential users in restricted environments.

This enhancement would significantly improve Hoppscotch's versatility and adoption in enterprise settings.

Originally created by @XiEdAotonG on GitHub (Jan 24, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4692 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Hoppscotch currently relies on external authentication mechanisms that require internet access. To support fully offline deployments in internal networks, Hoppscotch should be enhanced to allow username/password-based authentication. This would enable users to operate Hoppscotch in environments without external connectivity, such as secure internal networks systems. ### Why should this be worked on? 1. **Offline Deployment**: Many organizations operate in secure or isolated environments where internet access is restricted. Supporting username/password login ensures Hoppscotch can be used in such scenarios without compromising security. 2. **Flexibility**: Adding this feature broadens Hoppscotch's usability, making it suitable for a wider range of deployment scenarios, including government, healthcare, and financial sectors with strict compliance requirements. 3. **User Convenience**: For teams managing internal systems, a simple username/password login is often more practical and easier to manage compared to complex authentication mechanisms. 4. **Competitive Advantage**: Many similar tools already support offline authentication. Adding this feature would make Hoppscotch more competitive and appealing to potential users in restricted environments. This enhancement would significantly improve Hoppscotch's versatility and adoption in enterprise settings.