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

[GH-ISSUE #112] API call for attachment download => "missing, malformed, expired or otherwise invalid token provided" #5985

New Issue
Closed
opened 2026-04-20 16:28:12 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-20 16:28:12 -05:00
Owner
Copy Link

Originally created by @ozuzo on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/112

Description

I think I've assigned all roles to an API token in Vikunja, and are able to extract projects, tasks, etc from the API. But when trying to recreate download links for attachments, I get

[message] => missing, malformed, expired or otherwise invalid token provided

for the /tasks/XX/attachments/YY call, instead of the contents of the attachment

Are tokens supposed to work for this call as well?

Vikunja Frontend Version

0.22.1

Vikunja API Version

0.22.1

Browser and version

n/a

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @ozuzo on GitHub (Feb 2, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/112 ### Description I think I've assigned all roles to an API token in Vikunja, and are able to extract projects, tasks, etc from the API. But when trying to recreate download links for attachments, I get `[message] => missing, malformed, expired or otherwise invalid token provided ` for the `/tasks/XX/attachments/YY` call, instead of the contents of the attachment Are tokens supposed to work for this call as well? ### Vikunja Frontend Version 0.22.1 ### Vikunja API Version 0.22.1 ### Browser and version n/a ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the enhancement label 2026-04-20 16:28:12 -05:00
GiteaMirror commented 2026-04-20 16:28:16 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 5, 2024):

Looks like attachment upload and download are not included in the available token scopes.

<!-- gh-comment-id:1928092914 --> @kolaente commented on GitHub (Feb 5, 2024): Looks like attachment upload and download are not included in the available token scopes.
GiteaMirror commented 2026-04-20 16:28:17 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 14, 2024):

Now implemented in 415c6380a5, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

Note that you need to recreate any tokens you were previously using for this.

<!-- gh-comment-id:1943828185 --> @kolaente commented on GitHub (Feb 14, 2024): Now implemented in 415c6380a52fa15d1765cd3d4915bc0e76b1349a, please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)). Note that you need to recreate any tokens you were previously using for this.
GiteaMirror commented 2026-04-20 16:28:17 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 14, 2024):

Thanks - this seems to work now in my reporting tool :-)

<!-- gh-comment-id:1944102769 --> @ozuzo commented on GitHub (Feb 14, 2024): Thanks - this seems to work now in my reporting tool :-)
GiteaMirror commented 2026-04-20 16:28:18 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 14, 2024):

I'm a little curious, how are you using the api?

<!-- gh-comment-id:1944151463 --> @kolaente commented on GitHub (Feb 14, 2024): I'm a little curious, how are you using the api?
GiteaMirror commented 2026-04-20 16:28:19 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 14, 2024):

I'm running Vikunja to support a small group of not-very-technical board members of a committee - so we have a central location for ongoing tasks, keeping track of related documents etc (in the past this was usually done only in the minutes of meetings, quite ineffecient). Two issues: te GUI is for some of them already a bit challenging, and it was a bit difficult tracking any changes since our last board meeting (specifically: added comments).

So I've written a small PHP script to generate an overview of all open tasks, with all comments and attachments, highlighting any comments made within the last four weeks (the usual interval between meetings). That way we have a nice summary of what to discuss, and everybody can easily prepare...

<!-- gh-comment-id:1944160421 --> @ozuzo commented on GitHub (Feb 14, 2024): I'm running Vikunja to support a small group of not-very-technical board members of a committee - so we have a central location for ongoing tasks, keeping track of related documents etc (in the past this was usually done only in the minutes of meetings, quite ineffecient). Two issues: te GUI is for some of them already a bit challenging, and it was a bit difficult tracking any changes since our last board meeting (specifically: added comments). So I've written a small PHP script to generate an overview of all open tasks, with all comments and attachments, highlighting any comments made within the last four weeks (the usual interval between meetings). That way we have a nice summary of what to discuss, and everybody can easily prepare...
GiteaMirror commented 2026-04-20 16:28:19 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 14, 2024):

Looks like:

image

<!-- gh-comment-id:1944169908 --> @ozuzo commented on GitHub (Feb 14, 2024): Looks like: ![image](https://github.com/go-vikunja/vikunja/assets/5175516/acd9a6cf-0514-461c-b8e7-a04590a749e3)
GiteaMirror commented 2026-04-20 16:28:20 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 14, 2024):

Very nice, thanks for the insight!

<!-- gh-comment-id:1944242073 --> @kolaente commented on GitHub (Feb 14, 2024): Very nice, thanks for the insight!
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 enhancement
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#5985
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?