github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-07 12:37:14 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2654] Desktop app login flow: URL params stripped too quickly #6723

New Issue
Open
opened 2026-04-20 17:18:11 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 17:18:11 -05:00
Owner
Copy Link

Originally created by @CrazyWolf13 on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2654

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Hi,

With Vikunja 2.3.0, the desktop app now opens the system default browser for login. While this works in general, it becomes problematic when using multiple browsers.

In my case, I’m already logged into Vikunja in one browser, but the app opens another one. I tried copying the login URL and pasting it into the correct browser, but this doesn’t work because the URL parameters are cleared almost immediately due to the redirect. I guess this is for security.

Problem:

  • The login URL (with auth parameters) is only available for a very short moment
  • It gets stripped/redirected before it can be copied
  • This makes it impossible to transfer the login flow to another browser manually

Why this matters:
Users with multiple browsers (or profiles/containers) may not be authenticated in the default browser, even though they already have a valid session elsewhere. This makes the login flow unnecessarily frustrating or forces re-authentication.

Suggested improvements:

  • Show the full redirect URL (including parameters) on an intermediate page before redirecting
  • Add a “Copy URL” button (similar to VS Code’s auth flow)
  • Optionally delay the redirect slightly to allow manual copying
  • Or provide a fallback/manual login option in the desktop app

This would make the login flow more flexible and user-friendly in multi-browser setups.

Thanks!

Vikunja Version

2.3.0

Browser and version

Firefox 149.0

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @CrazyWolf13 on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2654 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Hi, With Vikunja 2.3.0, the desktop app now opens the system default browser for login. While this works in general, it becomes problematic when using multiple browsers. In my case, I’m already logged into Vikunja in one browser, but the app opens another one. I tried copying the login URL and pasting it into the correct browser, but this doesn’t work because the URL parameters are cleared almost immediately due to the redirect. I guess this is for security. **Problem:** * The login URL (with auth parameters) is only available for a very short moment * It gets stripped/redirected before it can be copied * This makes it impossible to transfer the login flow to another browser manually **Why this matters:** Users with multiple browsers (or profiles/containers) may not be authenticated in the default browser, even though they already have a valid session elsewhere. This makes the login flow unnecessarily frustrating or forces re-authentication. **Suggested improvements:** * Show the full redirect URL (including parameters) on an intermediate page before redirecting * Add a “Copy URL” button (similar to VS Code’s auth flow) * Optionally delay the redirect slightly to allow manual copying * Or provide a fallback/manual login option in the desktop app This would make the login flow more flexible and user-friendly in multi-browser setups. Thanks! ### Vikunja Version 2.3.0 ### Browser and version Firefox 149.0 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the area/desktopconcern/uxarea/auth labels 2026-04-20 17:18:12 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/auth area/desktop concern/ux
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6723
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?