Test Connection is getting failed in data factory for Mongo DB

ADMMMLIFEADFADMIN 0 Reputation points
2024-03-01T09:45:38.9033333+00:00

Test Connection is failing in datafactory for Mongo DB.

Note, Ips are whitelisted but i am getting the below error.

Failed to operate data via MongoDB client. An exception occurred while opening a connection to the server. Exception has been thrown by the target of an invocation. This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Can you please guide us on the same. How to connect to Mongo DB. Or shall i use any other way for the same.

User's image

Azure SQL Database
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,807 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Vinodh247 22,871 Reputation points
    2024-03-01T14:03:57.84+00:00

    Hi ADMMMLIFEADFADMIN,

    Thanks for reaching out to Microsoft Q&A.

    Looks like the error is due to compliance standards. The error indicates an issue related to FIPS (Federal Information Processing Standards) compliance in the cryptographic algorithms used by MongoDB. By definition FIPS is...

    FIPS is a set of standards that describes document processing, encryption algorithms, and other information technology standards for use within non-military government agencies and by government contractors and vendors who work with those agencies.

    narrow down/fix the issue by trying the below options sequentially.

    1. If your organization allows it, you can disable FIPS compliance on your Windows system. However, keep in mind that this might not be acceptable due to security policies, check with your admin team.
    2. Ensure that you are using MongoDB drivers that are FIPS compliant. MongoDB provides FIPS-compliant builds of its drivers for various platforms. Make sure you are using the appropriate FIPS-compliant driver for your setup.
    3. Ensure that you are using a version of MongoDB that supports FIPS compliance. MongoDB has made efforts to support FIPS-compliant cryptographic algorithms in later versions. Upgrading to a newer version might resolve the issue -give it a try if possible.
    4. Verify your MongoDB configuration settings to ensure that it is set up to use FIPS-compliant cryptographic algorithms if required.
    5. Check Windows FIPS Policy: Ensure that the Windows FIPS policy is correctly configured and enforced. You may need to work with your IT department to verify and adjust these settings if necessary.
    6. If you have a MongoDB support, consider reaching out to their support team for assistance in resolving this issue swiftly.

    Note: In the above there might/will be critical changes which has to be discussed with your org security team before turning on/off any settings.

    Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.