Difference between revisions of "GCube-Enabled geo-services"
From Gcube Wiki
(Created page with "Category:gCube Features == Overview == By saying '''GCube-Enabled geo-services''' we identify all services involved in an SDI that ''understand'' and ''exploit'' gcube aut...") |
|||
| Line 1: | Line 1: | ||
[[Category:gCube Features]] | [[Category:gCube Features]] | ||
== Overview == | == Overview == | ||
| − | By saying | + | 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 | ||
Revision as of 16:27, 20 November 2017
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
