ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Security Analytics custom LDAP configurations made outside of the Web Interface could get overwritten during an upgrade
Article ID: 168725
Updated On:
Products
Security Analytics
Issue/Introduction
Custom LDAP configurations made outside the Web Interface, such as from the Linux CLI could get overwritten during an upgrade.
Resolution
Blue Coat recommends backing up any form of custom configuration made that is outside the GUI to an external device. Such configuration might get overwritten in an upgrade or subsequent configuration changes made through the GUI.
Should the /etc/ldap.conf get overwritten, it can be restored by:
1. Comparing the difference in the new /etc/ldap.conf and /etc/openldap/ldap.conf with the existing backup copy.
2. Reapply the custom configuration into the /etc/ldap.conf and /etc/openldap/ldap.conf files and save it.
3. From the CLI, run "service nscd restart" for the restored configuration to take effect.
4. From the GUI, save the LDAP configuration.
5. Verify that the restored configuration is working as before.
Should the /etc/ldap.conf get overwritten, it can be restored by:
1. Comparing the difference in the new /etc/ldap.conf and /etc/openldap/ldap.conf with the existing backup copy.
2. Reapply the custom configuration into the /etc/ldap.conf and /etc/openldap/ldap.conf files and save it.
3. From the CLI, run "service nscd restart" for the restored configuration to take effect.
4. From the GUI, save the LDAP configuration.
5. Verify that the restored configuration is working as before.
Feedback
Yes
No
Powered by
