On Mon, Jan 27, 2014 at 8:42 PM, Gayan Yalpathwala <[email protected]> wrote:
> Goto https://dev.twitter.com/apps and create a new application. Here you > have to provide some basic information about the app. > Once the app is created it will show you the following artifacts which you > need to use in <twitter.init> operation. > [Consumer key, Consumer secret, Access token, Access token secret] > Prior to deploying, visit > https://api.twitter.com/oauth2/token<https://www.google.com/url?q=https%3A%2F%2Fapi.twitter.com%2Foauth2%2Ftoken&sa=D&sntz=1&usg=AFQjCNE4_apO1KFJZjWn-dwt_6XfwAOR-Q> > on > your browser and click on the https trust icon on address bar and follow > Connection tab. > Click certificate information and follow details tab on the appearing > dialog. There use 'Export' option to export the trust certificate to the > file system. > Then use the following command to import that certificate into ESB client > trust store. > keytool -importcert -file <certificate file> -keystore > <ESB>/repository/resources/security/client-truststore.jks -alias > "TwitterTrustCertImport" > After this, restart the server and deploy the twitter configuration. This is exactly the kind of guidance I want to be able to give our users, as they shouldn't have to navigate all over Twitter's documentation and ours to get the high-level steps for this. Thanks so much! -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
