Recently active topics

A common form of authentication used in SFTP transfers is Public Key authentication. In this form of authentication, the SFTP client creates a public and private key pair, and shares the public key with the SFTP Server admin. When authenticating, the SFTP client sends a small message signed with its private key that is verified by the server. This form of authentication is generally considered stronger than password authentication.  One of the most common tools for creating the key pair is through a free tool called PuTTYgen, which allows the user to create a new key pair:   Solution: Yes, key pairs generated via PuTTYgen can be used for both public key authentication from the client perspective in the SFTP connector and to authenticate inbound clients using the SFTP Server connector in CData Arc.  Public Key Authentication in client-side connections (SFTP connector)  To use a private key generated in PuTTYgen as your Client Certificate for public key authentication in an SFTP client, 

Tired of broken NetSuite schema replication in Microsoft Fabric?Learn how the CData JDBC Driver solves connector limitations and ensures accurate, complete data replication.Read the full guide: Resolving NetSuite Schema Replication Failures in Microsoft Fabric using CData

Hi Everyone, I'm Soumitra Dutta – Entrepreneur & Photographer Based in Oxford. I’m trying to connect my database to CData, but I’m not sure of the best approach. Could anyone share their tips, recommended connectors, or best practices for setting up a connection efficiently? I’d really appreciate your advice! RegardsSoumitra Dutta 

Hello,I just recently migrated my Arc instance to a new server.  I had been running v2023 with the old UI and I’m trying to figure out how I can ‘move’ my EDI connections (which are currently spread out across multiple workspaces) to the new Trading Partner Console.  Any help is appreciated.Thanks!

In CData Sync API connector with Bearer token authentication, currently it's not possible to provide and configure an endpoint from which a new token can be acquired. What are the other possible ways then to update the token dynamically then? This thread discusses a solution in CData Arc but I am not sure if that will be applicable here in CData Sync.This another thread discusses adding a manual bearer token in custom header for CData Sync, but how can the token value be updated dynamically?Is it possible to acquire the token in the Pre-Job event and then set it as an environment variable? Are environment variables (set up in the Pre-Job event) accessible in the Connection configuration?