Policies
ODD Platform allows to manage access to resources by creating policies and attaching them to owners through roles.
Policies are described in JSON format and validated with JSON Schema.
JSON policy structure
Each policy is represented by an array of statements and each statement defines a resource with optional conditions and permissions which will be allowed for given resource.
Resource type
There are 3 possible types of policy resource:
DATA_ENTITY - Indicates, that current permissions are applied for data entity
TERM - Indicates, that current permissions are applied for dictionary term
MANAGEMENT - Indicates, that current permissions are general and work all over the platform
QUERY_EXAMPLE - Indicates, that the current permissions are applied for query examples
Each type can be combined only with associated permissions and conditions, e.g. if you describe statement for DATA_ENTITY type you can only use data entity's conditions and permissions.
Conditions
Conditions allow to specify the circumstances under which the policy grants permission.
This is an optional field and in case of absence, permissions will be applied to all resource type entries.
Conditions can't be applied to MANAGEMENT resource type
In ODD Platform we have pre-defined condition operators and fields, which can be used with these operators.
Condition operators
Currently we support next operators:
all
- all conditions under this operator must be positiveany
- at least one condition under this operation must be positiveeq
**** - condition field must be equal to some valuenot_eq
**** - **** condition field must not be equal to some valuematch
**** - condition field must match some valuenot_match
**** - **** condition field must not match some valueis
**** - **** condition field must be truenot_is
**** - **** condition field must be false
Condition fields
There are couple of pre-defined fields, which can be used in conditions. Each resource type has its own fields.
Data entity
dataEntity:oddrn
- data entity's ODDRNdataEntity:internalName
- data entity's business namedataEntity:externalName
- data entity's ingested namedataEntity:type
- data entity's type namedataEntity:class
- data entity's class namedataEntity:datasource:oddrn
- data entity's datasource ODDRNdataEntity:datasource:name
- data entity's datasource namedataEntity:namespace:name
- data entity's namespace namedataEntity:tag:name
- data entity's tag namedataEntity:owner
- data entity's ownerdataEntity:owner:title
- data entity's owner title
Term
term:name
- term's nameterm:namespace:name
- term's namespace nameterm:tag:name
- term's tag nameterm:owner
- term's ownerterm:owner:title
- term's owner title
Condition examples
User must be term's owner, term must be in Open Data Discovery namespace and have tag, which name equals to
Test
.At least one of the conditions must be positive: User must be data entity's owner OR data entity shouldn't have tag
PII
.
Permissions
Please check Permissions section for all available permissions list.
Policy examples
Data entity policy with conditions
Policy allows to update business name, description and custom metadata if user is data entity's owner and this data entity is in Open Data Discovery
namespace
Data entity policy without conditions
All actions are allowed for all data entities
Dictionary term policy with conditions
Policy allows to update term information and ownership if it has Customer
tag
Management policy
Policy allows to manage datasources, collectors and namespaces
Combined policy
Policy allows to edit term information and permits all actions for data entities from Finance
namespace.
Last updated