Authorization Error (403) Appears while Using Aspose.Slides for Java

I have used licenced Aspose slides library in Java. I was working fine till last week. Now I am facing some issues in that: mainly Authentication error. I tried multiple repository in pom but each time it gave some error. I am posting 3 scenarios which I tried along with Error it is producing.

  1. With pom entry
<repositories>
  <repository>
    <id>AsposeJavaAPI</id>
    <name>Aspose Java API</name>
    <url>https://repository.aspose.com/repo/</url>
  </repository>
</repositories>

<dependency>
  <groupId>com.aspose</groupId>
  <artifactId>aspose-slides</artifactId>
  <version>19.2</version>
  <classifier>jdk16</classifier>
</dependency>

Error We are getting:

[ERROR] Failed to execute goal on project video: Could not resolve dependencies for project : Failed to collect dependencies at com.aspose:aspose-slides:jar:jdk16:19.2: Failed to read artifact descriptor for com.aspose:aspose-slides:jar:jdk16:19.2: Could not transfer artifact com.aspose:aspose-slides:pom:19.2 from/to AsposeJavaAPI (https://repository.aspose.com/repo/): authorization failed for https://repository.aspose.com/repo/com/aspose/aspose-slides/19.2/aspose-slides-19.2.pom, status: 403 Forbidden

2 . With pom entry

<repositories>
  <repository>
    <id>AsposeJavaAPI</id>
    <name>Aspose Java API</name>
    <url>https://artifact.aspose.com/repo/</url>
  </repository>
</repositories>

<dependency>
  <groupId>com.aspose</groupId>
  <artifactId>aspose-slides</artifactId>
  <version>19.2</version>
  <classifier>jdk16</classifier>
</dependency>

Error We are getting:

[ERROR] Failed to execute goal on project video: Could not resolve dependencies for project : Failed to collect dependencies at com.aspose:aspose-slides:jar:jdk16:19.2: Failed to read artifact descriptor for com.aspose:aspose-slides:jar:jdk16:19.2: Could not transfer artifact com.aspose:aspose-slides:pom:19.2 from/to AsposeJavaAPI (https://artifact.aspose.com/repo/): transfer failed for https://artifact.aspose.com/repo/com/aspose/aspose-slides/19.2/aspose-slides-19.2.pom: Certificate for <artifact.aspose.com> doesn’t match any of the subject alternative names: [repository-qa.aspose.com]

3 . With pom entry

<repositories>
  <repository>
    <id>AsposeJavaAPI</id>
    <name>Aspose Java API</name>
    <url>https://repository.aspose.com/webapp/#/artifacts/browse/tree/General/repo/</url>
  </repository>
</repositories>

<dependency>
  <groupId>com.aspose</groupId>
  <artifactId>aspose-slides</artifactId>
  <version>19.2</version>
  <classifier>jdk16</classifier>
</dependency>

Error We are getting:

[ERROR] Failed to execute goal on project video: Could not resolve dependencies for project : Failed to collect dependencies at com.aspose:aspose-slides:jar:jdk16:19.2: Failed to read artifact descriptor for com.aspose:aspose-slides:jar:jdk16:19.2: Could not transfer artifact com.aspose:aspose-slides:pom:19.2 from/to AsposeJavaAPI (https://repository.aspose.com/webapp/#/artifacts/browse/tree/General/repo/): authorization failed for https://repository.aspose.com/webapp/#/artifacts/browse/tree/General/repo/com/aspose/aspose-slides/19.2/aspose-slides-19.2.pom, status: 403 Forbidden

Please Provide some assistance as soon as possible. Any help would be appreciated.

@Anishek,
Welcome to our community! Thank you for the issue description.

This is a known issue recently. Please carefully read this thread on Aspose.Slides forum. We apologize for any inconvenience.

@Anishek

Our repository URL is https://repository.aspose.com/repo/. This is only accessible through Maven our Gradle Clients. You can explore our repository through https://repository.aspose.com/.

Could not transfer artifact com.aspose:aspose-slides:pom:19.2 from/to AsposeJavaAPI (https://repository.aspose.com/repo/): authorization failed for

Kindly flush DNS cache for your machine and then try again. This issue will be resolved. If you are using GitHub Actions. Please add this step in you workflow.

  • name: Clear DNS Cache
    run: |
    sudo systemd-resolve --flush-caches

You can see full GitHub Actions yml file at java-hello-world-maven/.github/workflows/maven.yml at master · farooqsheikhpk/java-hello-world-maven · GitHub.

Related GitHub Log: https://snipboard.io/UW751n.jpg

Feel free to reach me for any issue related to it. Thanks.

@farooq.sheikh

This solution is not working for us as we have Azure pipelines setup for building and deployment and each time maven dependencies gets downloaded directly from repository url . After trying the command which you suggested im git hub , I got error saying

Unexpected value ‘name’

Please refer the below attached screenshot for changes we tried

image.png (4.2 KB)

Can you please suggest any other alternative?
What about migration to new server that was going on ? By when can it be expected to be completed ?

@Anishek,
I’ve requested our developers to inform the state of our repositories. We will let you know as soon as possible.

@Anishek

Please share your Azure VM IP Address through which you are accessing repository.aspose.com. I will request our hosting team to do further investigation on it.

Feel free to reach us for any issue related to it. Thanks

@Anishek

Did you get chance to run your Azure pipelines again? My Azure pipeline is working with Aspose Repository - https://repository.aspose.com/repo/.

Feel free to reach us for any issue related to it.

1 Like

@farooq.sheikh

Today again getting some error with Aspose

Failed to execute goal on project video: Could not resolve dependencies for project com.aq.springboot.ca.video:video:jar:0.0.1-SNAPSHOT: Could not find artifact com.aspose:aspose-slides:jar:jdk16:19.2 in AsposeJavaAPI (https://repository.aspose.com/repo/) → [Help 1]

Can you please me in resolving this ?

@Anishek,
Please share a simple project that reproduces the error you are experiencing.

I am good with this issue now . This issue was resolved .

@Anishek,
We are glad to know that the issue has already resolved on your end. Thank you for using Aspose.Slides.

@Anishek

May I know how did you resolved this issue?

Thanks!!

@ramesh676,
Thank you for contacting support. Please describe the issue you are experiencing with environment details in a new forum thread. We will do our best to resolve it.

Hi @andrey.potapov @farooq.sheikh

I am again getting similar error now

Failed to execute goal on project presentation_generator: Could not resolve dependencies for project com.xxx:xx:jar:0.0.1-xxx: The following artifacts could not be resolved: com.aspose:aspose-slides:jar:jdk16:22.1, com.aspose:aspose-cells:jar:16.11.0: Could not transfer artifact com.aspose:aspose-slides:jar:jdk16:22.1 from/to AsposeJavaAPI (Aspose Repository Browser /java/repo/): authorization failed for https://repository.aspose.com/java/repo/com/aspose/aspose-slides/22.1/aspose-slides-22.1-jdk16.jar, status: 403 Forbidden → [Help 1]

POM entry :

<dependency>
			<groupId>com.aspose</groupId>
			<artifactId>aspose-slides</artifactId>
			<version>22.1</version>
			<classifier>jdk16</classifier>
		</dependency>

repository used

<repositories>
		<repository>
			<id>AsposeJavaAPI</id>
			<name>Aspose Java API</name>
			<url>https://repository.aspose.com/java/repo/</url>
		</repository>
	</repositories>

Please look into the issue asap and guide me to resolve this .

@Anishek,

I tested in a simple eclipse maven project and it works absolutely fine on my end. The Aspose.Slides for Java 22.1 jar is extracted fine, see the screenshot for your reference.
sc_shot1.png (178.0 KB)

@amjad.sahi

It’s working even for me in local setup , but its failing when I try to deploy this .
Can you tell me what kind of authorization it is expecting ?

try renaming your .m2 folder and it will fail even in your local

@pankajkundlia I tried even that …deleted that aspose dependency from m2 folder…still it got downloaded again and worked fine .

I figured the issue for my case.

we were pointing to repository.aspose.com while the working config is releases.aspose.com

now I am confused how it worked till last week.

@Anishek,

We have informed the responsible team (hosting team). According to the 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”.

We are working with our hosting team in order to resolve the problem soon. Please accept our apologies for any inconvenience. We will update you once any update is available.