Assistant: Janet Brooks - jsbrook...@uk.ibm.com
From: Madhan Neethiraj <mad...@apache.org>
To: "dev@atlas.apache.org" <dev@atlas.apache.org>
Date: 16/02/2018 02:23
Subject: Re: Metadata security policies examples
Neethiraj <mad...@apache.org>
To: "dev@atlas.apache.org" <dev@atlas.apache.org>
Date: 16/02/2018 02:23
Subject: Re: Metadata security policies examples
Mandy,
> edit access is limited to the user identified in the createdBy property.
It will be possible to suppo
.
From: Madhan Neethiraj <mad...@apache.org>
To: "dev@atlas.apache.org" <dev@atlas.apache.org>
Date: 16/02/2018 02:23
Subject: Re: Metadata security policies examples
Mandy,
> edit access is limited to the user identified in the createdBy prope
Mandy,
> edit access is limited to the user identified in the createdBy property.
It will be possible to support authorization as above. However, there are few
issues to be aware of in such approach. For example:
- 'createdBy' property may not be present in all entity-types
- the username in
Hello Madhan,
I was thinking through our common use cases for metadata security. For
most metadata entities and relationships, we would want to enforce that
metadata is readable by logged on users but edit access is limited to the
user identified in the createdBy property.
Then we have
