Gradle publish fails

[DeadlyMC]

I'm trying to deploy some files to a maven repo using the maven-publish gradle plugin with no luck. It always errors with a status 401 : Unauthorized.

This is the gradle publish task:

The alias and token aren't wrong as ive used them in the web login without any issues.

[dzikoysk]

Hey :) Did you associate a proper path with w permission?

[DeadlyMC]

yes, m with /*

[dzikoysk]

Could you enable debug in configuration? As far as I remember, I've added some extra logging during the authorization.

[DeadlyMC]

This is all that shows up when i run gradlew publish

[dzikoysk]

Add -Dtinylog.writerActive.level=DEBUG as VM option and check again

[BluCobalt]

the console output:

the gradle exception:

[dzikoysk]

Nah, I always forget that Gradle does not use basic auth by default. Just add it below the credentials:

credentials {
    // [...]
}
authentication {
    basic(BasicAuthentication)
}

Sorry for such a slow response, I'm kinda busy today 😅

[BluCobalt]

Lol, it's fine.
I added the authentication bit but it still gives me a 401 on maven-metadata.xml . Here is my publishing block:

[dzikoysk]

Does your Authentication header start with a Basic phrase?

I've added a log statement to print the response message for authentication error during deploy, check this build:
reposilite-2.9.10.zip (GitHub doesn't support .jar files, so rename zip to jar)

[BluCobalt]

[dzikoysk]

Let's try one more time 🤔

reposilite-2.9.10.zip

[BluCobalt]

[dzikoysk]

It looks like the associated path to the token does not really match the uri:

And you have enabled this option in configuration?

# Allow to omit name of the main repository in request
# e.g. /org/panda-lang/reposilite will be redirected to /releases/org/panda-lang/reposilite
rewritePathsEnabled: true

[dzikoysk]

yes, m with /*

Oh, wait, I didn't notice that you have asterisk after slash. Take a look at this table:

As you can see, there is no path that may end with * character. The only place where you can use functional asterisk is at the beginning of the path, to use it as a wildcard for repository name. Just regenerate your token with / or */ path and then it should work.

[BluCobalt]

Thank you! Setting a token with / worked.

@DeadlyMC you can close this and I'll gen new keys

[dzikoysk]

I've marked it as a documentation issue and I'll close it when I add BasicAuthentication to the docs :) I also think it might be a good idea to add a warning, when someone will generate a token with path that ends with asterisk.

[BluCobalt]

While you're here, do you know how (if possible) to change the text on the index page? I already set it in the reposilite.cdn but it still just says

[dzikoysk]

Are you sure it is not caused by Cloudflare cache?

[BluCobalt]

Yes, I have disabled caching for the subdomain with a page rule:

[dzikoysk]

As I thought, it is a known bug, that you can't use apostrophe:

window.REPOSILITE_DESCRIPTION = 'Legacy Fabric's maven repo'

You should be able to replace it with \' or just the Unicode representation.

[BluCobalt]

Escaping it worked, thanks!

[DeadlyMC]

Thank you! I'm able to publish too. Is the basic authentication bit imp? I was able to push without it

[dzikoysk]

I'm not sure when Gradle uses other auth method, but there was an issue related to this: #171 (comment)