This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

To use the Eloqua connector, add the <eloqua.init> or <eloqua.getAccessTokenFromCode> or <eloqua.getAccessTokenFromRefreshToken>  element in your configuration before carrying out any other Eloqua operations.To authenticating using HTTP basic authentication add <eloqua.init> element in your configuration before carrying out any other Eloqua operations.

init
<eloqua.init>
	<siteName>{$ctx:siteName}</siteName>
	<username>{$ctx:username}</username>
	<password>{$ctx:password}</password>	
	<apiVersion>{$ctx:apiVersion}</apiVersion>	
</eloqua.init>
properties
  • siteName: The site name of the user.

  • username: The username of the user.

  • password: The password of the user.

  • apiVersion: The version of the API.

For more information on authentication, see

http://docs.oracle.com/cloud/latest/marketingcs_gs/OMCBB/index.html#C_Tutorials/authenticate-using-basic-auth.htm%3FTocPath%3DTutorials%7C_____1

Be sure to import the Eloqua certificate to your ESB client keystore.

You can follow the following steps to import your Eloqua certificate into wso2esb client’s keystore as follows:

  1. View the certificate details (the steps vary by browser) and then export the trust certificate to the file system.

  2. Use the ESB Management Console or the following command to import that certificate into the ESB client keystore. keytool -importcert -file <certificate file> -keystore <ESB>/repository/resources/security/client-truststore.jks -alias "EloquaTrustCertImport"

  3. Restart the server and deploy the Eloqua configuration.

To authenticate using OAuth2 add <eloqua.getAccessTokenFromCode> or <eloqua.getAccessTokenFromRefreshToken> element in your configuration.

getAccessTokenFromCode
<eloqua.getAccessTokenFromCode>
	<code>{$ctx:code}</code>
	<redirectUri>{$ctx:redirectUri}</redirectUri>
	<clientId>{$ctx:clientId}</clientId>
	<clientSecret>{$ctx:clientSecret}</clientSecret>
	<apiVersion>{$ctx:apiVersion}</apiVersion>
</eloqua.getAccessTokenFromCode>
properties
  • code: The value of the authorization code.

  • clientId: The value of your client id given when you registered your application with Eloqua.
  • clientSecret: The value of your client secret given when you registered your application with Eloqua.

  • redirectUri: Same redirect_uri that you passed to get code.

  • apiVersion: The version of the API.

getAccessTokenFromRefreshToken
<eloqua.getAccessTokenFromRefreshToken>
	<refreshToken>{$ctx:refreshToken}</refreshToken>
    <scope>{$ctx:scope}</scope>
    <redirectUri>{$ctx:redirectUri}</redirectUri>
    <clientId>{$ctx:clientId}</clientId>
    <clientSecret>{$ctx:clientSecret}</clientSecret>
    <apiVersion>{$ctx:apiVersion}</apiVersion>
</eloqua.getAccessTokenFromRefreshToken>
properties
  • refreshToken: The value of the refresh token.

  • scope: The scope of the token.
  • redirectUri: Same redirect_uri that you passed to get code.
  • clientId: The value of your client id given when you registered your application with Eloqua.
  • clientSecret: The value of your client secret given when you registered your application with Eloqua.

  • apiVersion: The version of the API.

For more information on authentication, see

http://docs.oracle.com/cloud/latest/marketingcs_gs/OMCBB/index.html#C_Tutorials/authenticate-using-oauth.htm%3FTocPath%3DTutorials%7C_____2

Now that you have connected to Eloqua, use the information in the following topics to perform various operations with the connector. After you have completed your configurations, see Testing the Eloqua Integration.

  • No labels