Databases
StackOverflow2013
Postsdbo
POLDAP Authentication using Java
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLDAP Authentication using Java
    primarykey
    data
    text
    <p>I need to do LDAP Authentication for an application.</p> <p>I tried the following program:</p> <pre><code>import java.util.Hashtable; import javax.naming.Context; import javax.naming.NamingException; import javax.naming.ldap.InitialLdapContext; import javax.naming.ldap.LdapContext; public class LdapContextCreation { public static void main(String[] args) { LdapContextCreation ldapContxCrtn = new LdapContextCreation(); LdapContext ctx = ldapContxCrtn.getLdapContext(); } public LdapContext getLdapContext(){ LdapContext ctx = null; try{ Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory"); env.put(Context.SECURITY_AUTHENTICATION, "Simple"); //it can be &lt;domain\\userid&gt; something that you use for windows login //it can also be env.put(Context.SECURITY_PRINCIPAL, "username@domain.com"); env.put(Context.SECURITY_CREDENTIALS, "password"); //in following property we specify ldap protocol and connection url. //generally the port is 389 env.put(Context.PROVIDER_URL, "ldap://server.domain.com"); ctx = new InitialLdapContext(env, null); System.out.println("Connection Successful."); }catch(NamingException nex){ System.out.println("LDAP Connection: FAILED"); nex.printStackTrace(); } return ctx; } } </code></pre> <p>Getting following exception:</p> <pre> LDAP Connection: FAILED javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3053) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2801) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2715) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:305) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:187) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:205) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:148) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:78) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:235) at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348) at javax.naming.InitialContext.internalInit(InitialContext.java:286) at javax.naming.InitialContext.init(InitialContext.java:308) at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:99) at LdapContextCreation.getLdapContext(LdapContextCreation.java:27) at LdapContextCreation.main(LdapContextCreation.java:12) </pre> <p>Few more points to consider:</p> <ol> <li><p>Earlier I was using <code>tomcat 5.3.5</code> but somebody told me that only tomcat 6 supports it so I downloaded <code>tomcat 6.0.35</code> and currently using this version only.</p></li> <li><p>Configured <code>server.xml</code> and added the following code -</p> <pre><code>&lt;Realm className="org.apache.catalina.realm.JNDIRealm" debug="99" connectionURL="ldap://server.domain.com:389/" userPattern="{0}" /&gt; </code></pre></li> <li><p>Commented the following code from <code>server.xml</code> -</p> <pre><code>&lt;!-- Commenting for LDAP &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/&gt; --&gt; </code></pre></li> <li><p>Steps 2 and 3 from <a href="http://viralpatel.net/blogs/implement-ldap-authentication-in-tomcat-jboss-server-for-java-app/" rel="nofollow noreferrer">article</a> </p></li> <li><p>Someone suggested that there are some jar files that are supposed to be copied to tomcat in order to run <code>ldap</code> authentication, is that something I need to do? And which <code>jar</code> files?</p></li> <li><p>Also, I am using the correct credentials for sure, then what is causing this issue?</p></li> <li><p>Is there a way I can figure out the correct attributes for LDAP in case I am using incorrect ones?</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGary
    1. USanujin
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThere are better libraries for this, but here is a Similar Question http://stackoverflow.com/a/12165647/1286621 I agree with @jasim about the principal. You need to figure out what format your LDAP server is using. Here's an example of my Active Directory Server "CN=bindUserName,CN=Users,DC=myDepartment,DC=myNetwork". The LDAP folks should pretty quickly be able to tell you what the format is. There are also gui tools out there that can connect to LDAP and browse the directories. Talk to your Admins first though.
      singulars
      1. POLDAP Authentication using Java
      1. USMike
    2. COJust one more comment, you are aware that there is usually a "Bind" user/password, one that has permission to lookup info in the LDAP Server correct? Once you Bind to the Server, you can then authenticate the users credentials.
      singulars
      1. POLDAP Authentication using Java
      1. USMike
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload