JSON

Connecting to JSON Data Sources

Below is an overview of the authentication properties corresponding to each data source:

Connecting to Local Files

Set the URI to a JSON file.

Below is an example connection string:

Connecting to HTTP JSON Streams

Set the URI to the HTTP or HTTPS URL of the JSON resource you want to access as a table. Set AuthScheme to use the following authentication types. The provider also supports OAuth authentication;

• HTTP

  To use HTTP Basic or Digest, set the User and Password. Set CustomHeaders if you need access to the request headers. Set CustomUrlParams to modify the URL query string.

• Windows (NTLM)

  Set the Windows User and Password to connect and set AuthScheme to "NTLM".

• Kerberos and Kerberos Delegation

  To authenticate with Kerberos, set the User and Password and set AuthScheme to NEGOTIATE. To use Kerberos Delegation, set AuthScheme to KERBEROSDELEGATION.

For example:

Connecting to Amazon S3

Set the URI to a JSON document in a bucket. Additionally, set the following properties to authenticate:

• AWSAccessKey: Set this to an Amazon Web Services Access Key (a username).

• AWSSecretKey: Set this to an Amazon Web Services Secret Key.

For example:

Optionally, specify AWSRegion.

Connecting to Wasabi

Set the URI to the bucket and folder. Additionally, set the following properties to authenticate:

• AWSAccessKey: Set this to an Wasabi Access Key (a username)

• AWSSecretKey: Set this to an Wasabi Secret Key.

For example:

Optionally, specify AWSRegion in addition.

Connect to Azure Blob Storage

Set the URI to the name of your container and the name of the blob. Additionally, set the following properties to authenticate:

• AzureAccount: Set this to the account associated with the Azure blob.

• AzureAccessKey: Set the to the access key associated with the Azure blob.

For example:

Connecting to Google Drive

Set the URI to the path to a JSON file. To authenticate to Google APIs, use the OAuth authentication standard. You can connect with a user account or a service account. In the user account flow, you do not need to set any connection properties for your user credentials, as shown in the connection string below:

Connecting to Box

Set the URI to the path to a JSON file. To authenticate to Box, use the OAuth authentication standard. You can authenticate with a user account or a service account. In the user account flow, you do not need to set any connection properties for your user credentials, as shown in the connection string below:

Connecting to Dropbox

Set the URI to the path to a JSON file. To authenticate to Dropbox, use the OAuth authentication standard. You can authenticate with a user account or a service account. In the user account flow, you do not need to set any connection properties for your user credentials, as shown in the connection string below:

Connecting to SharePoint Online

Set the URI to a document library containing JSON files. To authenticate, set User and Password and SharepointUrl.

Connecting to FTP

Set the URI to the address of the server followed by the path to a JSON file. To authenticate, set User and Password.

Securing JSON Connections

By default, the provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats to do so.