Service Authentication

The high performance access to services providing COSMOS layers is made available through the simple retrieval of URLs targeting respective services.

Once the service URLs are fetched, there is no more need for further authentication and users are free to use their favourite library to enjoy the smooth experience of COSMOS integration!

Request Service URLs

GET https://<user>:<password>@p20.cosmos-project.ch/urlrequest

Respective service URLs can be retrieved using a BASIC authentication over HTTPS.

Path Parameters

Name	Type	Description
<user>:<password>	string	user and password for authentication

200 JSON response containing all available services for a respective user.

{
    pathrequest:"XXXXXXXXXXXXXXXXXXX",
    boundary:"XXXXXXXXXXXXXXXXXXX",
    staterequest:"XXXXXXXXXXXXXXXXXXX",
    pathrequest_cosmos20alps:"XXXXXXXXXXXXXXXXXXX",
    cosmos500:[
        {
            "name":"exosnow_map500",
            "url":"XXXXXXXXXXXXXXXXXXX"
        }
    ],
    cosmos20:[
        {
            name:"europealps",
            url:"XXXXXXXXXXXXXXXXXXX"
        },
        {
            name:"usarockies",
            url:"XXXXXXXXXXXXXXXXXXX"
        },
        {
            name:"usasierra",
            url:"XXXXXXXXXXXXXXXXXXX"
        },
        {
            name:"centrehimalaya",
            url:"XXXXXXXXXXXXXXXXXXX"
        },
        {
            name:"westhimalaya",
            url:"XXXXXXXXXXXXXXXXXXX"
        }
    ],
    beta:[
        {
            name:"sd_usasierra",
            url:"XXXXXXXXXXXXXXXXXXX"
        },
        {
            name:"sd_usarockies",
            url:"XXXXXXXXXXXXXXXXXXX"
        
        },
        {
            name:"age_alps",
            url:"XXXXXXXXXXXXXXXXXXX"
        }
    ],
    point_sd_rockies:"XXXXXXXXXXXXXXXXXXX",
    point_sd_sierra:"XXXXXXXXXXXXXXXXXXX"
}

It is expected that this request of URLs is made by the customer's backend to ExoLabs backend.

The customer client must never have access to the authentication credentials and should be authorized by a separate authentication between customer backend and client!

28KB

credentials_management.pdf

pdf

How credentials should be managed

Descriptions for the URL keys can be found here:

Service Listing