Adding Vinitha. On Wed, Oct 7, 2015 at 5:31 PM, Kathees Rajendram <[email protected]> wrote:
> Hi Vinitha, > > As Kesavan mentioned, we better to go with oAuth 1.0 rather than basic > authentication. To implement SalesforceDesk connector with oAuth 1.0, you > don't need to use any external Java libraries. You can use HMAC-SHA1 > signature generation method. > > You can refer Twitter2.0.0 [1] and Amazon SQS connectors which are > implemented with oAuth 1.0. > [1] - > https://github.com/wso2/esb-connectors/blob/master/twitter/twitter-connector/twitter-connector-2.0.0/org.wso2.carbon.connector/src/main/java/org/wso2/carbon/connector/twitter/TwitterSignatureGeneration.java > > Thanks, > Kathees > > On Wed, Oct 7, 2015 at 12:29 PM, Vinitha Rajenthiran < > [email protected]> wrote: > >> Hi Kesavan, >> >> We choose Basic Authentication instead of Oauth 1.0 due to the following >> reasons; >> >> 1. For Oauth1.0, a java library has not been provided, hence we need to >> use >> an external Java library (e.g: Signpost) to implement the Oauth flow. >> 2. Basic authentication is the simplest form of authentication to get you >> up >> and running with the Desk.com API. >> >> Regards, >> Vinitha >> >> >> >> -- >> View this message in context: >> http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-SalesforceDesk-tp126434p126635.html >> Sent from the WSO2 Architecture mailing list archive at Nabble.com. >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > > -- > Kathees > Software Engineer, > email: [email protected] > mobile: +94772596173 > -- Kathees Software Engineer, email: [email protected] mobile: +94772596173
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
