1. Home
  2. Development
  3. RE: Accessing default Liferay /api/axis services

RE: Accessing default Liferay /api/axis services

Olaf Kock, modified 3 Years ago.
Accessing default Liferay /api/axis services
New Member Posts: 2 Join Date: 7/29/22 Recent Posts

Hello,

I have tried last version of Liferay Community Edition Portal 7.4.3.33 CE GA33 (Cavanaugh / Build 7403 / July 15, 2022)

I only started the Liferay without any customizations or configurations, just using Hypersonic db and I tried to access default Liferay soap services from http://localhost:8080/api/axis but they are not available. Portal main page just loads. I use JDK: "11.0.15"

Any idea why? Does it required to be enabled from portal-ext.properties?

Thx,
Ova

 

 

 

thumbnail
Olaf Kock, modified 3 Years ago.
RE: Accessing default Liferay /api/axis services
Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

If I'm not mistaken, SOAP was deprecated a while ago, and might be gone by now.

The JSONWS API would still be there, and - of course - the Headless APIs (through REST)

Olaf Kock, modified 3 Years ago.
RE: RE: Accessing default Liferay /api/axis services
New Member Posts: 2 Join Date: 7/29/22 Recent Posts

Thanks for your reply. Is there any "hello world" JSONWS example to work wirth LF 7.4.3 or similar? I could not get a basic service running + an extender.

Thx,

Ova

 

thumbnail
Olaf Kock, modified 3 Years ago.
RE: RE: Accessing default Liferay /api/axis services
Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

From slack (which will disappear sooner or later, so I'll copy it here)

Anyone else getting 403 forbidden errors in the JS console on the JSONWS when trying to use categories in a range of assets? How to resolve?

yes, I got that error in one portal. It was caused by a  missing/wrong configuration for the "Portal Session Auth Verifier".

In System Settings > API Authentications there was an entry missing for Portal Sessions allowing /api/json*,/api/jsonws*,/c/portal/json_service*.

Credits go to Dominik Marks (ignore my name on those lines, which seems to be added here due to the use of blockquote formatting - filing an issue)

In general, I'd rather watch out for anything "Headless", e.g. proper REST. That interface is more stable, versioned, and easier to access with current tooling.