The DBA is confident about the port. If I switch the port, to say 20021, it immediately returns a failure (see pic). Only when I try to connect to that particular port does it lock up. That, along with being able to run a Test-NetConnection from powershell (see pic) tells me the port is correct. I had a working session with the DBA, but the only way he know how to connect was using MongoDBCompass so that wasn’t any help with the ODBC connector, which is what CyberArk uses typically. Even with Compass, we couldn’t get it to connect. I am going to reach back out to him to ensure he has it configured correctly per your recommendation.
Appreciate the help guys, this has me banging my head on the keyboard as I have zero control or insight of the database side.
Lastly, CyberArk can only manage the password on this via the CPM server (connects to DB, verifies or changes password), it doesn’t have the recording/audit capabilities found in a PSM connection, like you might find with other devices.
So the problem is you are trying to connect to MongoDB, but if you look at the error it mentions failure connecting to MySQL Server. I didn’t look at the screenshots in detail… but your issue is you “CANNOT” use this to connect to MongoDB. I realized, this driver is specifically for their “BI Connector” product, this is software is either in Atlas or on premise as a separate service that talks to MongoDB. You can’t run Mongo Commands through this nor would this be the right path. It’s a readonly to query database collections.
You might try to find something else?
https://docs.devart.com/odbc/mongodb/dbeaver.htm
This will also give you some ideas too: connection - Mongodb - connect through ODBC - Stack Overflow