mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3544] [feature]: Backend auth support for Hoppscotch Desktop #1211
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#1211
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 @rokibulislaam on GitHub (Nov 13, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3544
Is there an existing issue for this?
Summary
I noticed that the desktop code was pushed a few days ago. I attempted to run it, but it appears that the backend implementation has not been pushed yet.
github.com/hoppscotch/hoppscotch@de725337d6/packages/hoppscotch-selfhost-desktop/src/platform/auth.ts (L264-L292)The released desktop app seems to be using Firebase. I'm curious about the backend implementation for the authentication part. Additionally, I'm interested in the frontend, specifically the process of injecting or intercepting requests to inject cookies that have been stored on Tauri's store. (https://github.com/hoppscotch/releases/releases/tag/v23.8.3-1)
Is there a plan to push these implementations soon? I'm not entirely sure how you have planned to achieve this, but I would be interested in contributing if the codes for the backend part and cookie injection could be pushed.
Thanks!
Best,
Rokibul
Why should this be worked on?
It appears that the most recent release (2023.8.3) may not be fully complete. Specifically, I noticed potential gaps in the handling of authentication in the backend and the injection of
access_tokeninto the header of each outgoing request from the Desktop App.@liyasthomas commented on GitHub (Mar 4, 2025):
Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release.
Download the latest builds and provide your valuable feedback.
Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.