Page tree
Skip to end of metadata
Go to start of metadata



Overview

This document details the steps involved in Installing latest version of Apache Incubator Ranger independently on RHEL / Ubuntu / SUSE / Debian OS.

Installation of Ranger includes the following. Plan to install and configure in the same order.

Ranger Admin Portal - This is the UI portal and RESTful server for managing policies, users and groups. It also contains the UI interface for Audit queries and adhoc reports.

Ranger UserSync - This is a standalone server with dual purpose. It is used to synchronize the users/groups from Unix system or LDAP into RangerAdmin. This standalone process can be also used as an authentication server for RangerAdmin to use the linux user/password for login into RangerAdmin.

Ranger KMS - This service provides key management for Hadoop HDFS Encryption (TDE). It is highly scalable and provides access control and auditing. This service is optional and only needed if you are planning to use HDFS TDE.

Component Plugins - Ranger provides authorization and auditing for the following Apache projects. Apache Ranger version 0.5.x is compatible with only the component versions mentioned below. You need to install and enable the plugins for only does components you want enable Ranger Authorization and Auditing.

 

Dependent Services: Refer to Prerequisites section

 

Prerequisites


ProductVendorsPurpose
JDK

OpenJDK 1.7

SunJDK 1.7

Run RangerAdmin and RangerKMS
RDBMS

MySQL 5.7+

Oracle - latest

Postgres - latest

SQL Server - latest

  1. Storing policies
  2. Storing Ranger Users and Groups
  3. Storing Audit Logs (Optional)
Solr

Apache Solr - 5.2.1+

  1. Store Audit Logs
  2. Used by RangerAdmin Portal to search AuditLogs
HDFSApache HDFS - 2.7+
  1. Store Audit Logs (Optional, but recommended)
Kerberos

MIT

Microsoft AD

Even though not mandatory for installing and using Ranger, it is strongly recommended to enable Kerberos in your Hadoop. This ensures all requests are authenticated, which is very important for authorization and auditing. Without Kerberos, users would you be able to impersonate other users and workaround any authorization policies

Installation Instructions

Since Apache Ranger is still an incubating project, binary distribution is still not available. To install Apache Ranger, you will need to build from source. The below instructions is to build on RHEL or CentOS 6+ Linux server.

Preparing to install

You need to login as root or will need "sudo" access to install some of the build tools.

Install Maven

Required to build the project

Install git

Required to download the source code from Apache Ranger git repository

Install gcc

This is optional and required if you are using your Linux /etc/passwd to authenticate to login into Ranger Admin. It is not required if you are using RangerAdmin local user/password or LDAP for authentication.

Install MySQL

Ranger support MySQL, Oracle,  MS SQL and PostGress RDBMS.  Please refer to official installation from the vendor site. This section gives quick instructions about how to install MySQL. For full detail please refer to http://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en.

If you using RedHat or CentOS, find out the version of your distribution

Go to the this site http://dev.mysql.com/downloads/repo/yum and download the release package for your platform.


You will also need to download the MySQL JDBC. Download it from the this site http://dev.mysql.com/downloads/connector/j and unzip/untar it. You should copy the .jar to a common location where everyone can access it. E.g. /usr/share/java

Build Ranger Admin from source 

Clone the ranger source code

Build the source 

Verify all the tar files under the target directory:

 

 

Install Steps for Ranger Policy Admin on RHEL/CentOS

Lay down the build into appropriate places.

 

Install and configure Solr or SolrCloud

Ranger stores audit logs in Solr. The RangerAdmin UI depends on Solr for running adhoc queries on audit logs. Please refer to the following link to Install and Configure Solr for Ranger Audits

 

2. Update the install.properties 

2.1 Configure database properties. For MySQL, you will need to use the root password that you had picked while installing mysql.

c.The install process would create a couple of users in the database for storing administration and audit information, pick passwords for those too. With my choices here’s how the relevant sections in the install.properties file looks like.

d. Ranger allows you to get fancier with security and authentication mode but for now let’s just leave rest of the things in this file as they are.

e. Once all the required properties are updated run the setup.sh script

f. The setup script will setup the db user/tables using the properties in install.properties and also lay down the binaries and setup initd scripts. 

g. Once installed Ranger Admin service can be started by issuing the following command

h. The ranger-admin script supports the following options:

Start the Ranger Admin service : ranger-­admin start

Stop the Ranger Admin service : ranger-admin stop 

Restart the Ranger Admin service : ranger-­admin restart

i.You can verify by visiting the external URL of the server using browser, for example: 

http://<Host_Address>:6080


Configuring Ranger Admin Authentication Modes

Ranger Admin supports three Authentication methods namely : Active Directory, LDAP and Unix.

  •  ACTIVE DIRECTORY

      To enable active directory authentication on Ranger Admin, you need to configure following properties in install.properties

PROPERYVALUEDESCRIPTION
authentication_methodACTIVE_DIRECTORYThe authentication method to use.

xa_ldap_ad_domain

E.g. : “example.com”

 
xa_ldap_ad_url

E.g. : “ldap://127.0.0.1:389”

Ldap server URL.
xa_ldap_ad_base_dn

E.g. : “DC=example,DC=com”

The Distinguished Name (DN) of the starting point for directory server searches.
xa_ldap_ad_bind_dn

E.g. :
“CN=Administrator,CN=Users,DC=example,DC=com”

Full distinguished name (DN), including common name (CN), of an Active Directory user
account that has privileges to search for users. This user account must have at least
domain user privileges.
xa_ldap_ad_bind_password

Password for the account that can search for users.

 
xa_ldap_ad_referral

Possible values are “ignore ”, “follow ” and “throw ”. Default value is “follow”.

When searching a directory, the server might return several search results, in addition to a few continuation references that show where to obtain further results. These results and references might be interleaved at the protocol level. When property is set to "follow", the AD service provider processes all the normal entries first, before following the continuation references. When this property is set to "throw", all of normal entries are returned in the enumeration first, before the ReferralException is thrown. By contrast, a "referral" error response is processed immediately when property is set to "follow" or "throw".

       

  • LDAP
PROPERTYVALUEDESCRIPTION
authentication_methodLDAP 
xa_ldap_url

E.g. : "ldap://127.0.0.1:389"

Ldap server URL
xa_ldap_userDNpatternE.g. : "uid={0},ou=users,dc=example,dc=com" User DN pattern is expanded when a user is being logged in. For example, if the user
‘ldapadmin’ attempted to log in, the LDAP Server would attempt to bind against the DN
‘uid=ldapadmin,ou=users,dc=example,dc=com’ using the password the user provided
 xa_ldap_groupSearchBase

E.g. : "dc=example,dc=com"

Defines the part of the directory tree under which group searches should be performed.
xa_ldap_groupSearchFilter E.g. : "(member=cn={0},ou=users,dc=example,dc=com)" The filter which is used to search for group membership. The default is uniqueMember={0}, corresponding to the groupOfUniqueNames LDAP class. In case of Ranger authentication, the substituted parameter is the full distinguished name of the user. The parameter {0} can be used if you want to filter on the login name.
 xa_ldap_groupRoleAttributeE.g. : "cn" The attribute which contains the name of the authority defined by the group entry.
 xa_ldap_base_dnE.g. : " dc=example,dc=com" The Distinguished Name (DN) of the starting point for directory server searches.
 xa_ldap_bind_dnE.g. : "cn=ldapadmin,ou=users,dc=example,dc=com" Full distinguished name (DN), including common name (CN), of an LDAP user account that has privileges to search for users.
xa_ldap_bind_password Password for the account that can search for users. 
 xa_ldap_referral

Default value is “follow”. Possible values are “ignore ”, “follow ” and “throw ”.

 
When searching a directory, the server might return several search results, in addition to a few continuation references that show where to obtain further results. These results and references might be interleaved at the protocol level. When property is setto "follow", the AD service provider processes all the normal entries first, before following the continuation references. When this property is set to "throw", all of normal entries are returned in the enumeration first, before the ReferralException is thrown. By contrast, a "referral" error response is processed immediately when property is set to "follow" or
"throw".
  • UNIX
PROPERTYVALUEDESCRIPTION
authentication_methodUNIX  
remoteLoginEnabledtrue 
authServiceHostName

E.g. : localhost

An Address of host where unixauth service is running
authentication_method5151Port number on which unixauth service is running. default is 5151

Configuring Ranger Admin HA Mode 

  1. Follow the ranger admin install steps above to install it on multiple hosts 
  2. Make sure to use the same configuration and policy DB details 
  3. Configure a load balancer (Software e.g. Apache httpd or hardware load balancer could be used) and note down the load balancer URL. Configuration details are outside the scope of this document. 
  4. Update the policy manager external URL in all the clients of Ranger Admin (Ranger UserSync and Ranger plugins) to point to the load balancer URL.
  5. Restart all the clients (Ranger UserSync and Ranger plugins).

Installing the Ranger UserSync Process

  •  We’ll start by extracting out build at the appropriate place. 
  • Edit the install.properties file and fill out relevant information.

  •  Now run the setup.sh command to install the usersync

h. The ranger-usersync script supports the following options:

Start the Ranger Usersync service : ranger-usersync start

Stop the Ranger Usersync service : ranger-usersync stop

Restart the Ranger Usersync service : ranger-usersync restart


Configuring Ranger UserSync process to use LDAP/AD server

  • To Sync LDAP or AD users following properties should be configured in install.properties file before executing the setup.sh.
PROPERTYDESCRIPTIONCOMMENTS
SYNC_LDAP_USER_OBJECT_CLASSObject class to identify user entries.  Please customize the value to suit your deployment. 
SYNC_LDAP_USER_SEARCH_FILTER

Optional additional filter constraining the users selected for syncing.

Please customize the value to suit your deployment. 
SYNC_LDAP_USER_NAME_ATTRIBUTE

Attribute from user entry that would be treated as user name

Please customize the value to suit your deployment. 
SYNC_LDAP_USER_GROUP_NAME_ATTRIBUTE

Attribute from user entry whose values would be treated as group values to be pushed into Policy Manager database. You could provide multiple attribute names separated by comma.

Please customize the value to suit your deployment. 
SYNC_LDAP_USERNAME_CASE_CONVERSION

UserSync ­ Case Conversion Flags.

Possible values:  none, lower, upper 
SYNC_LDAP_GROUPNAME_CASE_CONVERSION

UserSync ­ Case Conversion Flags.

Possible values:  none, lower, upper
SYNC_GROUP_SEARCH_ENABLED

Do we want to do ldapsearch to find groups instead of relying on user entry attributes. valid values: true, false

Any value other than true would be treated as false
SYNC_GROUP_USER_MAP_SYNC_ENABLED

Do we want to do ldapsearch to find groups instead of relying on user entry attributes and sync memberships of those groups valid values: true, false. any value other than true would be treated as false.

 
SYNC_GROUP_SEARCH_BASE

Search base for groups. overrides value specified in SYNC_LDAP_SEARCH_BASE,SYNC_LDAP_USER_SEARCH_BASE.
If a value is not specified, takes the value of SYNC_LDAP_SEARCH_BASE
if SYNC_LDAP_SEARCH_BASE is also not specified, takes the value of
SYNC_LDAP_USER_SEARCH_BASE

 
SYNC_GROUP_SEARCH_SCOPE

Search scope for the groups, only base, one and sub are supported values

Any value other than true would be treated as false
SYNC_GROUP_OBJECT_CLASS

Object class to identify group entries. Default value: groupofnames

Any value other than true would be treated as false
SYNC_LDAP_GROUP_SEARCH_FILTER

Optional additional filter constraining the groups selected for syncing. Default value is empty.

Please customize the value to suit your deployment. 
SYNC_GROUP_NAME_ATTRIBUTE 

Attribute from group entry that would be treated as group name.

Please customize the value to suit your deployment.  
PSYNC_GROUP_MEMBER_ATTRIBUTE_NAME

Attribute from group entry that is list of members. Default value: member.

 
SYNC_PAGED_RESULTS_SIZE

Page size for paged results control. Search results would be returned page by page with the specified number of entries per page default value: 500

 
SYNC_PAGED_RESULTS_ENABLED

Do we want to use paged results control during ldapsearch for user entries.

Valid values: true, false. default value: true

Any value other than true would be treated as false. If the value is false, typically AD would not return more than 1000 entries.

Please customize the value to suit your deployment. 
SYNC_SOURCESync source, “ldap” should be used for both LDAP or AD user syncing. 
SYNC_LDAP_URLURL of source ldap server. Must specify a value if SYNC_SOURCE is "ldap" 
SYNC_LDAP_BIND_DNLdap bind dn used to connect to ldap and query for users and groups. Must specify a value if SYNC_SOURCE is ldap. 
SYNC_LDAP_BIND_PASSWORDLdap bind password for the bind dn specified above. Please ensure read access to this file is limited to root, to protect the password. Must specify a value if SYNC_SOURCE is ldap unless anonymous search is allowed by the directory on users and group. 
SYNC_LDAP_SEARCH_BASESearch base for users and groups  
SYNC_LDAP_USER_SEARCH_BASESearch base for users, overrides value specified in SYNC_LDAP_SEARCH_BASE. Must specify a value if SYNC_SOURCE is ldap and SYNC_LDAP_SEARCH_BASE is empty. 
SYNC_LDAP_USER_SEARCH_SCOPESearch scope for the users, supported values : base, one and sub. 

 

  Table: LDAP/AD Properties with sample values 

PROPERTIES NAMESAMPLE VALUES FOR LDAP USER-SYNCSAMPLE VALUES FOR AD USER-SYNC
SYNC_LDAP_URL ldap://127.0.0.1:389 ldap://127.0.0.1:389 
SYNC_LDAP_BIND_DN 

cn=ldapadmin,ou=users,dc=example,dc=com

cn=adadmin,cn=Users,dc=exa
mple,dc=com

SYNC_LDAP_BIND_PASSWORD secret secret 
SYNC_LDAP_SEARCH_BASE dc=example,dc=com dc=example,dc=com 
SYNC_LDAP_USER_SEARCH_BASEou=users,dc=example,dc=com dc=example,dc=com 
SYNC_LDAP_USER_SEARCH_SCOPE sub sub 
SYNC_LDAP_USER_OBJECT_CLASSperson person 
SYNC_LDAP_USER_SEARCH_FILTER (objectcategory=person) 
SYNC_LDAP_USER_NAME_ATTRIBUTEuid or cn sAMAccountName 

SYNC_LDAP_USER_GROUP_NAME_AT
TRIBUTE

memberof,ismemberof memberof,ismemberof 

SYNC_LDAP_USERNAME_CASE_CONV
ERSION

lower lower 

SYNC_LDAP_GROUPNAME_CASE_CON
VERSION

lower lower 
SYNC_GROUP_SEARCH_ENABLED false false 

SYNC_GROUP_USER_MAP_SYNC_ENA
BLED

false false 
SYNC_GROUP_SEARCH_BASE ou=groups,dc=example,dc=com dc=example,dc=com 
SYNC_GROUP_SEARCH_SCOPE subsub
SYNC_GROUP_OBJECT_CLASS groupofnames groupofnames 
SYNC_LDAP_GROUP_SEARCH_FILTER  
SYNC_GROUP_NAME_ATTRIBUTE cncn

SYNC_GROUP_MEMBER_ATTRIBUTE_
NAME

member member 
SYNC_PAGED_RESULTS_ENABLED true true 
SYNC_PAGED_RESULTS_SIZE 500500

Installing Apache Hadoop

  • If java is not there, install JDK first.
  • Make a note of the location where you installed Apache Hadoop. Here I assume that you have installed it in
  • Create a user under which we could install and ultimately run the various hadoop processes. And login as that user.

If you get the group exists error, try the following command:

  • Create a hdfs user :

 

 

 

 

 

 

  • Follow the instruction on the site and install Apache Hadoop

Enabling Ranger HDFS Plugins

a. We’ll start by extracting our Ranger plugin build at the appropriate place (/usr/local).

b. Now let’s edit the install.properties file. Here are the relevant lines that you should edit

  • Change the install.properties file 
PROPERTYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEhadoopdev 
XAAUDIT.DB.IS_ENABLEDtrue
XAAUDIT.DB.FLAVOURMYSQL
XAAUDIT.DB.HOSTNAMElocalhost 
XAAUDIT.DB.DATABASE_NAMEranger_audit 
XAAUDIT.DB.USER_NAMErangerlogger 
XAAUDIT.DB.PASSWORDrangerlogger 

c. Now enable the hdfs­-plugin by running the enable-­hdfs-­plugin.sh command (Remember to set JAVA_HOME before running the command)

Hadoop conf and hadoop lib folder are not found at expected locations as per the script because of which, Ranger hdfs plugin installation might fail. To resolve this issue create a symlink as conf dir of hadoop linking to hadoop conf dir. For e.g:

  • Export HADOOP_HOME and run the enable plugin script
  • One more change that we need to do is copy all the jar files from ${hadoop_home}/lib to share lib
  • Make sure the log dir exists and provide required permissions to it
  • Provide required permission to users in OS file system and hdfs file system according to your environment and requirement.

d.  Once these changes are done restart Hadoop NameNode and Secondary NameNode.

  • Stop NameNode, SecondaryNameNode and DataNode daemon: 
  • Start NameNode, SecondaryNameNode and DataNode daemon: 

e. This will make necessary changes to Hadoop config files to enable Ranger. One can verify the communication between Ranger Admin and Ranger Plugin as below :

  • By logging into the Ranger Admin Web interface and navigating to Audit > Agents. 
  • You can verify the plugin is communicating to Ranger admin by going to Audit -­> plugins tab and checking for status code 200 under the HDFS repo.

Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the hdfs­-plugin will not be able to communicate with Ranger admin.

Installing Apache Hive(1.2.0)

HiveServer2 doesn’t start unless HADOOP_VERSION is exported to bashrc

Enabling Ranger Hive Plugin

  • We’ll start by extracting our build at the appropriate place. 
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
  • Change the insall.properties file 
PROPERTYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEhivedev 
XAAUDIT.DB.IS_ENABLED true
XAAUDIT.DB.FLAVOUR=MYSQL MYSQL
XAAUDIT.DB.HOSTNAMElocalhost
XAAUDIT.DB.DATABASE_NAMEranger_audit
XAAUDIT.DB.USER_NAME rangerlogger
XAAUDIT.DB.PASSWORDrangerlogger
  •  Now enable the hive­-plugin by running the enable-­hive­-plugin.sh command (Remember to set JAVA_HOME)

This will make necessary changes to Hadoop config files to enable Ranger. One can verify the communication between Ranger Admin and Ranger Plugin as below :

  • By logging into the Ranger Admin Web interface and navigating to Audit > Agents. 
  • You can verify the plugin is communicating to Ranger admin by going to Audit -­> plugins tab and checking for status code 200 under the HIVE repo.

Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the hive-plugin will not be able to communicate with Ranger admin.

Helpful info Ranger Hive Plugin / Hive Services

 

 If /var/log/hive directory does not exist then create one and give required rights to user hive.

  • Make sure hive user has access to the configuration files
  • To start hive metastore
  • To start HiveServer2 
  • To Stop Hive service
  • Using Beeline to connect to Hive Metastore
  • If hive metastore and hiveserver2 do not start then verify below given key-­values according to your environment in following files.

hiveserver2­site.xml  

 

hive­site.xml 

 

  • You can verify the plugin is communicating to Ranger admin in Audit-­>plugins tab

Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the hive-plugin will not be able to communicate with Ranger admin.

Installing Apache HBase (1.1.0.1)

  • For HBase 0.98.5 and later, you are required to set the JAVA_HOME environment variable before starting HBase

Enabling Ranger HBase Plugins

  • We’ll start by extracting our build at the appropriate place.
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit
  • PROPERTYVALUE
    POLICY_MGR_URL

    http://localhost:6080

    REPOSITORY_NAMEhbasedev 
    XAAUDIT.DB.IS_ENABLEDtrue 
    XAAUDIT.DB.FLAVOURMYSQL
    XAAUDIT.DB.HOSTNAMElocalhost
    XAAUDIT.DB.DATABASE_NAMEranger_audit
    XAAUDIT.DB.USER_NAMErangerlogger
    XAAUDIT.DB.PASSWORDrangerlogger
  • Now enable the hbase­-plugin by running the enable­-hbase-­plugin.sh command (Remember to set JAVA_HOME)

This will make necessary changes to HBase config files to enable Ranger. Once these changes are done restart HBase Master and HBase Regionserver. 

One can verify the communication between Ranger Admin and Ranger Plugin as below :

  • By logging into the Ranger Admin Web interface and navigating to Audit > Agents. 
  • You can verify the plugin is communicating to Ranger admin by going to Audit -­> plugins tab and checking for status code 200 under the HBASE repo.

Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the hbase-plugin will not be able to communicate with Ranger admin.

Helpful info Ranger HBase Plugin / HBase Services

  •  To stop HBase Master and RegionServer: 

Installing Apache Knox Gateway

Enabling Ranger Knox Plugins

  • We’ll start by extracting our build at the appropriate place. 
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit:

PROPERYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEknoxdev
KNOX_HOME/usr/local/knox
XAAUDIT.DB.IS_ENABLEDtrue
XAAUDIT.DB.HOSTNAMElocalhost 
XAAUDIT.DB.DATABASE_NAMEranger 
XAAUDIT.DB.USER_NAMErangerlogger 
XAAUDIT.DB.PASSWORDrangerlogger 
  • Now enable the knox­-plugin by running the enable-­knox-­plugin.sh command (Remember to set JAVA_HOME)

This will make necessary changes to HBase config files to enable Ranger. Once these changes are done restart Knox Gateway and optionally Knox LDAP. 

One can verify the communication between Ranger Admin and Ranger Plugin as below :

  • By logging into the Ranger Admin Web interface and navigating to Audit > Agents. 
  • You can verify the plugin is communicating to Ranger admin by going to Audit -­> plugins tab and checking for status code 200 under the KNOX repo.

Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the knox-plugin will not be able to communicate with Ranger admin.

Helpful info Ranger Knox Plugin / Knox Services

If you get permission denied error during knox start please provide required privileges to knox user. For example : 

 

Trusting Self Signed Knox Certificate

       When Knox is listening on its SSL port with self signed certificate, you have to import SSL certificate of Knox into truststore used by Ranger Admin. This can be achieved by following the step:

  • Log in the machine running Apache Knox
  • Export knox certificate
    1. cd $GATEWAY_HOME/data/security/keystores              #This is typically /usr/local/knox/data/security/keystores on Linux machine. 
    2. keytool -­exportcert ­-alias gateway-­identity -­keystore gateway.jks -­file knox.crt
  • Copy knox.crt file onto machine running Ranger Admin to a working directory, for example /usr/local/ranger-­admin
  • Copy the cacerts and name it cacertswithknox
  • Import Knox certificate into the replicated new keystore
  • Edit /usr/local/ranger-­admin/ews/ranger-­admin-­services.sh
    1. Add parameter -­Djavax.net.ssl.trustStore=<path to the cacertswithknox> to the java call in the script.
  • Restart Ranger Admin.

Enabling Ranger Solr Plugin

Follow these steps to configure Ranger for Solr

  1. Install and configure Apache Solr in SolrCloud mode
  2. Create Solr Service/Repo in Ranger Admin and add default policies
  3. Install and Enable Solr Plugin by updating install.properties and calling ./enable-solr-plugin.sh
  4. Add security.json with Ranger Authorizer configuration

Install and configure Apache Solr in SolrCloud mode

You can refer here for instructions.

Solr Service in Ranger Admin

  1. Login to Ranger Admin
  2. Give a service name. e.g. solrdev  (Note this service name. You need to use this in the install.properties)
  3. For Username and Password, give "ranger" and "ranger". Please note this is not used yet
  4. For Solr URL, give the URL to the Solr instances. E.g. http://$HOST1:8983/solr,http://$HOST2:8983/solr
  5. Test Connection might not work. Please ignore it for now
  6. Click on "Add" and save the repository
  7. Go to the new service and update the default ( * ) policy to add user "solr" to it. This should be the same user as in the JAAS file used by Solr server process. Check -Djava.security.auth.login.config for the JAAS file used by Solr. This policy is needed because Solr process within the cloud talk with each other for replication and other house keeping requests.

Install and Enable Solr Plugin

  • Extract Ranger Solr plugin to a temporary location
  • Edit the install.properties file. Here are the relevant lines that you should edit:
  • Change the insall.properties file 
PROPERTYSample valuesDescription
POLICY_MGR_URL

http://$RANGER_ADMIN_HOST:6080

URL to the RangerAdmin
REPOSITORY_NAMEsolrdevThis is the service name used during creation of creation of the Solr service in Ranger
XAAUDIT.SOLR.ENABLEtrueThis enables audit to Solr
XAAUDIT.SOLR.URLhttp://$AUDIT_SOLR_HOST:6083/solr/ranger_audits This is the URL to the Solr instance used for storing audits.
  • set JAVA_HOME
  • Now enable the solr-plugin by running the enable-­solr-plugin.sh command
  • Repeat the above process for all the Solr instances. You can reuse the same install.properties for all the servers.
  • After these changes and enable-solr-plugin.sh are run on all the servers

Configuring Solr for Ranger

Solr needs to be configured to use Ranger Authorization implementation. For that, run the following command on one of the Solr host

In addition, please do following on all the Solr hosts

  • Restart all the Solr instances
  • You can check the solr.log for any errors
  • You can verify by logging into the Ranger Admin Web interface ­> Audit > Plugins
  • Make sure to create required policies for users. If users are getting denied, please check the audit logs.

Installing Apache Storm (0.10.0)

Enabling Ranger Storm Plugins

  • We’ll start by extracting our build at the appropriate place. 
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
  • Change the insall.properties file 
PROPERTYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEstormdev 
XAAUDIT.DB.IS_ENABLEDtrue
XAAUDIT.DB.HOSTNAMElocalhost 
XAAUDIT.DB.DATABASE_NAMEranger 
XAAUDIT.DB.USER_NAMErangerlogger 
XAAUDIT.DB.PASSWORDrangerlogger
  • Now enable the storm-plugin by running the enable-­storm-plugin.sh command (Remember to set JAVA_HOME)
  • Once these changes are done Restart Storm
  • This should start the association of ranger-storm-plugin with storm
  • You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents
  • You can verify the plugin is communicating to Ranger admin in Audit >plugins tab

If stormdev service is not created in Ranger Admin then storm-plugin will not able to communicate with Ranger Admin.

Installing Apache Yarn

You can run a MapReduce job on YARN in a pseudo­distributed mode by setting a few parameters and running ResourceManager daemon and NodeManager daemon in addition

The following instructions assume that hadoop installations steps mentioned in Installing Apache Hadoop are already executed.

Enabling Ranger Yarn Plugin

  • We’ll start by extracting our build at the appropriate place (/usr/local). 
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
  • Change the install.properties file 
PROPERTYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEyarndev
XAAUDIT.DB.IS_ENABLEDtrue
XAAUDIT.DB.FLAVOURMYSQL
XAAUDIT.DB.HOSTNAMElocalhost
XAAUDIT.DB.DATABASE_NAMEranger_audit 
XAAUDIT.DB.USER_NAMErangerlogger 
XAAUDIT.DB.PASSWORDrangerlogger 
  • Now enable the yarn­-plugin by running the enable-­yarn-­plugin.sh command.
  • One more change that we need to do is copy all the jar files from  ${hadoop_home}/lib
  • if you get permission denied error during yarn start please provide required privileges to yarn user in local and hdfs file system. for example :
  • Once these changes are done Start ResourceManager daemon and NodeManager daemon.
  • Start the ResourceManager on ResourceManager hosts. 
  • Start the NodeManager on NodeManager hosts. 
  • Stop the ResourceManager on ResourceManager hosts. 
  • Stop the NodeManager on NodeManager hosts. 

This should start the association of ranger-­yarn-­plugin with hadoop. 

  1. You can verify by logging into the Ranger Admin Web interface ­> Audit > Agents
  2. You can verify the plugin is communicating to Ranger admin in Audit-­>plugins tab

If yarndev service is not created in Ranger Admin then yarn­-plugin will not able to communicate with Ranger Admin.

Installing Ranger KMS (0.5.0)

Prerequisites: (Need to done for all host on which Ranger KMS needs to be installed)

  • Download “Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files” zip using below link depending upon the Java version used
    1. http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html 
    2. http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
  • Unzip the above downloaded zip file to java’s security folder (Depending upon the java version used)

 STEPS FOR RANGER KMS

  • We’ll start by extracting our build at the appropriate place(/usr/local). 
  • Please note that Ranger KMS plugin is integrated with Ranger KMS and will be installed automatically when KMS is installed.
  • Now let’s edit the install.properties file. Here are the relevant lines that you should edit:
  • Change the install.properties file 
PROPERTYVALUE
POLICY_MGR_URL

http://localhost:6080

REPOSITORY_NAMEkmsdev
KMS_MASTER_KEY_PASSWD  enter master key password
XAAUDIT.DB.IS_ENABLEDtrue
XAAUDIT.DB.FLAVOURMYSQL 
XAAUDIT.DB.HOSTNAMElocalhost 
XAAUDIT.DB.DATABASE_NAMEranger_audit 
XAAUDIT.DB.USER_NAMErangerlogger
XAAUDIT.DB.PASSWORDrangerlogger
DB_FLAVOURMySQL/ ORACLE/ Postgres/ SQL Server
SQL_CONNECTOR_JAR<Location of jar file>
db_root_userroot
db_root_password<password>
db_hostlocalhost
db_namerangerkms
db_userrangerkms
db_password<password>
  • Edit “hdfs-site.xml”( Need to give provider else it will not support hadoop commands)Replace localhost with <internal host name> 
    1. Go to path cd /usr/local/hadoop/conf/
    2. vim hdfs-site.xml
    3. For property “dfs.encryption.key.provider.uri” ,enter the value “kms://http@<internal host name>:9292/kms
    4. Save and quit 
  • Edit “core­site.xml”( Need to give provider else it will not support hadoop commands)
  • Replace localhost with <internal host name> 
    1. Go to path cd /usr/local/hadoop/conf/ 
    2. vim core­site.xml 
    3. For property “hadoop.security.key.provider.path” ,enter the value “kms://http@<internal host name>:9292/kms
    4. Save and quit 
  • Once these changes are done Restart hadoop.
  • Stop NameNode, SecondaryNameNode and DataNode daemon: 
  • Run setup  
  • Start the kms server
  • You can verify the plugin is communicating to Ranger admin in Audit-­>plugins tab.

Note

If kmsdev service is not created in Ranger Admin then kms­-plugin will not able to connect to Ranger admin.

  • To Create the Kms service 
PROPERTYVALUE
REPOSITORY_NAME

Name specified in installed.properties (e.g
kmsdev)

KMS URLkms://http@<internal host name>:9292/kms 
Username<username> (for e.g keyadmin)
Password<password> 
  • Check Test connection

Enabling Audit Logging To HDFS

To enable Audit to HDFS for a plugin do the below

  1. Depending upon Keberos or non-kerberos mode, one of the scripts from here need to be run: https://github.com/apache/incubator-ranger/tree/master/security-admin/contrib/audit_hdfs_folders 
  2. Set XAAUDIT.HDFS.ENABLE = true for respective component plugin in the install.properties file which may be found in /usr/local/ranger­<component>­plugin/ directory.
  3. Configure NameNode host in the XAAUDIT.HDFS.HDFS_DIR.
  4. Create a policy in HDFS service from Ranger Admin for individual component users (hive/hbase/knox/storm/yarn/kafka/kms) to give READ+ WRITE permission for the particular audit folder. i.e for enabling Hive component to log Audits to HDFS , we need to create a policy for hiveuser with READ+ WRITE permissions to respective audit directory
  5. Audit to HDFS caches logs in local directory, which can be specified in XAAUDIT.HDFS.LOCAL_BUFFER_DIRECTORY ( this can be like ‘/var/log/<component>/**), which is the path where audit is stored temporarily, likewise for archived logs we need to update XAAUDIT.HDFS.LOCAL_ARCHIVE_DIRECTORY value ( this can be like ‘/var/log/<component>/**), before enabling the plugin for the component.

HDFS audit logging is for archive purposes. For seeing audit report in the Ranger Admin UI, recommended option is Solr.

Enabling Audit Logging To SOLR

  • To enable Audit report from Solr, do the below change in Ranger admin 
  1.  Set following properties in install.properties of ranger service to work audit to solr in Ranger
PROPERTIESVALUE
audit_storesolr
audit_solr_urls 

http://solr_host:6083/solr/ranger_audits

audit_solr_userranger_solr
audit_solr_password 

NONE 

   2. Restart Ranger

  •  To enable Audit to Solr for a plugin do the below

Set following properties in install.properties of plugin to start logging audit to Solr : for eg Hbase

PROPERTYVALUE
XAAUDIT.SOLR.IS_ENABLEDtrue 
XAAUDIT.SOLR.ENABLEtrue 
XAAUDIT.SOLR.URL

http://solr_host:6083/solr/ranger_audits

XAAUDIT.SOLR.USERranger_solr  
XAAUDIT.SOLR.PASSWORDNONE 
XAAUDIT.SOLR.FILE_SPOOL_DIRvar/log/hadoop/hdfs/audit/solr/spool  
  1. Enable ranger plugin for Hbase
  2. Restart Hbase component. 

Configuring Kerberos Authentication

Installing and Configuring the KDC

  • To use Kerberos with Hadoop you can either use an existing KDC or install a new one just for Hadoop's use. The following gives a very high level description of the installation process.
  • To install a new version of the server.
  • Increase the entropy of the linux kernel. This can be done by installing rng-tools on CentOS:
  • Edit /etc/sysconfig/rngd to add EXTRAOPTIONS="-r /dev/urandom"
  • Start rng daemon:  
  • When the server is installed use a text editor to edit the configuration file, located by default here:
  • Change the [realms] section of this file by replacing the default “kerberos.example.com” setting for the kdc and admin_server properties with the Fully Qualified Domain Name of the KDC server. In this example below, “kerberos.example.com” has been replaced with “my.kdc.server”.
  •  Set up the KDC Access Control List (ACL) by adding administrators to /var/kerberos/krb5kdc/kadm5.acl. For example, the following command grants full access to the database for users with the admin extension: */admin@EXAMPLE.COM

Creating the Kerberos Database

  • Use the utility kdb5_util to create the Kerberos database. Create Kerberos database on Kerberos server host using kdb5_util utility:  
  • Start the KDC.

Installing and Configuring the Kerberos Clients

  •  To install the Kerberos clients, on every server in the cluster:
  • Creating Service Principals and Keytab Files

Each service and sub-service in Hadoop must have its own principal. A principal name in a given realm consists of a primary name and an instance name, which in this case is the FQDN of the host that runs that service. As services do not login with a password to acquire their tickets, their principal's authentication credentials are stored in a keytab file, which is extracted from the Kerberos database and stored locally with the service principal on the service component host.First you must create the principal, using mandatory naming conventions.Then you must create the keytab file with that principal's information and copy the file to the keytab directory on the appropriate service host.

  • Open the kadmin.local utility on the KDC machine:
  • Create the service principals

The -randkey option is used to generate the password.Note that in the example each service principal's primary name has appended to it the instance name, the FQDN of the host on which it runs. This provides a unique principal name for services that run on multiple hosts, like DataNodes and NodeManagers. The addition of the host name serves to distinguish, for example, a request from DataNode A from a request from DataNode B. This is important for two reasons:If the Kerberos credentials for one DataNode are compromised, it does not automatically lead to all DataNodes being compromisedIf multiple DataNodes have exactly the same principal and are simultaneously connecting to the NameNode, and if the Kerberos authenticator being sent happens to have same timestamps, then the authentication would be rejected as a replay request.

  • Once the principals are created in the database, you can extract the related keytab files for transfer to the appropriate host:
  • When the keytab files have been created, on each host create a directory for them and set appropriate permissions.

Configure Storm to Work with a Secured Zookeeper Cluster

  • open /etc/krb5.conf file in text editor and validate the following content.
  • Open /var/kerberos/krb5kdc/kdc.conf file in text editor and validate the following content
  • cd /usr/local
  • Download the zookeeper from apache mirror site http://www.apache.org/dyn/closer.cgi/zookeeper/ and untar the downloaded gz file in /usr/local
  • tar -xvf zookeeper.tar.gz
  • useradd hadoop
  • useradd zookeeper
  • Open zookeeper/conf/zoo.cfg file in text editor and validate the following content.
  • Open zookeeper/conf/zookeeper-env.sh file in text editor and validate the following content.
  •  Provide permission to files and directories.
    1. mkdir -p $ZOOKEEPER_DATA_DIR
    2. chown -R $ZOOKEEPER_USER:$HADOOP_GROUP $ZOOKEEPER_DATA_DIR
    3. chmod -R 755 $ZOOKEEPER_DATA_DIR
    4. mkdir -p $ZOOKEEPER_LOG_DIR
    5. chown -R $ZOOKEEPER_USER:$HADOOP_GROUP $ZOOKEEPER_LOG_DIR
    6. chmod -R 755 $ZOOKEEPER_LOG_DIR;
    7. mkdir -p $ZOOPIDFILE
    8. chown -R $ZOOKEEPER_USER:$HADOOP_GROUP $ZOOPIDFILE
    9. chmod -R 755 $ZOOPIDFILE;
    10. chmod a+x $ZOOKEEPER_CONF_DIR/;
    11. chown -R $ZOOKEEPER_USER:$HADOOP_GROUP $ZOOKEEPER_CONF_DIR
    12. chmod -R 755 $ZOOKEEPER_CONF_DIR/../
  • Add principal for zookeeper service.
  • Add principal for HTTP service.
  • Restart the zookeeper service.

Configure Kerberos Authentication for Storm

  • Open /usr/local/storm/conf/storm.yaml file in text editor and validate the following content.
  • Open /usr/local/storm/conf/storm_jaas.conf file in text editor and validate the following content.
  • Open /usr/local/storm/conf/client_jaas.conf file in text editor and validate the following content.
  • Add storm headless principal.
  • Add principal for nimbus service.
  • Add storm client headless principal.
  • Provide permission to logs, keytab files.
    1. mkdir -p /usr/local/storm/logs
    2. chown -R storm:storm /usr/local/storm/logs
    3. chmod +r /tmp/*.keytab
    4. chmod +x /tmp/*.keytab
    5. chmod +r //etc/security/keytabs/*.keytab
    6. chmod +x //etc/security/keytabs/*.keytab
  • To initiate a session use kinit.
  • Now enable storm plugin.
  • Create stormdev repo with stormtestuser.
  • Check connection.
  • Check plugin communication with ranger.
  • If required add user in os/ranger admin.

Installing Ranger KMS(0.5.0) on Kerberos Environment

Prerequisites Required

  • Check on secure instance
    1. Checking HTTP Principle
      1. kadmin.local

      2. list_principals

      3. exit

    2. search for spnego.service.keytab

      1. locate spengo keytab

      2. kadmin.local

      3. list_principals

      4. exit

      • The list shown should contain HTTP/<internal host name>@Realm

    3. Try to using  “HTTP/<internal host name>@Realm” with “spnego.service.keytab”

      1. locate spengo keytab
      2. kinit -k -t  <path>/spengo.service.keytab/<intername host name>@EXAMPLE.COM
      3. klist
      4. kdestroy

 

  • Create a principle to use with Ranger Repo for logging in KMS
  • Create principal
  • Check the principal by doing kinit
  • Edit “hdfs­-site.xml”
  • Edit “core-­site.xml”

  • Restart Namenode
  • Restart krb5kdc
  • We’ll extract our build of ranger KMS at the appropriate place (/usr/local).

Note that ranger KMS plugin is integrated with ranger KMS and will be installed automatically when KMS is installed

  • Setting required for secure instance

    1. Edit following properties under ews/webapp/WEB­INF/classes/conf.dist/kms-­site.xml:
  •   Add following property in ews/webapp/WEB­INF/classes/conf.dist/kms-­site.xml : (Replace “testkms1” with appropriate user who will be used for credential authentication):

  • Create link to /etc/hadoop/conf/core-site.xml under /etc/ranger/kms/conf

    1. (ln -s /etc/hadoop/conf/core-site.xml /etc/ranger/kms/conf/core-site.xml)

  • Install Ranger-kms with appropriate property values

    1. Go to ranger-kms folder and edit install.properties (Enter appropriat  values for the below given properties)
      1. db_root user=
      2. db_root password
      3. db_host
      4. db_name
      5. db_user
      6. db_password
      7. KMS_MASTER_KEYPASSWD
      8. POLICY_MGR_URL
      9. REPOSITORY_NAME
      10. XAAUDIT.DB.IS_ENABLED
      11. XAAUDIT.DB.FLAVOUR
      12. XAAUDIT.DB.HOSTNAME
      13. XAAUDIT.DB.DATABASE_NAME
      14. XAAUDIT.DB.USER_NAME
      15. XAAUDIT.DB.PASSWORD
  • Run setup
  • start the KMS server

 

Ranger UI setup

Check the user present in ranger which will be used for credential validation (for e.g (“testkms1”) if not then create that using “admin” login

  • Create KMS service
    1. REPOSITORY_NAME: name specified in installed.properties (e.g kmsdev)

    2. KMS URL: kms://http@<internal host name>:9292/kms
    3. Username:Principle that will be used for kms (e.g.testkms1@EXAMPLE.COM)
    4. Password:Password for principle(e.g.testkms1 password)
    5. Check test connection
    • Please check the logged in user (for e.g “keyadmin”) has the permission for KMS operation You can navigate to KMS Tab and do all the operation related to the KMS.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



 

 

 

 

 


 

 

 

 

 

 



  • No labels

5 Comments

  1. this is error:

    cp /usr/local/hadoop/lib/*.jar /usr/local/hadoop/share/hadoop/hdfs/lib/

     

    should be:

    cp /usr/local/ranger-hdfs/lib/ranger-hdfs-plugin-impl/*.jar /usr/local/hadoop/share/hadoop/hdfs/lib/

     

  2. I want to only install Ranger KMS, how to install ?

    I want to Kms Ranger is integrated into the existing Hadoop cluster, using only Ranger kms, but encountered a number of error messages:

    1      how to control ACL kms, is through the configuration file dbks-site.xml?

    2         hadoop key list -provider kms://http@<host>:9292/kms

    the kms-audit.log   

    2016-05-08 01:33:06,923 UNAUTHENTICATED RemoteHost:172.27.32.115 Method:OPTIONS URL:http://<hostname>:9292/kms/v1/keys/names ErrorMsg:'Authentication required'

    3. There is no better documentation, KMS ranger of each configuration file, and the role of KMS Hadoop in different places,

    The difference between conf and conf.dist?

    4. the kms.log error,  Has been reported to the wrong, how to disable the PolicyRefresher.

    2016-05-08 01:50:37,014 WARN  PolicyRefresher - cache file does not exist or not readble '/etc/ranger/kmsdev/policycache/kms_kmsdev.json'

    2016-05-08 01:51:07,015 ERROR PolicyRefresher - PolicyRefresher(serviceName=kmsdev): failed to refresh policies. Will continue to use last known version of policies (-1)

    com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused

            at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:155)

            at com.sun.jersey.api.client.Client.handle(Client.java:652)

     

    Thank you.

  3. Hello everyone ,

    Iam using WIN7 64 bit system. I checked out the code . Gave the following build command. 

    -DskipTests=false clean compile package install assembly:assembly;but iam getting the following error .

    Results :

    Failed tests: 
    org.apache.ranger.authorization.hadoop.utils.RangerCredentialProviderTest.testCredentialProvider(org.apache.ranger.authorization.hadoop.utils.RangerCredentialProviderTest)
      Run 1: RangerCredentialProviderTest.setup:92 expected:<0> but was:<1>
      Run 2: RangerCredentialProviderTest.teardown:141 expected:<0> but was:<1>

    org.apache.ranger.authorization.hadoop.utils.RangerCredentialProviderTest.testCredentialString(org.apache.ranger.authorization.hadoop.utils.RangerCredentialProviderTest)
      Run 1: RangerCredentialProviderTest.setup:92 expected:<0> but was:<1>
      Run 2: RangerCredentialProviderTest.teardown:141 expected:<0> but was:<1>


    Tests run: 2, Failures: 2, Errors: 0, Skipped: 0

    [INFO]                                                                         
    [INFO] ------------------------------------------------------------------------
    [INFO] Skipping ranger
    [INFO] This project has been banned from the build due to previous failures.
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] 
    [INFO] ranger ............................................. SUCCESS [ 10.946 s]
    [INFO] Jdbc SQL Connector ................................. SUCCESS [  5.466 s]
    [INFO] Credential Support ................................. FAILURE [  9.601 s]
    [INFO] Audit Component .................................... SKIPPED
    [INFO] Common library for Plugins ......................... SKIPPED
    [INFO] Installer Support Component ........................ SKIPPED
    [INFO] Credential Builder ................................. SKIPPED
    [INFO] Embedded Web Server Invoker ........................ SKIPPED
    [INFO] Key Management Service ............................. SKIPPED
    [INFO] ranger-plugin-classloader .......................... SKIPPED
    [INFO] HBase Security Plugin Shim ......................... SKIPPED
    [INFO] HBase Security Plugin .............................. SKIPPED
    [INFO] Hdfs Security Plugin ............................... SKIPPED
    [INFO] Hive Security Plugin ............................... SKIPPED
    [INFO] Knox Security Plugin ............................... SKIPPED
    [INFO] Storm Security Plugin .............................. SKIPPED
    [INFO] YARN Security Plugin ............................... SKIPPED
    [INFO] Ranger Util ........................................ SKIPPED
    [INFO] Unix Authentication Client ......................... SKIPPED
    [INFO] Security Admin Web Application ..................... SKIPPED
    [INFO] KAFKA Security Plugin .............................. SKIPPED
    [INFO] SOLR Security Plugin ............................... SKIPPED
    [INFO] NiFi Security Plugin ............................... SKIPPED
    [INFO] Unix User Group Synchronizer ....................... SKIPPED
    [INFO] Ldap Config Check Tool ............................. SKIPPED
    [INFO] Unix Authentication Service ........................ SKIPPED
    [INFO] KMS Security Plugin ................................ SKIPPED
    [INFO] Tag Synchronizer ................................... SKIPPED
    [INFO] Hdfs Security Plugin Shim .......................... SKIPPED
    [INFO] Hive Security Plugin Shim .......................... SKIPPED
    [INFO] Knox Security Plugin Shim .......................... SKIPPED
    [INFO] YARN Security Plugin Shim .......................... SKIPPED
    [INFO] Storm Security Plugin shim ......................... SKIPPED
    [INFO] KAFKA Security Plugin Shim ......................... SKIPPED
    [INFO] SOLR Security Plugin Shim .......................... SKIPPED
    [INFO] Atlas Security Plugin Shim ......................... SKIPPED
    [INFO] KMS Security Plugin Shim ........................... SKIPPED
    [INFO] Ranger Hive Utils .................................. SKIPPED
    [INFO] ranger-examples .................................... SKIPPED
    [INFO] Ranger Examples - Conditions and ContextEnrichers .. SKIPPED
    [INFO] Ranger Examples - SampleApp ........................ SKIPPED
    [INFO] Ranger Examples - Ranger Plugin for SampleApp ...... SKIPPED
    [INFO] Ranger Tools ....................................... SKIPPED
    [INFO] Atlas Security Plugin .............................. SKIPPED
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 27.366 s
    [INFO] Finished at: 2017-02-10T10:51:06+05:30
    [INFO] Final Memory: 36M/390M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project ranger-plugins-cred: There are test failures.
    [ERROR] 
    [ERROR] Please refer to C:\Users\git\ranger\agents-cred\target\surefire-reports for the individual test results.
    [ERROR] -> [Help 1]
    [ERROR] 
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] 
    [ERROR] After correcting the problems, you can resume the build with the command
    [ERROR]   mvn <goals> -rf :ranger-plugins-cred

    Could you please let me know how to rectify this build error ?

    Regards

    1. neeravarora : In windows, credential store module has dependency on gcc (linux libraries), so either you can install the gcc library on windows or you  can skip build of credential store.

  4. Hi Mehul ,

    Thanks for answering my query . I think, i will proceed with developing on Linux since that is the preferred way of developing as mentioned in the docs .