However, when our client acquired a new company and it was necessary to input new employees as users in the system all sort of bad things started to happen. Just a few more months later into the use, with no significant addition of user entries, we did not encounter any more problems. We also updated to the latest version which at the time was M17, and hoped for the best.
We had no choice but to restore from our backups. 50-60 insert/update operations have been done in the ApacheDS LDAP directory, and we had data corruption again, with all sorts of misleading error messages. Since we were pushing towards the deadline for our project and things seemed to have been resolved, we went ahead and imported all 15000 users, with “only” one restart required.Ī month or two into using the application, in which aprox. We also found documentation indicating that there are some cache settings that need to be incremented, so we did that. We scratched our heads, and started again from 0. In the mean time version M12 came out, so we decided to go for that. The corruption of data made it such that you could not find a user by searching for it, you could not delete it, and even more frustrating, while trying to add the same user you got a duplicate entry error. However, after a couple restarts we got to about 3-4000 users imported it stopped working even after restart.Įven more, some of the data already in the system seemed to be corrupted. Well, restarting ApacheDS seemed to be the solution, so we did that a couple of times. Initial tests for importing user information went smooth, however we only tested batches of 10-20 users at a time. We then moved to importing larger batches, and we did notice that after about 500 users we started getting errors upon trying to add more. Since the installation out of the box was pretty simple for ApacheDS, we just deployed it on the server and did not give it a second thought. We had a portal and we used ApacheDS LDAP authentication in front of that.
This was part of a bigger project in which the LDAP integration was about 10%. We deployed version M11 of ApacheDS for one big client we had (around 15,000 users). I started using ApacheDS around a year ago, but little did I suspect what was going to happen. To be honest, being mainly a Java programmer I have to say that I’m very happy with all most of the solutions found under Apache. What is ApacheDS? It is an open source directory server developed under the Apache Foundation. I don’t usually do this, I’m not hater, but take this warning from me: stay away from ApacheDS! ApacheDS LDAP After a brief investigation about what open source solutions there are we decided that we go for the ApacheDS LDAP authentication.
Apache directory studio m11 code#
Here is my code trying to connect using Apache's LDAP Client API:Įdit: I added the trust manager.While developing a relatively large application, we required a single sign-on authentication. I have followed Apache's user guide exactly and still no luck! I have enabled TSLv1.2 protocol in the server's configuration and still no luck. I'm able to connect to the LDAP server but when I try to connect to LDAPS, I keep getting errors.
I need help connecting to Apache's Directory Server using SSL.
0 kommentar(er)
