Task #10861
closed
Remove VO scopes from all CKanConnector instances
Added by Roberto Cirillo over 7 years ago.
Updated about 7 years ago.
Assignee:
Costantino Perciante
Infrastructure:
Production
Description
In order to avoid to discover a gCoreEndpoint accessible only at VO level from a VRE scope, it's needed to remove the VO scopes from all the CKanConnector instances.
- Status changed from New to In Progress
I'm going to remove the VO scope from the following instances:
- ckan-sobigdata2.d4science.org (SoBigData scope)
- ckan-iotc.d4science.org (D4Research scope)
- ckan-d4s.d4science.org (D4Research scope)
a restart is needed.
- Status changed from In Progress to Feedback
- Assignee changed from Roberto Cirillo to Costantino Perciante
- % Done changed from 0 to 100
Done. Please, @costantino.perciante@isti.cnr.it could you perform a check?
- Status changed from Feedback to Closed
@roberto.cirillo@isti.cnr.it let me add a comment to this old ticket: in the last release (i.e. 4.10) a patch has been added so that the discovering of the ckan-connector is performed by asking for the one that contains the current context. In case more than one is found, the correct one will be picked.
We can readd the above VO contexts when you can.
- Related to Task #11186: Add VO scopes to the ckanConnector instances added
Also available in: Atom
PDF
Updated by 
Updated by Costantino Perciante 
