Connecting to Pinterest
Pinterest authentication is based on the standard OAuth flow. To authenticate, you must initially create an app via the Pinterest developer's platform where you can obtain an OAuthClientId, OAuthClientSecret, and CallbackURL.
InitiateOAuth to GETANDREFRESH, OAuthClientId, OAuthClientSecret, and CallbackURL parameters will be set as connection properties to your driver.
Creating a Custom OAuth App
To obtain an OAuthClientId, OAuthClientSecret, and CallbackURL, you first need to create an app linked to your Pinterest account.
To create an app linked to your Pinterest account:
- Navigate to https://developers.pinterest.com/apps/.
- Log in to your Pinterest account.
- Click Create app, specify an app Name and Description then click on Create.
- Fill the required details in the form.
- Set the Auth Callback URL to https://localhost:33333 or a different port of your choice.
- You can choose whether your app will be accessed by multiple users or only by the owner in collaborators.
- After completing the changes the browser will prompt you to save .
Once you are done with creating a new app, it will be displayed on your screen. From there, you can click View Client ID to reveal your newly created app's Client ID and Client Secret. You can now use these credentials to connect to Pinterest by setting them as the following connection properties:
- OAuthClientId = Client Id
- OAuthClientSecret = Client Secret
- CallbackURL = Auth Callback URL
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.