The project’s aim is to define rules to restrict access to SOS contents on the operation and parameter level. An introduction to the project can be found in the previous blog post. This goal is achieved with a nice graphical user interface to enable the admin user to manage permissions for a particular enforcement point, which is the connection point for the client instead of the original SOS endpoint.more >
Currently the OGC SOS allows the use of Sensor data through an inter operable interface through which a user can perform tasks, such as
1. Getting the sensor observations;
2. Getting the capabilities of the sensor;
3. Inserting, deleting and reading the observations of the sensor etc.
There is no graphical permission editor through which we can control which user role can access which parameters. Through the interface the admin should be able to grant and revoke rights for different parameters to the roles already defined. An example use case of access control would be that users assigned the role “guest” should only be able to get the capabilities of the sensor and not insert/delete observations.