Authorization failed with error 403 for Aspose repo for download PDF java

Aspose.PDF Product Family
1

hello

since last 48 hours I receive an error through GitHub actions to access Aspose repo
and download PDF java artifact

authorization failed for https://repository.aspose.com/repo/com/aspose/aspose-pdf/24.5/aspose-pdf-
24.5.pom, status: 403 Forbidden → [Help 1]

I see another case opened but no clear solution

please advise

1 Like
2

@AssafBenMoshe

Can you please share how you have specified the dependency in pom.xml file?

3

it fails when run it from Github actions mainly

Aspose-Maven-Repository Aspose Maven Repository https://repository.aspose.com/repo/ com.aspose aspose-pdf 24.2

all was perfect till last days

4

We have been facing the same issue since Thursday afternoon in a gradle build on gitlab. Everything compiles locally and the build finishes normally. When we run it in a gitlab runner it fails.

I’ve tried multiple versions, and even went back and triggered a build that finished successfully on Thursday morning only to see it fail.

The repository is defined as:

repositories {

    maven { url = uri("https://releases.aspose.com/java/repo") }
    mavenCentral()
}

and all of following (I’ve tried every version from 23.9 → 24.5):

implementation("com.aspose:aspose-pdf:24.5")
implementation("com.aspose:aspose-pdf:24.5:jdk17")
implementation("com.aspose:aspose-pdf:23.10")

fail with the following error:

Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not download aspose-pdf-23.9.jar (com.aspose:aspose-pdf:23.9)
      > Could not get resource 'https://releases.aspose.com/java/repo/com/aspose/aspose-pdf/23.9/aspose-pdf-23.9.jar'.
         > Could not GET 'https://releases.aspose.com/java/repo/com/aspose/aspose-pdf/23.9/aspose-pdf-23.9.jar'. Received status code 403 from server: Forbidden

When I try to pull the ‘jdk17’ version it can’t find the POM:

> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve com.aspose:aspose-pdf:24.5.
     Required by:
         project :
      > Could not resolve com.aspose:aspose-pdf:24.5.
         > Could not get resource 'https://releases.aspose.com/java/repo/com/aspose/aspose-pdf/24.5/aspose-pdf-24.5.pom'.
            > Could not GET 'https://releases.aspose.com/java/repo/com/aspose/aspose-pdf/24.5/aspose-pdf-24.5.pom'. Received status code 403 from server: Forbidden
      > Could not resolve com.aspose:aspose-pdf:24.5.
         > Could not get resource 'https://repository.aspose.com/repo/com/aspose/aspose-pdf/24.5/aspose-pdf-24.5.pom'.
            > Could not GET 'https://repository.aspose.com/repo/com/aspose/aspose-pdf/24.5/aspose-pdf-24.5.pom'. Received status code 403 from server: Forbidden

Via a browser I can click all the way through from Aspose Repository Browser /java/repo/ to the jar and I’m able to download it. It just cannot get pulled from gitlab.

5

Am also facing same error as posted by @AssafBenMoshe in gitlab. Could you please provide solution for this asap, as we are blocked.

Am facing issue for aspose-cells/23.3 version.

6

we have noticed the same issue today and builds are failing for us as well.

Failed to collect dependencies at com.aspose:aspose-slides:jar:jdk16:23.2: Failed to read artifact descriptor for com.aspose:aspose-slides:jar:jdk16:23.2: Could not transfer artifact com.aspose:aspose-slides:pom:23.2 from/to AsposeJavaAPI (Aspose Repository Browser /java/repo/): authorization failed for https://repository.aspose.com/repo/com/aspose/aspose-slides/23.2/aspose-slides-23.2.pom, status: 403 Forbidden

7

We have to postpone the production release due to this unforeseen error. Please help asap

8

@jrbizzo

Would you please try to specify the URL like below:

repositories {

    maven { url = uri("https://releases.aspose.com/java/repo/") }
    mavenCentral()
}

There is an extra “/” at the end. Please check if it resolves your issue.

@pankajkundlia @AssafBenMoshe @yesumary
Could you please also try suggested change in your configuration and let us know how it went. We will further proceed accordingly.

9

in my case the url is already with extra
“/”
and it doesn’t work

10

Apparently you guys were getting pinged repeatedly so the firewall team blocked anyone that was calling excessively which I am guessing included anyone from a shared job-runner place like gitlab/hub/asure/etc. Once your hosting company/team changed the firewall rules our build started working although it looks like it’s not working for everyone.

See this thread for reference:

11

@jrbizzo
@AssafBenMoshe

Please allow us to investigate this case and we will get back to you with a feedback as soon as investigation is done.

12

The url am using is already with extra “/” .

13

Somehow, it worked only once after that am facing same issue. It’s not consistent.
Please provide solution asap, because of this our production deployment is blocked.

14

we are using maven and we have the / at the end for the repo config.

It worked has worked for years before failing few days back.

I am raising a support case with Aspose as we have paid support with our Aspose Total OEM License.

15

@yesumary @jrbizzo @pankajkundlia

We are checking it and will get back to you shortly.

16

,hi Apsose Team

?any update

Thanks

17

@AssafBenMoshe

We tested and could not replicate the issue.
Image.jpeg (277.0 KB)

Looks like there was a temporary issue with the server that seems to be resolved. Would you please confirm if issue is still happening at your end?

18

I see that it works now , I will keep follow up that it is stable

1 Like