Maven build failed: Could not resolve dependencies with 403

Aspose.Words Product Family
,
1

The team hit issue during maven build the project with dependency ‘aspose-words’ executed on Azure DevOps.

authorization failed for https://releases.aspose.com/java/repo/com/aspose/aspose-words/21.8/aspose-words-21.8.pom, status: 403 Forbidden

Wondering is there any configuration has to be done?

2

@henrycslai Could you please attach your POM file here for our reference? Please make sure it has the following:

...
<repository>
	<id>AsposeJavaAPI</id>
	<name>Aspose Java API</name>
	<url>https://releases.aspose.com/java/repo/</url>
</repository>
...
...
<dependency>
	<groupId>com.aspose</groupId>
	<artifactId>aspose-words</artifactId>
	<version>24.5</version>
	<classifier>jdk17</classifier>
</dependency>
...
3

We had the same error today.

Having a POM with a lot of dependencies, it seems like https://releases.aspose.com/java/repo/ is hitting the rate limit with a 403 error.

I found a workaround by creating a Maven module only with Aspose dependencies and the Aspose repository reference in it.

4

@nhnatyshyn Thank you for sharing your workaround.

5

alexey.noskov

I believe this needs to be fixed right?
The aspose repo on maven central from your organisation doesn’t show up anymore and all are builds are failing due to this.

image.png (64.1 KB)

Please look into this on priority.

6
AsposeJavaAPI Aspose Java API https://repository.aspose.com/repo/ 
    <dependency>
        <groupId>com.aspose</groupId>
        <artifactId>aspose-words</artifactId>
        <version>19.11</version>
        <classifier>jdk17</classifier>
    </dependency>

This is giving 403 forbidden exception since yesterday now.

Please check this.

7

@alexey.noskov

this is the error we are getting

[ERROR] Failed to execute goal on project resourceService: Could not resolve dependencies for project com.gce.lms:resourceService:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at com.aspose:aspose-words:jar:jdk17:24.5: Failed to read artifact descriptor for com.aspose:aspose-words:jar:jdk17:24.5: The following artifacts could not be resolved: com.aspose:aspose-words:pom:24.5 (absent): Could not transfer artifact com.aspose:aspose-words:pom:24.5 from/to AsposeJavaAPI (https://repository.aspose.com/repo/): status code: 403, reason phrase: Forbidden (403) -> [Help 1]
8

@ankit11088 I have informed the responsible person regarding the problem. Please accept our apologies for your inconvenience.

9

@ankit11088 @nhnatyshyn @henrycslai I have received an answer from our hosting team.

We have been experiencing a huge and sudden surge in parasitic traffic since the beginning of May. We expect this increase to continue.
Therefore, we have enabled the Web Application Firewall, and it is quite possible that clients making more than 300 requests in 5 minutes have been blocked.

10

I believe there are multiple aspose users here are using Azure DevOps (Microsoft cloud service) to build the application. That’s why Azure DevOps is blocked by aspose artifacts now.

11

@henrycslai02 I have answered you via private message.

12

Hello. How could we resolve this issue?

13

@pavilandoangelo Could you please provide your IP address via private message from where the Aspose Repository is requested. We will check whether it has been blocked.

15

Hi @alexey.noskov , we currently facing the same issues, can you as well check ours ?

16

Same issue but we’re calling from gitlab.

17

@afrisanjaya @jrbizzo We are working with our hosting team in order to resolve the problem. Please accept our apologies for your inconvenience.

18

@afrisanjaya @henrycslai02 @nhnatyshyn @jrbizzo @pavilandoangelo @ankit11088 The hosting team informed that they have reconfigured our maven repository. Now one request is allowed every 2 seconds. Could you please check whether the problem still persist on your side?

19

still having the same issue from my side

[ERROR] Failed to execute goal on project pmp-service-budget-report: Could not resolve dependencies for project com.pmp:pmp-service-budget-report:jar:1.0.0: Failed to collect dependencies at com.aspose:aspose-cells:jar:22.9: Failed to read artifact descriptor for com.aspose:aspose-cells:jar:22.9: Could not transfer artifact com.aspose:aspose-cells:pom:22.9 from/to AsposeJavaAPI (Aspose Repository Browser /java/repo/): authorization failed for https://repository.aspose.com/repo/com/aspose/aspose-cells/22.9/aspose-cells-22.9.pom, status: 403 Forbidden → [Help 1]

20

@henrycslai02 Thank you for your feedback.

21

we just had a successful build! Thank you very much!

1 Like