Akana API Hook

![Image of Akana] (https://www.akana.com/img/formerlyLOGO8.png)
Akana.com

Twitter-API-Hook

API Hook using SOA Software's Products to interact with the Twitter API. Also, integrates with Twitter's OAuth authorization steps.

Twitter API

About the API

The Twitter API.
API Documentation: Twitter API Documents

Pre-Reqs

Create a Twitter Developer account at Twitter Developers and define your application.
- Click on the 'Create New App' button.
- Enter the name of your application.
- Enter a description for your application.
- Enter the Website of your application.
- If necessary, enter the Callback URL that if required for OAuth 1.0a
- Accept the agreement and click on 'Create your Twitter appliction' button.
You must install the pso extension custom policies
- unzip the com.akana.pso.apihooks.extensions_7.2.0.zip (available in this repository) into the /sm70 directory.
- unzip the com.akana.pso.apihooks.technology.preview_7.2.90.zip (available in this repository) into the /sm70 directory.
- unzip the com.akana.pso.persistence_7.2.0.zip (available in this repository) into the /sm70 directory.
- stop all PM and ND nodes
- Run the configurator in update mode for all PM and ND instances:
  - Run this command, depending on your environment:
    - Windows: <Gateway base dir>\sm70\bin\startup.bat configurator -Dsilent=true -DdeploymentName=Standalone -Dproperties=C:\\myprops.properties
    - UNIX/Linux: <Gateway base dir>/sm70/bin/startup.sh configurator -Dsilent=true -Dproperties=/export/home/username/myprops.properties
    - The myprops.propertis path must be the fully qualified path, and the file contents will look like:
```
container.instance.name=<instance name, e.g. PM>
wizard.mode=update
```
- Using the SOA Admin Console, install the following Plug-ins in each PM container:
  - Akana PSO Persistence
- Using the SOA Admin Console, install the following Plug-ins in each ND container:
  - Akana APIHooks Enhancements
- Restart all PM and ND containers.

Getting Started Instructions

Download and Import

Download org_Twitter_API_Hook_export.zip
Download the migration.properties file, and edit it to replace the text with the 'Container Key' of the ND or ND cluster in your target PM.
- The container key is found by going to the 'Details Tab' of the ND, or ND Cluster, defined in the Policy Manager Console. Looking at the 'Container Overview' tab on that page, copy the 'Container Key:' value.
- Login to Policy Manger, example: https://:
- Select the root 'Registry' organization and click on the 'Import Package' from the Action Portlet window on the right side of the screen
  - Click on the button to browse for the org_Twitter_API_Hook_export.zip archive file
  - Make sure to select the migrations.properties file.
  - Click OK button to start the importation of the hook.
- This will create a 'Twitter API Hook Organization' with the requisite artifacts to run the API.

Verify Import

Expand the service folder in the 'Twitter API Hook' you imported and find 'Twitter_API_vs0'

Activate Anonymous Contract

Expand the contracts folder in the 'Twitter API Hook' you imported and find the 'Twitter Anonymous' contract under the 'Provided Contracts' folder.
Click on the 'Activate Contract' workflow activity in the right hand Activities portlet.
Ensure that the status changes to 'Workflow is Completed'

Configure Security

Go to Twitter API Hook --> Policies --> Operational Policies --> ProcessVariables policy
- Click 'modify' in the XML Policy Tab. An XML Policy content editor dialog will be displayed.
- Change the value of the 'redirectURI' element to be the 'Redirect URL' value you added in the Twitter Developers Application Console, from above.
- Save the changes
- Click on the 'Activate Policy' workflow activity in right hand Activities portlet.
- Validate that the status changes to 'State: Active'

####Verify Connectivity Twitter API offers using 2-legged OAuth2 to consume specific API's. Akana Software's Twitter API Hook are successfully authenticated using Twitter's OAuth2 API's.

The figure below shows the entire OAuth2 2-Legged Application-Only flow: Steps:
1-4) The consuming application requests an access token to use Twitter API's via Akana Software's API Gateway. Twitter expects the api key and api secret to be passed in a Basic Authentication header on the message. The grant type is a required parameter with the value of 'client_credentials':

Request:

    POST /oauth2/token HTTP/1.1
    Accept-Encoding: gzip,deflate
    Content-Type: application/x-www-form-urlencoded
    Authorization: Basic eHlXeTUxZmFiYnpaMlBRRktvTVlJUDJVdzp2d2dxbjFRcU91d3E2UWdvRE54WUlQREhjSXh6bjRxTHBpOGJZT0RNaGlkblpWakRXWA==
    Content-Length: 29
    Host: enord-macbook-pro.local:9920
    Connection: Keep-Alive
    User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

Response:

    HTTP/1.1 200 OK
    Content-Type: application/json;charset=utf-8
    Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
    content-disposition: attachment; filename=json.json
    Date: Mon, 18 May 2015 13:25:32 GMT
    Expires: Tue, 31 Mar 1981 05:00:00 GMT
    Last-Modified: Mon, 18 May 2015 13:25:32 GMT
    ml: A
    Set-Cookie: guest_id=v1%3A143195553271495424;Domain=.twitter.com;Path=/;Expires=Wed, 17-May-2017 13:25:32 UTC
    status: 200 OK
    strict-transport-security: max-age=631138519
    x-connection-hash: 367252cdcf4c0f282032293078848c3c
    x-content-type-options: nosniff
    x-frame-options: SAMEORIGIN
    x-response-time: 17
    x-transaction: ef6f24c4ddbfc530
    x-tsa-request-body-time: 0
    x-twitter-response-tags: BouncerCompliant
    x-ua-compatible: IE=edge,chrome=1
    x-xss-protection: 1; mode=block
    Transfer-Encoding: chunked
    Server: Jetty(7.6.10.v20130312)

    {"token_type":"bearer","access_token":"AAAAAAAAAAAAAAAAAAAAAArPfgAAAAAAEbfGdNpuDl%2FYCIC7Dx0%2FGgkbMEs%3DrX8NQm2O0a7eHUBGkhQ6ADfHgFGn2ZJEUvBcY5IoIc7rgpUkgK"}

5-8) The consuming application requests an actual API using the access token that was returned from Twitter's OAuth2 call: