I set up LDAP using the web console interface instead of put those settings in the file portal.properties. After I saved the changes, where are all LDAP settings saved to?

Hi Khoivu,

When you save the LDAP Settings through the GUI, they get saved to the database.

The table you want to check is PortletPreferences, more specifically, the Preferences column.

Thanks,
Chris

Hi Christopher,

I started the LDAP setup using portal-ext.properties file. And it worked fine. However, one of our colleagues made a change through UI.
Because of that change though UI, I cannot change some setting from the portal-ext.properties any more.

Now I am trying to change ldap.import.group.search.filter. However, The UI fails to save the change. Even if I hit save button, it still shows old value. (I am using 6.0 EE version). Therefore, I tried to change it through portal.ext-properties, but it failed as well.

Now, I am stuck and I cannot change it at all. I think my last resort is to change the entry in the database. Can you tell you the where it is saved in the database so that I can directly change it? Thank you.

Brian Ko

I found it was saved in the table, portalpreferences. When it was saved from the UI fresh new, XML string is saved. (The DB is Mysql in this case.) However, in my case, Java object is saved instead on Db2 daatabase. Is it safe to change the java object to XML string?

Brian Ko

Hi Brian, since I do not know the extent of the LDAP changes beyond what you've noted, I'll just assume there might be others. Because of this, you can not just blow out the row in the portalpreferences table. That would tell the portal to fetch the values from the portal.properties (and override) files again. But you're started from scratch again.

You'll want to update the row's name/value pair with your value. However, you mentioned that your UI updates are not taking as well. If that the case, in the LDAP UI, you can use the "test" buttons to make sure it works. If not, you can debug by using another LDAP broswer with the same connection values. If they work in the LDAP browser and do not work in LDAP, we'll have to debug further with Liferay.

You should see immediate LDAP changes from the UI as well. You may have to re-index or restart your server if you're on your own dev machine.

Great, I will try that. Thank you!

Brian