This message was deleted.
# secoda-supportw
wooden-spring-14915
09/26/2023, 2:48 PMThis message was deleted.
✅ 1
thankyou 1
e
elegant-house-93198
09/26/2023, 2:51 PM
Hey @thankful-baker-24993 we're investigating why the integration failure is occurring and will provide guidance on how to fix the error shortly.
elegant-house-93198
09/26/2023, 2:53 PM
@thankful-baker-24993 based on the error message, it seems that the user that you've connected MongoDB with doesn't have the correct permissions.
The required permissions are included in our documentation here. https://docs.secoda.co/integrations/databases/mongodb#creating-a-database-user. At a minimum the user needs
Only read any databaset
thankful-baker-24993
09/26/2023, 2:59 PMThanks Andrew, those are the permissions I gave the user.
I can confirm this new user can connect using the MacOS terminal.
I can also confirm that the IPs where whitelisted... in fact, I also temporarily opened it to any IP just to make sure.
Will give it another shot.
thankful-baker-24993
09/26/2023, 3:36 PMNo joy yet... do you have any sort of error log on your side with some detail? Happy to try more, yet another hint would be super useful.
Thank you!
thankful-baker-24993
09/27/2023, 1:52 AMOk, it finally worked... changed 2 things, so I am not sure what cured it...
1. Changed the name of the "mongo cluster" in the integrations tab, from the actual mongo cluster name, to the name of the database I am interested in.
2. When selecting the schema to crawl, I selected all databases, then ran the sync... then it complained that it could not access something in the "config" dB... then I deselected all the dBs except for the one I'm interested in, and voila!
Thanks @elegant-house-93198, hope this helps : )
e
elegant-house-93198
09/27/2023, 2:02 AM
Hey @thankful-baker-24993 we ended up pushing a fix this evening, so I think that plus some of the changes you made led to the resolution. Thanks for the detailed explanation
👍 1
🙌 1
✅ 1
t
thankful-baker-24993
09/27/2023, 1:44 PMThank you!