I have a pretty stable environment to upload to Sonatype my Java packages like fastutil. It has been pretty stable for the last +20 years so unfortunately I’ve become a bit rusty with the details. Suddenly my tentative to stage an artifact are met with /home/vigna/git/fastutil/build.xml:139: Could…

Hi, this seems like a question for the the Central Repository forum

Just moved this post to that forum for visibility!

Thanks! Unfortunately no help. I must say the very flaky nature of all the Java ecosystem is one of the things I’m not missing moving to Rust. I’ll try to go through the whole configuration again.

@sebastiano.vigna it seems like you have the same problem as I have: Upload to OSSRH varying error codes since July 22nd I don’t think we can solve it from our side - it’s something on Sonatype side, because (as you) I didn’t change anything…

I see. I’m available to do testing, but I don’t know who to contact…

Shouldn’t we try to file a bug report? We are already two people with the same issue.

Yes totally - would be good. Just I don’t know where. I thought this forum may be a way to get in touch…

From one of my contributors: Sonatype now enforces token authentication instead of username and password. Refer to the user manual to generate your token.

More precisely, follow these instructions: Generating a token - Documentation It is difficult for me to understand how can someone make such a major change and not arrange things so to emit a proper, useful error message.

I previously did switch to a token, and still have that problem…

Upload via ant/Maven stopped working with "reason phrase: Unauthorized (401)"

Central Repository

ph1 (Philip Helger) July 29, 2024, 2:40pm 19

Yes totally. It was changed. However I don’t understand WHY the token was changed without me doing anything. Anyway, I am already modifying all my GitHub Actions secrets :-/

Topic		Replies	Views
Upload to OSSRH varying error codes since July 22nd Central Repository	3	592	July 29, 2024
"401 Content access is protected by token" authentication failure while performing maven release Central Repository help , nexus-repository	24	9742	February 12, 2025
Status code: 401, reason phrase: Content access is protected by token Central Repository nexus-repository , central , maven	4	746	August 1, 2024
Status code: 401, reason phrase: Unauthorized (401) Central Repository nexus-repository	2	2976	March 25, 2024
`401 Content access is protected by token` even though I'm using my token Sonatype Nexus Repository help	1	931	June 24, 2024

Upload via ant/Maven stopped working with "reason phrase: Unauthorized (401)"

Related topics