FROST-Server

The FROST-Server allows for managing sensor data and their meta data, i.e. description of things. In addition, it enables real-time data processing, storage, and access. The Server implements and provides the SensorThings API standardized by the OGC.

Access to the FROST-Server resources is controlled using Keycloak tokens, ensuring secure access to sensor data and related functionalities.

The FROST-Server is a headless service that can be configured using an extensive OGC SensorThings REST API.

The API base path for the FROST-Server is https://api.<domain>/context/sensorthings/. Metadata and measured data can be added to the FROST-Server using this API, too.

For configuration, a REST testing tool like Postman can be used. With Postman, users can easily interact with the FROST-Server APIs to add sensor data, manage things, and perform other actions as required.

User Roles

The platform enables project-level permissions in FROST for fine-grained access control.

For access across all dataspaces (FROST projects), accounts can be assigned these roles in Keycloak:

• read
• create
• update
• delete
• admin

For dataspace-level access, create the corresponding roles for each dataspace in Keycloak with the access type separated by two underscores:

• ds_traffic__create
• ds_traffic__read
• ds_traffic__write
• ds_traffic__update
• ds_traffic__delete
• ds_energy__create
• ...

For an architectural overview over this authorization concept, go to Data spaces in FROST.