Skip to content

son‐access

Luís Conceição edited this page Aug 31, 2017 · 3 revisions

The son-access component provides a secured connection based on authentication and authorization processes between SDK end-users and the Service Platform, which offers possibilities to use end-user credentials and JSON Web Tokens to access the Service Platform features such the unified SP Catalogue and enable end-users to submit and request package files and descriptors from the SP Catalogue.

This tool is internally divided in sub-components following different functionalities, detailed in the following sections.

Sub-components

Access

This sub-component implements the security layer (authentication and authorization of end-users) to the communications with the Service Platform and performs automatically required authentication processes for each interaction. The following features are highlighted:

  • Full integration with Service Platform Gatekeeper API to perform authentication and authorization processes
  • Integrated with son-cli components, it supports shared use of the access token between different CLI tools for the same end-user
  • Access token included in each message header to authenticate and authorize developers
  • Full integration with Service Platform Gatekeeper API to perform authentication and authorization processes

Push

It enables submission of Package files generated by son-package including Service and Function descriptors to the SP Catalogue. The Gatekeeper API requires package files as input, however the son-access is still able to submit descriptors. This is useful in order to be able to connect the son-access to other platforms that accepting this input element or son-emu.

Pull

This sub-component is fully integrated with the other son-access sub-components, and it also works along with son-workspace SDK tool in order to retrieve package files (son-packages), service and functions descriptors, from the SP and store them in the end-user configured file system or storage system according to their preferences set in the workspace configuration file. This component is able to downstream SP Catalogue contents using access sub-component as interface, authenticating the developer and providing the required access token to the requests.

Clone this wiki locally