github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

NuGet push returns 401 (Unauthorized) when using --api-key #9373

New Issue
Closed
opened 2025-11-02 08:36:48 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 08:36:48 -06:00
Owner
Copy Link

Originally created by @A9G-Data-Droid on GitHub (Aug 8, 2022).

Description

I created an organization with my main account. I can use my account to push nuget packages in to the repository for my organization. Then I generated an API token using the GUI, saved that to my password manager. I've been having trouble using that token.

When I run this command:

dotnet nuget push --source gitea {package_file} --api-key {gitea_token}

The response is:

error: Response status code does not indicate success: 401 (Unauthorized).

Gitea Version

Gitea Version: 1.17.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

2022/08/04 14:59:45 ...kages/nuget/nuget.go:25:apiError() [E] [62ec4151-12] context canceled

Screenshots

No response

Git Version

git version 2.31.1

Operating System

Operating System: Red Hat Enterprise Linux 8.6 (Ootpa) CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos Kernel: Linux 4.18.0-372.16.1.el8_6.x86_64

How are you running Gitea?

Installed from binary, running as a service.

Database

PostgreSQL

Originally created by @A9G-Data-Droid on GitHub (Aug 8, 2022). ### Description I created an organization with my main account. I can use my account to push nuget packages in to the repository for my organization. Then I generated an API token using the GUI, saved that to my password manager. I've been having trouble using that token. When I run this command: dotnet nuget push --source gitea {package_file} --api-key {gitea_token} The response is: > error: Response status code does not indicate success: 401 (Unauthorized). ### Gitea Version Gitea Version: 1.17.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist 2022/08/04 14:59:45 ...kages/nuget/nuget.go:25:apiError() [E] [62ec4151-12] context canceled ### Screenshots _No response_ ### Git Version git version 2.31.1 ### Operating System Operating System: Red Hat Enterprise Linux 8.6 (Ootpa) CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos Kernel: Linux 4.18.0-372.16.1.el8_6.x86_64 ### How are you running Gitea? Installed from binary, running as a service. ### Database PostgreSQL
GiteaMirror added the topic/packagestype/feature labels 2025-11-02 08:36:48 -06:00
GiteaMirror commented 2025-11-02 08:36:49 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 8, 2022):

That's simple, --api-key is not supported. You can just use your token instead of the password when creating the source.

Changed into feature request.

@KN4CK3R commented on GitHub (Aug 8, 2022): That's simple, `--api-key` is not supported. You can just use your token instead of the password when creating the source. Changed into feature request.
GiteaMirror commented 2025-11-02 08:36:49 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 8, 2022):

I have added this in #20717.

@KN4CK3R commented on GitHub (Aug 8, 2022): I have added this in #20717.
GiteaMirror commented 2025-11-02 08:36:49 -06:00
Author
Owner
Copy Link

@viceice commented on GitHub (Sep 22, 2022):

I still get 401 when using an api-key on 1.17.2

> dotnet nuget push -s https://gitea.domain.test/api/packages/org/nuget/index.json -k some-api-key .\bin\some.package.2.1.6.nupkg --force-english-output
error: Unable to load the service index for source https://gitea.domain.test/api/packages/org/nuget/index.json.
error:   Response status code does not indicate success: 401 (Unauthorized).
@viceice commented on GitHub (Sep 22, 2022): I still get 401 when using an api-key on 1.17.2 ```sh > dotnet nuget push -s https://gitea.domain.test/api/packages/org/nuget/index.json -k some-api-key .\bin\some.package.2.1.6.nupkg --force-english-output error: Unable to load the service index for source https://gitea.domain.test/api/packages/org/nuget/index.json. error: Response status code does not indicate success: 401 (Unauthorized).
GiteaMirror commented 2025-11-02 08:36:49 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Sep 22, 2022):

@viceice this was added in 1.18.0-dev, and was not backported to 1.17.2

@techknowlogick commented on GitHub (Sep 22, 2022): @viceice this was added in 1.18.0-dev, and was not backported to 1.17.2
GiteaMirror commented 2025-11-02 08:36:49 -06:00
Author
Owner
Copy Link

@viceice commented on GitHub (Sep 22, 2022):

@techknowlogick what about #20734 ? Isn't that the backport to v1.17.1 ? 😕

Also mentioned in release notes:
https://github.com/go-gitea/gitea/releases/tag/v1.17.1

@viceice commented on GitHub (Sep 22, 2022): @techknowlogick what about #20734 ? Isn't that the backport to v1.17.1 ? 😕 Also mentioned in release notes: https://github.com/go-gitea/gitea/releases/tag/v1.17.1
GiteaMirror commented 2025-11-02 08:36:50 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Sep 22, 2022):

Looked at this again, and yes it does not work the way you use it. :-)
If you use it with --source <name> it does work (that's how I tested #20734). You use it with --source <url/index.json>. Here the client makes a request to .../index.json but WITHOUT the token. This request fails then. I will add a second PR to handle this.

@KN4CK3R commented on GitHub (Sep 22, 2022): Looked at this again, and yes it does not work the way you use it. :-) If you use it with `--source <name>` it does work (that's how I tested #20734). You use it with `--source <url/index.json>`. Here the client makes a request to .../index.json but WITHOUT the token. This request fails then. I will add a second PR to handle this.
GiteaMirror commented 2025-11-02 08:36:50 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Dec 10, 2022):

The error indicates a connection problem.

@KN4CK3R commented on GitHub (Dec 10, 2022): The error indicates a connection problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/packages type/feature
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/gitea#9373
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?