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

Automatically redirects if only one Oauth provider #106

New Issue
Closed
opened 2025-11-01 20:47:11 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-01 20:47:11 -05:00
Owner
Copy Link

Originally created by @thelicato on GitHub (Nov 14, 2022).

Description

Currently if there is only one Oauth provider it automatically "clicks" on the "Login with " button. This is especially awkward when you logout and it automatically re-performs the login.

Vikunja Frontend Version

0.20.1

Vikunja API Version

0.20.1

Browser and version

Chrome Version 107.0.5304.110 (Official Build) (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @thelicato on GitHub (Nov 14, 2022). ### Description Currently if there is only one Oauth provider it automatically "clicks" on the "Login with <provider>" button. This is especially awkward when you logout and it **automatically re-performs the login**. ### Vikunja Frontend Version 0.20.1 ### Vikunja API Version 0.20.1 ### Browser and version Chrome Version 107.0.5304.110 (Official Build) (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:47:12 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 14, 2022):

This is meant for cases where you open Vikunja from an external source (like a dashboard) and would want to get logged in right away.

What would you propose as a solution to that problem?

@kolaente commented on GitHub (Nov 14, 2022): This is meant for cases where you open Vikunja from an external source (like a dashboard) and would want to get logged in right away. What would you propose as a solution to that problem?
GiteaMirror commented 2025-11-01 20:47:12 -05:00
Author
Owner
Copy Link

@thelicato commented on GitHub (Nov 15, 2022):

Well I think that the normal usage is that the user must click on the OpenID provider login button. It doesn't make sense this way, it is also impossible to fully logout in a normal way.

@thelicato commented on GitHub (Nov 15, 2022): Well I think that the normal usage is that the user **must** click on the OpenID provider login button. It doesn't make sense this way, it is also impossible to fully logout in a normal way.
GiteaMirror commented 2025-11-01 20:47:12 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 16, 2022):

With 3891d5b876 there's now an extra query parameter to automatically redirect. This allows for automatically logging in when opening Vikunja from an external dashboard but prevents automatically re-logging the user in after being logged out.

@kolaente commented on GitHub (Nov 16, 2022): With https://github.com/go-vikunja/frontend/commit/3891d5b87634c890265477680fafaa04ff06cc3e there's now an extra query parameter to automatically redirect. This allows for automatically logging in when opening Vikunja from an external dashboard but prevents automatically re-logging the user in after being logged out.
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
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#106
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?