Difference between revisions of "GCube-Enabled geo-services"
From Gcube Wiki
(→Overview) |
|||
| Line 5: | Line 5: | ||
* non standard authentication APIs | * non standard authentication APIs | ||
* specific instance credentials use | * 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 === | ||
| + | === Architecture === | ||
| + | |||
| + | == Deployment == | ||
| + | |||
| + | === Large deployment === | ||
| + | === Small deployment === | ||
| + | |||
| + | == Use Cases == | ||
| + | |||
| + | === Well suited use cases === | ||
| + | === Less suited use cases === | ||
Revision as of 16:32, 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
