I'm not sure why this would have a big impact. We do tend to use Directory String by default. Just out of curiosity, what LDAP server did you use instead of OpenDJ? @HARJINDER.DHANJAL can you look at this to see if it would have any negative impact. If not, I guess we should change it.

Thanks for your quick response. We are using VDS as our ldap which has the ability to create proxies. It will automatically change the DN referenced through the proxy to match that of the proxy base DN so long as it knows the attribute is referring to an entry DN and not just a random string. It determines this based on the syntax defined in the schema.

The Radiant Logic VDS? We love that product... In practice, I would not recommend what you have attempted. I would use the Cache Refresh feature in Gluu to sync the data from the VDS. If you use the VDS as the primary database to back Gluu, I think it will lead to rigidity when it comes to upgrade. Also, when it comes to performance, you ideally don't want to gather data on the fly--it hurts performance. The best design is to think of OpenDJ as the "persistent cache". Do the mapping in the VDS... but persist the data in OpenDJ. If you want to schedule a call to discuss, you do so on the [booking page](https;//gluu.org/booking).