view release on metacpan or  search on metacpan

adwords.properties  view on Meta::CPAN

# Please see http://code.google.com/apis/adwords/docs/headers.html
# for an overview of header information.

# A string of your choosing, used to identify your application.
userAgent=INSERT_USER_AGENT_HERE

# A 22 character Developer Token.
developerToken=INSERT_DEVELOPER_TOKEN_HERE

# To use an alternative URL in case you want to manually proxy your requests
# or fake the API servers.
# alternateUrl=https://my-fake-server-address

# The Client Customer ID of the client account your application will access.
# This can be programmatically set in the Client object as
# $client->set_client_id
clientId=INSERT_CLIENT_CUSTOMER_ID_HERE

### Peer verification of SSL certificates ###
#
# To avoid spoofing attacks, enable either a CAPath or CAFile for SSL
# certificates validation.
#
# This library can use two different underlying SSL modules either
# IO::Socket::SSL or Crypt::SSLeay, being IO::Socket::SSL the default and
# recommended since it can do certificate authenticity validation as well as
# hostname validation while Crypt::SSLeay does not support hostname validation.

# The certificate authority directory to search in when performing peer
# validation. For example: /etc/ssl/certs
# CAPath=<PATH TO CERTIFICATE AUTHORITY DIRECTORY>

# The certificate authority file to use when performing peer validation.
# For example: /etc/ssl/certs/ca-certificates.crt
# CAFile=<PATH TO CERTIFICATE AUTHORITY FILE>

### Authorization Mechanisms ###
#
# The library supports the OAuth2, OAuth1.0a and ClientLogin mechanisms. Need to
# choose one, un-comment and fill in its details.
#
# More details about authorization options supported by the library can be found
# in the README, section "Authorization Options".
#
# Also to learn more about API authorization please visit
# https://developers.google.com/accounts/docs/GettingStarted

### OAuth2 ###

# Un-comment the following keys to use OAuth 2 authorization.
# All these values are found in the Google API Console.
#
# oAuth2ClientId=INSERT_OAUTH_CLIENT_ID_HERE

# For the Web/Installed Applications flow, un-comment the following.
#
# oAuth2ClientSecret=INSERT_OAUTH_CLIENT_SECRET_HERE
#
# Then you need one of the following two options.
#
# Option 1: un-comment the following if you already have OAuth2 authorization
# tokens.
# oAuth2AccessToken=INSERT_OAUTH_TOKEN_HERE
# oAuth2RefreshToken=INSERT_OAUTH_TOKEN_HERE
#
# Option 2: Use the library to trigger the authorization flow and have the
# user authorize access to his account. See the
# examples/oauth/generate_offline_credentials.pl to learn how to use the
# library for requesting user authorization.
#
# Optionally, un-comment the following if you want to change defaults for the
# user interaction flow.
# Default offline
# oAuth2AccessType=[online|offline]
# Default auto
# oAuth2ApprovalPrompt=[force|auto]
# Defaults to urn:ietf:wg:oauth:2.0:oob
# oAuth2RedirectUri=INSERT_REDIRECT_URI_HERE

# For the Service Accounts flow, un-comment the following.
#
# In order to user the library for service accounts you need to transform your
# p12 certificate as generated by the Google API Console to PEM format. And make
# sure no password is set.
# In Linux/Unix systems with openssl installed you can execute.