Configuring GoodData Operations

To use the GoodData connector, add the <gooddata.init> element in your configuration before carrying out any other operations. GoodData uses cookie-based authentication. Through the login API resource, the user name and password are authenticated and the Super Secure Token (SST) is returned if the authentication is valid. Using this SST, a Temporary Token (TT) is then returned, which is subject to expiry.

init

<gooddata.init>
	<remember>{$ctx:remember}</remember>
    <username>{$ctx:username}</username>
    <apiUrl>{$ctx:apiUrl}</apiUrl>
    <password>{$ctx:password}</password>
</gooddata.init>

Properties

remember: Whether to remember the user login.
username: The user name of the account.
apiUrl: The URL of the GoodData API.
password: The password of the account.

Additional information

Ensure that the following Axis2 configurations are added and enabled in the <ESB_HOME>\repository\conf\axis2\axis2.xml file.

Required message formatters

messageFormatters

<messageFormatter contentType="text/html" class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>

Required message builders

messageBuilders

<messageBuilder contentType="text/html" class="org.wso2.carbon.relay.BinaryRelayBuilder"/>

Now that you have connected to GoodData, use the information in the following topics to perform various operations with the connector.

To ensure the security of the customer's sensitive data (e.g., user name and password), proxy services should only allow HTTPS access to ensure transport-level security. The transports property in the <proxy> element in your ESB configuration restricts the access to HTTPS only (<proxy transports="https"/>).