Establishing a Connection
Authenticating to Wasabi
To authorize Wasabi requests, provide the credentials for an administrator account or for an IAM user with custom permissions by setting the following properties:
- Set AccessKey to the access key Id.
- Set SecretKey to the secret access key.
Note: You can connect as the AWS account administrator, but it is recommended to use IAM user credentials to access Wasabi services.
Obtaining the Access Key
To obtain the credentials for an IAM user:
- Sign in to the AWS console.
In the navigation pane, select IAM.
- To create or manage the access keys for a user, select the Access Keys tab.
- Click Create New Access Key and use the credentials that will be displayed in the csv file to authenticate to Wasabi services.
Authenticating as an IAM Role
In many situations, it may be preferable to use an IAM role for authentication instead of the direct security credentials of an AWS account root user. An IAM role may be used by specifying the RoleARN. This will cause the CData ADO.NET Provider for Wasabi 2019 to attempt to retrieve credentials for the specified role.
If you are connecting to Wasabi (instead of already being connected such as on an EC2 instance), you must additionally specify the AccessKey and SecretKey of an IAM user to assume the role for. Roles may not be used when specifying the AccessKey and SecretKey of an AWS account root user.
Authenticating with SSO
For users and roles that require SSO Authentication, specify the RoleARN and PrincipalArn connection properties. You must also specify the SSOProperties, which is specific for each Identity Provider and leave AccessKey and SecretKey empty. This will cause the CData ADO.NET Provider for Wasabi 2019 to submit the SSO credentials in a request to retrieve temporary authentication credentials.
Connecting to Wasabi
In addition to the AccessKey and SecretKey properties, specify Region. Set Region to the region where your Wasabi data is hosted. The default value for the Region is set to "NORTHERNVIRGINIA".
Customizing the SSL Configuration
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.
Connecting Through a Firewall or Proxy
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
- To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
- To tunnel the connection, set FirewallType to TUNNEL.
- To authenticate, specify FirewallUser and FirewallPassword.
- To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.
Troubleshooting the Connection
To show provider activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.
- Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
- Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.
- The certificate presented by the server cannot be validated: This error indicates that the provider cannot validate the server's certificate through the chain of trust. If you are using a self-signed certificate, there is only one certificate in the chain.
To resolve this error, you must verify yourself that the certificate can be trusted and specify to the provider that you trust the certificate. One way you can specify that you trust a certificate is to add the certificate to the trusted system store; another is to set SSLServerCert.