Atlas-Ranger-Tag-Security

by emaxwell-hw JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | Atlas-Ranger-Tag-Security Summary

Atlas-Ranger-Tag-Security is a JavaScript library typically used in Financial Services, Insurance applications. Atlas-Ranger-Tag-Security has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Atlas-Ranger-Tag-Security

Support

Quality

Security

License

Reuse

Support

Atlas-Ranger-Tag-Security has a low active ecosystem.

It has 5 star(s) with 4 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

Atlas-Ranger-Tag-Security has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Atlas-Ranger-Tag-Security is current.

Quality

Atlas-Ranger-Tag-Security has no bugs reported.

Security

Atlas-Ranger-Tag-Security has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

Atlas-Ranger-Tag-Security does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

Atlas-Ranger-Tag-Security releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Atlas-Ranger-Tag-Security

Get all kandi verified functions for this library.

Atlas-Ranger-Tag-Security Key Features

No Key Features are available at this moment for Atlas-Ranger-Tag-Security.

Atlas-Ranger-Tag-Security Examples and Code Snippets

No Code Snippets are available at this moment for Atlas-Ranger-Tag-Security.

Community Discussions

No Community Discussions are available at this moment for Atlas-Ranger-Tag-Security.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Atlas-Ranger-Tag-Security

Atlas uses HBase for its graph database store. If HBase is not already installed, HBase will need to be added to the cluster.
In Ambari, use the Add Servcie wizard to add HBase to the cluster.
Choose the HBase Master node and assign Region Servers to the appropriate worker nodes in the cluster.
Enable the HBase-Ranger plugin: Ambari -> Ranger -> Configs -> Ranger Plugin -> HBase Ranger Plugin -> On
Restart all neccessary components in Ambari
Atlas uses Kafka to queue messages for tracking lineage and audit usage as well as for transferring infmriaton about assets within the environment.
In Ambari, use the Add Servcie wizard to add Kafka to the cluster.
Enable the Kafka-Ranger plugin: Ambari -> Ranger -> Configs -> Ranger Plugin -> Kafka Ranger Plugin -> On
Restart all neccessary components in Ambari
Once Kafka and HBase are installed and the Ranger plugins are enabled, the Atlas service can be installed and configured.
In Ambari, use the Add Servcie wizard to add Atlas to the cluster.
At the configuration step, set the authentication parameters for Atlas. Use the following parameter values: Authentication Type: AD atlas.authentication.method.ldap.ad.url: ldap://ad01.lab.hortonworks.net:389 Domain Name: LAB.HORTONWORKS.NET atlas.authentication.method.ldap.ad.base.dn: dc=lab,dc=hortonworks,dc=net atlas.authentication.method.ldap.ad.bind.dn: cn=ldap-reader,ou=ServiceUsers,dc=lab,dc=hortonworks,dc=net atlas.authentication.method.ldap.ad.bind.password: BadPass#1
In the Advanced ranger-atlas-plugin-properties configuration page, check the box for Enable Ranger for Atlas
Restart all affected services
Troubleshooting Not enabling the Ranger Atlas Plugin may cause the Atlas Metadata Server to not start properly. If this happens, check the logs for the following error: ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException: org.apache.hadoop.hbase.coprocessor.CoprocessorException: HTTP 400 Error: atlas is Not Found
Login to Ranger as an administrative user (admin/admin)
Navigate to Access Manager -> Tag Based Policies
Click the + next to Tag to create a new tag service
Create a new tag service with a name <cluster_name>_tags (e.g. if the cluster name is sme-security-11, then use sme-security-11_tags as the name)
Click Add
Create a Hive policy in Ranger that gives both the sales and hr groups access to look at and update the sample_07 table.
In Ranger, navigate to Access Manager -> Resource Based Policies
Click on the Hive policy service
Click Add New Policy
Add a policy that gives access to the sample_07 table: Poicy Name: Sample07Policy Database: default Table: sample_07 Hive Column: * Group: hr, Permissions: select, update Group: 'sales', Permissions: select, update

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: