mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #3469] Login page #1173
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1173
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @UBT-FJ on GitHub (Oct 24, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3469
Hello,
is it possible to have the login page without having the main page accessable? so anyone lands on the URL they would need to login first so they can use the system.
@thetronjohnson commented on GitHub (Oct 25, 2023):
@UBT-FJ Hi, could you explain a bit more on the use case here?
The current approach enables user's to easily get started with API testing as soon as they land on hoppscotch.io
@balub commented on GitHub (Oct 25, 2023):
@UBT-FJ the behaviour you are asking for is currently not available in the Hoppscotch app.
@UBT-FJ commented on GitHub (Oct 25, 2023):
@balub I got that it is not available but maybe there is a way to add it!
@thetronjohnson what I would want is to have a user database and add people that I want to access the first page, then allow them to access the selfhost hoppscotch, then inside there it should be as it is.
@thetronjohnson commented on GitHub (Oct 25, 2023):
@UBT-FJ , understood.
The community edition of Hoppscotch self-hosted works the same way as hoppscotch.io, with an additional admin dashboard. Therefore, there is no way to restrict access to approved users only. You might have to host your instance under a VPN to prevent unauthorized access.
However, we offer this feature in our self-hosted enterprise edition, where only users approved by the admin can access the app.
@prom00 commented on GitHub (Nov 13, 2023):
I'm kind of surprised by this, as this is offered as open source. The pricing on the enterprise is even higher than the 'original' Postman. This is being advertised as great for small teams and commercial projects. How can this be used for a small team, where everybody can access this without having to login?
@AurelienConte commented on GitHub (Nov 29, 2023):
Totally agree with @prom00, i am testing to add this to my enterprise and after fully setuped my self hosted instance it is a red flags since everyone can access it without any login page.
The current community edition must be used under a VPN but for startups and small teams this can be difficult to maintain.
I would love to have the possibility to restrict the landing page with a login page.
@liyasthomas commented on GitHub (Nov 30, 2023):
This is a feature for organizations and enterprises. Consider self-hosting our enterprise edition that has private Hoppscotch Self-Hosted instances support that only allows authorized login-only users.
Documentation: https://docs.hoppscotch.io/documentation/self-host/enterprise-edition/getting-started
Enterprise Store: https://enterprise.hoppscotch.com
@prom00 commented on GitHub (Nov 30, 2023):
I don't really understand how you think a (small) team can work with this while everything is publicly open and available for the whole world. Even with the matter of security these days it's a basic functionality that you secure your data.
Whoever is using hoppscotch now, all data from the system is available for everyone whenever they find a small glitch somewhere, since they can easily register themselves to the system.
I get it, you want people to buy a license. But remember why people come to Hoppscotch from other (cough Postman) systems.
Making the application login protected will make the system alot more robust if you ask me.
We already have the problem "sorted" by using a basic authentication on apache. But that's just not a real solution if you ask me.
Edit:
We already self host this on a vm. If I'm not mistaking, if we host the enterprise edition, we will pay 19$ per month per user right?
@liyasthomas commented on GitHub (Nov 30, 2023):
Access control protection and team login protection options are available on Enterprise plan.
In Hoppscotch self-hosted community edition, users can control allowed authentication providers, or control site access by IP address or location or via firewall traffic rules or by any external means.
Hoppscotch enterprise edition has inbuilt access control mechanisms to secure access to the self-hosted instances. Enterprise edition includes more features like SSO authentication, audit logs, etc and the license is priced at $19/user/month.
@prom00 commented on GitHub (Nov 30, 2023):
So basically we are using an open source project where people are encouraged to pay for good security?
@liyasthomas commented on GitHub (Nov 30, 2023):
Hoppscotch enterprise edition is built on top of the open-core community edition for those who want additional features like SAML-based Single-Sign-On, identity and access management, audit logs, dedicated support, etc.
All work product on the community edition is provided "AS IS". This includes unlimited collections, unlimited teams, and collaborators, an admin dashboard, community support, etc.
Since access control mechanisms are already available in the enterprise edition and are not planned for the community edition, I'm closing this ticket.
@bigghe commented on GitHub (Sep 12, 2024):
Hello @liyasthomas
I don't know if you are the correct person to ask about, but one thing.
I see that the issue #3447 is open asking more or less the same thing, a way to authenticate as users in the selfhosted version of Hoppscotch.
But then in a latest issue, #4232, I see a possible bug in authenticate to the selfhosted version through Microsoft.
Then it's not really clear to me, is the authentication (also a basic one, just username/password), possible or not in the selfhosted version of the app?
Thanks!
@liyasthomas commented on GitHub (Sep 12, 2024):
Hi @bigghe,
As of now, Hoppscotch doesn't have a username + password authentication mechanism. Both Hoppscotch Cloud and Hoppscotch Self-Hosted Editions prefer OAuth Authentication over Basic Authentication, along with Passwordless Authentication using email links.