Colm,
Authorizations are in place for following operations on entity:
- create/update/delete/get
- add/update/remove of classifications
Requirements on filtering of search results based on authorizations needs to be
discussed further. If you have usecases, can you please file an Atlas JIRA?
I was able to get past the problems in the previous mail. I'm trying to use
the v2 API but authorization doesn't seem to kick in:
curl -v -u username:password
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path
This call succeeds without the Ranger plugin being called. In
Thanks Madhan. Just to clarify - ATLAS-2459 is not yet applied, so do I
have to apply this manually to get this to work?
When trying to install the current Ranger 1.1.0-SNAPSHOT plugin with the
latest Atlas SNAPSHOT distribution I see an error in application.log:
java.lang.NoClassDefFoundError:
Colm,
Perhaps you are using the Atlas service-def from Ranger master, against Atlas
from branch-0.8 (or from master before ATLAS-2459)? Earlier Atlas versions use
a different authorization model, which don't allow access controls at
instance/type levels. Please try with Atlas from master
Hi all,
I'm using the Ranger plugin to secure access to Atlas. How can I create a
policy in Ranger to allow a user access to a subset of the entities? So for
example, I want to allow "alice" to "read" all entities that have a given
type. I created an authorization policy of "type" "Table", but I
