You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the creation of common layers in each LA spatial portal is a tedious and time cost effort. With common layers, I mean layers generic that can be used in any LA portal, like world or similar layers.
spatial-service has a copy layers functionality but this is only allowed to auth systems in a local LA portal via an api-key.
It would be interesting to have a central spatial service in the LA community that allows that copy operation to others LA portals without this restriction of with some external or different authorization. This can relief this layer creation task in other LA portals.
is the responsible of allowing or not the copy right now.
As this login is used for other layer tasks, it will be nice if this can be deactivated or configured in other way to allow these copy operations. I can send some PR if we agree in some option.
I can create a shared spatial service for this purpose and offer it its use to the LA community, but it will be nice if I can copy first some general layers (for instance from ALA).
Any comment? TIA
The text was updated successfully, but these errors were encountered:
The use of app specific keys was intended for copying between test and prod. Both the spatial key and api key will be deprecated. Noting that there are some restrictions on distributing layers, depending on the layer licence.
Thoughts
Add JWT authentication for access to permitted layers from a remote spatial-service instances.
Package individual permitted layers and push to a public S3 bucket or similar. This would be more work but result in lower impact on the server when in use.
Opted to add JWT to the copy page. The updated services require JWT with the default role ROLE_ADMIN, because not all layers will have permission for a copy. JWT is always required but it can be set to ROLE_USER for more open access to layer files.
Currently the creation of common layers in each LA spatial portal is a tedious and time cost effort. With common layers, I mean layers generic that can be used in any LA portal, like world or similar layers.
spatial-service
has a copy layers functionality but this is only allowed to auth systems in a local LA portal via anapi-key
.It would be interesting to have a central spatial service in the LA community that allows that copy operation to others LA portals without this restriction of with some external or different authorization. This can relief this layer creation task in other LA portals.
The
login
function in:spatial-service/grails-app/controllers/au/org/ala/spatial/service/ManageLayersController.groovy
Line 583 in 49af0d8
is the responsible of allowing or not the copy right now.
As this
login
is used for other layer tasks, it will be nice if this can be deactivated or configured in other way to allow these copy operations. I can send some PR if we agree in some option.I can create a shared spatial service for this purpose and offer it its use to the LA community, but it will be nice if I can copy first some general layers (for instance from ALA).
Any comment? TIA
The text was updated successfully, but these errors were encountered: