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

@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.

@Anishek,

We increased the limit to two requests per second. Could you please recheck whether the problem still persists for you.

@amjad.sahi Yes , its working now . Thanks a lot .

@pankajkundlia When you hit Aspose Repository Browser /java/repo/ , it actually redirects to https://releases.aspose.com/java/repo/ . So both meant the same thing .

for our use case. It started failing on GitHub Actions with repository.aspose.com but works with releases.aspose.com

@Anishek,

It is nice to know that your issue is sorted out now. Please feel free to write us back if you have further queries or comments.