Differences

This shows you the differences between two versions of the page.

--- java:ldapconfigfromtheground [2010/10/20 13:06] – rlunaro
+++ java:ldapconfigfromtheground [2022/12/02 22:02] (current) – external edit 127.0.0.1
@@ Line 35: / Line 35: @@
 <code xml>
-<application-policy name="ldapAuditmap">
+<application-policy name="INVENT A NAME FOR THIS">
 	<authentication>
 		<login-module flag="required" code="org.jboss.security.auth.spi.LdapExtLoginModule">
@@ Line 72: / Line 72: @@
 </code>
+We will explain how to identify every one of the values needed to configure this XML snippet.
+**INVENT A NAME FOR THIS:** It's just a name, we will use later. I've chosen for this ldapJMXConsole.
+**PUT THE SERVER : AND THE PORT:** If you managed to connect to the LDAP server using Jxplore --I strongly recommend this even if you are using Active Directory in your installation--, this values are provided in the connection screen:
+{{:java:jxplorer2.jpg|}}
 ===== Step N: set a security domain =====
@@ Line 81: / Line 88: @@
 <security-domain>java:/jaas/ldapJMXConsole</security-domain>
 </code>
+===== Step N+1: Thing's aren't going well =====
+Ok, let's face it: despite following the steps in this guide, thing's aren't working. The Active Directory Administrator isn't working very much (many times he/she is fighting in his/her own wars). And, what else???
+**Use the brute force to diagnose what is happening:** [[http://www.wireshark.org/|Wireshark]] is a packet sniffer: it allows you to see what's happening behind the scenes. The problem I had to face when configuring this stuff was that there were no errors when the thing fails: nothing. No message, no error is in the server log, nothing.
+But //alas!!!// with a packet sniffer you can see the traffic behind and the exact error message returnet.
+If nobody allows you to install a packet sniffer in the production server (a bad idea), you can try to make a testing deployment in your computer and try to find there the correct configuration of the LDAP.