I am pretty much new to setting up LDAP with Ambari server. So I wanted to understand where the details entered during LDAP setup are stored/cached. Whenever I try to do ambari-server setup-LDAP, I am getting the following error.
Fetching LDAP configuration from DB.ERROR: Exiting with exit code 1. REASON: Error while fetching LDAP configuration. Error details: HTTP Error 403: Forbidden
Here I am not sure what exactly DB means. So please help me in understanding what happens in background when I try to do LDAP setup or sync. I am trying to connect to an AD hosted in a remote machine.
When you do ambari-server ldap setup, everything gets stored in the database which your ambari server is using/configured while installation probably postgres or any other whichever you have used.
I would suggest you to check your LDAP configuration which you have used/passed for integrating ambari with ldap. As per above error, there is a issue with authorization while ldap integration. its not with DB but LDAP. LDAP Configuration or bind user would be possible reason for your issue.
Please accept this answer if it helps you resolve your issue and share with the community.
Thank you for the inputs. Another new observation is the issue occurs when ambari-server is connecting to MariaDB as there were two different databases. When the database value is changed authentication works and is able to sync data from LDAP.
Ambari server uses appropriate database base connector which is located under /user/share/java/*<databasename>.jar
This same connector jar is used to connect to any external or internal database. It needs to be mentioned using ambari-server --jdbc * command.
Refer documentation for exact command.
Issue could be due to the connector jar that is configured for ambari to use. For eg. Ambari is configured to use postgres but you are trying to connect to Mariadb and since it doesn't has the proper jar configured, it won't connect and you will face issue.
Let me know if this resolves your issue. Else please share the screen shot and error logs to check further.