Skip to content
This repository was archived by the owner on Sep 19, 2024. It is now read-only.

Home

Jump to bottom
Dushyant Sabharwal edited this page Aug 15, 2014 · 9 revisions

Welcome to 52 North's Timeseries Protector Wiki

About the Project

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 here. 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. Below are the resources which contain information about every bit and piece of the project

Getting Started with Timeseries Protector

So after the user has successfully installed and configured the application the next steps describe how to perform various actions and achieve goals

Creating a new Permission Set

A Permission set is defined as a set of permissions which restrict the use of a particular SOS instance's capabilities by allowing particular actions for the tagged user roles which are part of a permission. From the above definition it is quite evident that we need the following things for a successful application of a permission set

  • URI of the SOS end point whose capabilities are intended to be restricted
  • Domain of the configured user roles which are to be restricted
  • Defined permissions specifying the allowed operations for the selected user roles

The application may or may not come up with a default permission set depending upon how is it configured. To learn more refer to the configuration details. Below steps explain how to create a permission set

  1. Click on the + button on the Timeseries Permission Manager page which redirects the user to a new page which looks like below Create permission set All the fields which are * marked are mandatory and user has to provide an appropriate value. Lets take each field at a time

Permission Set Name

This has to be unique as it is used to identify a permission set. User will be warned if at all an existing permission set's name is entered

Action Domain

This is a dropdown which contains pre-configured SOS endpoints present in the editor-config.xml.

Advance Settings

This section contains Resource Domain and Subject Domain fields which are not mandatory. Resource Domain if not specified by the user explicitly is assumed to be same as the Action Domain. For Subject Domain a user can enter his custom values also Subject Domain Widget

Clone this wiki locally