D4Science Infrastructure

Please @fabio.sinibaldi@isti.cnr.it could you check if the configuration schema is ok for you?

Seems ok to me.

@fabio.sinibaldi@isti.cnr.it can you provide the maven data to fetch the sdi-service app?

Andrea Dell'Amico wrote:

@fabio.sinibaldi@isti.cnr.it can you provide the maven data to fetch the sdi-service app?

<groupId>org.gcube.spatial.data</groupId>
<artifactId>sdi-service</artifactId>
<version>1.0.0-4.4.0-146794</version>

The service is running only under root-vo scope: "/gcube" but the request is to run in all gcube scopes.
Please, could you add the missing scopes?

It's running with

<authorizeChildrenContext>true</authorizeChildrenContext>

If that's not what you want, please list the needed scopes. Or maybe it's running the wrong smartgears version?

Andrea Dell'Amico wrote:

It's running with

<authorizeChildrenContext>true</authorizeChildrenContext>

If that's not what you want, please list the needed scopes. Or maybe it's running the wrong smartgears version?

It is perfect for me. You should only add the following VO scopes:

/gcube/devsec
/gcube/devNext
/gcube/preprod

remember also to add the preproduction key. Thanks.

Done. I also removed the http -> https redirection. We verified that some java clients fail when the redirection is active, so we will need to check each case.

I've checked the service: the service is running correctly but we need also to add the "/gcube" scope.
Now the service is running only at VO level and the root-VO scope is missing in the container.xml file.

Could you add the /gcube token to the container, please?

Done.