Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
Master
-
7.3.x
-
Committed
-
5
-
3
-
Regression Bug
Description
Description
Liferay JSON Web Services API calls no longer work, when the portal property: portal.proxy.path is configured.
Steps to reproduce
- Configure a reverse proxy (e.g. using Apache)
<VirtualHost *:80> ServerName localhost ProxyPreserveHost On <location /portal> ProxyPass "http://localhost:8080" ProxyPassReverse "http://localhost:8080" </location> </VirtualHost>
- Prepare a clean bundle with the following portal property:
portal.proxy.path=/portal web.server.http.port=80
- Start Liferay
- Navigate to http://localhost/portal
- Login as admin user
- Navigate to http://localhost/portal/api/jsonws
- Click get-companies under COMPANY
- Click Invoke
Expected results
Result displays an array with the default company as an entry, example:
[ { "active": true, "companyId": "20097", "createDate": 1656362181077, "homeURL": "", "industry": "", "legalId": "", "legalName": "", "legalType": "", "logoId": "0", "maxUsers": 0, "modifiedDate": 1656362181077, "mvccVersion": "1", "mx": "liferay.com", "name": "Liferay", "sicCode": "", "size": "", "system": false, "tickerSymbol": "", "type": "", "userId": "0", "userName": "", "webId": "liferay.com" } ]
Actual results
Result displays empty results and a 403 is thrown for the invoked request, example:
{}
Attachments
Issue Links
- is caused by
-
LPS-129496 AuthVerifier configurations are not working when portal is running under a custom context
- Closed
- Testing discovered
-
LPS-159215 Failed to load API definition when when using portal.proxy.path
- Closed
-
LPS-159485 AuthVerifierPipeline does not need to know about proxy path
-
- Closed
-
- mentioned in
-
Page Loading...