Hi, in order to make a change to the LDAP configuration, you should use the LDAP configuration script:
https://montier.atlassian.net/wiki/spaces/DPOD011500/pages/14274723968/LDAP+Configuration+ScriptThe script expects to get a configuration file with all the LDAP parameters and a test user, and tests the configuration before applying it, so it is very unlikely that you will get locked out of the system.
You can run the script from an SSH session or from the Admin Console (https://montier.atlassian.net/wiki/spaces/DPOD011500/pages/14274724429/Admin+Console).
This script also allows you to disable the LDAP, so even if you have an issue with the LDAP configuration, you can always disable it and go back to the internal user repository, or fix the issue and run the LDAP configuration script again.
The Web Console doesn't have a fallback user. However, the Admin Console does, exactly for this scenario where you have an LDAP issue and you want to fix the LDAP configuration or disable it through the Admin Console.
------------------------------
Amit Munwes
------------------------------
Original Message:
Sent: Fri January 28, 2022 12:59 PM
From: Jennifer Stipe
Subject: DPOD v1.0.11 - is there a fallback user in case of an issue with ldap?
Hello!
I'd like to make a change to our ldap settings on our dpod appliance (v1.0.11). However I am concerned that if I make a mistake in the ldap connection setup and it fails I will then be unable to log back into the appliance. Usually products have a fallback user (Datapower and api connect both have a fallback admin user) for this issue. I tried the default admin credentials but they do not work on our dpod installation. The root account can only log into the OS, not the webgui.
Is there a fallback user like admin for dpod? If not how do I ensure I can safely log back into the box if there is an issue with ldap?
------------------------------
Jennifer Stipe
------------------------------