[
https://issues.apache.org/jira/browse/RANGER-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Polavarapu reopened RANGER-652:
---------------------------------------
Reopening the issue as the below error is reported while running the tool:
[root@vp-os-rh6-ora-sim-amb212-hdp2-3-151022-1547-5 ldaptool]# ./run.sh
JAVA commnad = java -cp
/usr/hdp/2.3.4.0-3042/ranger-usersync/ldaptool/lib/ldapconfigcheck.jar:/usr/hdp/2.3.4.0-3042/ranger-usersync/ldaptool/lib/*:/usr/hdp/2.3.4.0-3042/ranger-usersync/ldaptool/conf
org.apache.ranger.ldapconfigcheck.LdapConfigCheckMain -o
/usr/hdp/2.3.4.0-3042/ranger-usersync/ldaptool/output/
Exception in thread "main" java.lang.SecurityException: Invalid signature file
digest for Manifest main attributes
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:287)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:240)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:317)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:348)
at java.util.jar.JarFile.getInputStream(JarFile.java:415)
at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:775)
at sun.misc.Resource.cachedInputStream(Resource.java:77)
at sun.misc.Resource.getByteBuffer(Resource.java:160)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:436)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
> LDAP configuration tool
> -----------------------
>
> Key: RANGER-652
> URL: https://issues.apache.org/jira/browse/RANGER-652
> Project: Ranger
> Issue Type: New Feature
> Affects Versions: 0.5.0
> Reporter: Velmurugan Periasamy
> Assignee: Sailaja Polavarapu
> Fix For: 0.6.0
>
> Attachments:
> 0001-RANGER-652-Adding-support-for-ldap-connection-check-.patch,
> 0001-RANGER-652-Include-ldapconfigcheck-tool-in-main-pom..patch, Ldap
> Connection Check Tool.pdf
>
>
> A common use-case for Ranger is to sync the enterprise LDAP/AD users and make
> the process of defining authorization policies simpler. Currently, making
> this integration to LDAP/AD server require some effort from the administrator
> as Ranger provides many properties that need to be configured to sync the
> LDAP/AD users.
> It would be very helpful to have a tool that helps administrators to
> configure LDAP properties for Ranger UserSync and LDAP/AD authentication for
> Ranger Admin.
> For example, this tool can collect minimal input about the LDAP/AD server and
> provide suggestions for various other LDAP/AD properties in order to
> successfully pull only targeted Users and Groups from the LDAP/AD server.
> Admins can change the input and verify if they are correct by validating the
> users/groups retrieved.
> Once all the properties are discovered and tested with the tool, these values
> can be applied in Ranger config. This will save time and reduce errors when
> configuring ranger usersync and admin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
