Adapter Online Help > TDV Google Contacts Adapter > Advanced Settings
 
Advanced Settings
Register Your Own OAuth Application
The OAuth user consent flow involves the authenticating user to interact with Google using the browser. To facilitate this, the adapter is already registered as an OAuth application, but you may need to configure values specific to your application or organization. You may also want to display your own information instead of the CData app's when users log in to grant permissions.
Follow the steps below to register an app to obtain the credentials needed for your application:
1.Log into the Google API Console and open a project. Select the API Manager from the main menu.
2.Click Credentials -> Create Credentials -> OAuth Client Id. Click Other.
3.Click Library and enable the Drive, Calendar, and Contacts APIs. To enable an API, click the API and then click Enable API.
After creating the app, the OAuthClientId and OAuthClientSecret are displayed. You can then follow the connection guide in Connecting to GoogleContacts by setting these two additional values when you authenticate.
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 and in addition set the following.
To authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
To connect to other proxies, set FirewallType, FirewallServer, and FirewallPort. To tunnel the connection, set FirewallType to TUNNEL. To authenticate to a SOCKS proxy, set FirewallType to SOCKS5. Additionally, specify FirewallUser and FirewallPassword.
Troubleshooting the Connection
To show adapter 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 adapter'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.