Difference between revisions of "GCube-Enabled geo-services"
(→Small deployment) |
(→Well suited use cases) |
||
| Line 39: | Line 39: | ||
=== Well suited use cases === | === Well suited use cases === | ||
| + | Well suited use cases addressed by this technology are : | ||
| + | |||
| + | * Direct interaction with involved geo-service's REST API | ||
| + | * Embedding of geo-service's GUI in a gCube Portal | ||
| + | |||
=== Less suited use cases === | === Less suited use cases === | ||
Latest revision as of 17:55, 20 November 2017
Contents
Overview
By saying GCube-Enabled geo-services we identify all services involved in an SDI that understand and exploit gcube authorization framework. While dealing with these services, authentication and authorization of http(s) requests rely on the presence of the gcube-token just as like as any other gCube Service, relieving users and applications from dealing with :
- non standard authentication APIs
- specific instance credentials use
Key Features
GCube-Enabled geo-services is a technology provided by gCube offering the following key features on geo-services :
- Automatic geo-service authentication of http(s) requests declaring a valid gcube-token
Design
Philosophy
Geo-services are typically third-party software with no knowledge of gCube technology, thus all of these services implements their own approach in terms of security. gCube-enabled geo-services represents a wrapping layer around geo-services, harmonizing the security level of these technologies with the gCube Authorization Framework. Since Geo-services are used and integrated in other systems that might not be aware of gCube Authorization Framework, it is crucial that the layer introduced by gCube-enabled geo-services is absolutely transparent to non-gCube applications.
Architecture
The aim of gCube-enabled geo-services is to intercept incoming http(s) requests under certain conditions, and make them authorized by the underlying geo-service. The chosen approach is to provide a filter servlet which for every and each request :
- if the request doesn't declare a gcube-token do nothing. Else
- Retrieves the credentials <CREDENTIALS> for that token ( via the SDI-Service)
- Does the required operation(s) in order for the incoming request to be authenticated as <CREDENTIALS>
The picture below describes the architecture of a gCube-enabled GeoServer.
Deployment
Large deployment
Small deployment
This feature is distributed as a set of libraries, each one serving a particular technology. They are typically distributed as a single maven artifact. Since they deal with the specific logic implemented by the underlying geo-service, their deployment may vary. Please refer to specific section in wiki docs about the administration of involved geo-service. gCube-enabled geo-services provided so far are :
- GeoServer (see Install and Configure GeoServer for details)
- GeoNetwork (see GeoNetwork Configuration for details)
Use Cases
Well suited use cases
Well suited use cases addressed by this technology are :
- Direct interaction with involved geo-service's REST API
- Embedding of geo-service's GUI in a gCube Portal
