D4Science Infrastructure

In order to solve this issue we had to revert a change that was performed in the portlet recently. This change was creating a problem that was only visible in production environment. When the portlet was deployed in the development or in the pre-production it was working without any problem.

I will try to give a brief explanation regarding this issue. In general, the geoanalytics administration portlet performs only some simple actions i.e. discovering the active scope, user, active service instance, and afterwards it dispatches the request to the geoanalytics service that does the actual work. Furthermore, the response that the client (user's browser) receives is actually the response that the service generates. In the latest portlet update apart, from the response body we also changed the code in order to return also all the http headers that the service creates. By doing this, the portlet probably overrides some http headers that are required from the production portal to work properly. After we reverted this change, the portlet seems to work without any issues.

A new portlet configuration has been created (#9914) in order to fix this issue.

Dimitris

Yes, absolutely. I am closing the incident, please create a new ticket with the investigation (if not already open).