Hi Dushan, OAuth 2.0 flow includes the redirection to the OAuth Dialog Page[1]. Is there any workround to handle this within the ESB?
[1] https://developer.surveymonkey.com/mashery/guide_oauth Thanks BR Indika Kularathne On Wed, Mar 19, 2014 at 7:53 AM, Dushan Abeyruwan <[email protected]> wrote: > Hi > Can't we find a better approach of getting access-token, this has to be > automated (better approach is to use OAuth 2.0 flow) implemented within > the connector rather passing access? > > [1] https://developer.surveymonkey.com/mashery/guide_oauth > > Cheers, > Dushan > > > On Fri, Mar 14, 2014 at 8:02 PM, indika prasad <[email protected]>wrote: > >> *Introduction* >> SurveyMonkey is the world's leading provider of web-based survey >> solutions, >> helping people gather the insights they need to make more informed >> decisions. >> >> *SurveyMonkey Connector Summery* >> * Connector Name: SurveyMonkey >> * API Version: v2 >> * Technology: REST >> * API Url: https://api.surveymonkey.net >> >> >> *Authentication* >> oauth2 access token use to access the API [0] method. >> >> Selected Methods (8) for version 1.0.0 >> >> *getSurveyList *- Retrieves a paged list of survey user's >> account. >> *getSurveyDetails *- Retrieve a given survey's metadata. >> *getCollectorList *- Retrieves a paged list of collectors for a >> survey in a >> user's account. >> *getRespondentList *- Retrieves a paged list of respondents for a >> given >> survey and optionally collector >> *getResponses *- Takes a list of respondent ids and returns the >> responses >> that correlate to them. To be used with 'getSurveyDetails' >> *getResponseCounts *- Returns how many respondents have started >> and/or >> completed the survey for the given collector >> *getUserDetails *- Returns basic information about the logged-in >> user >> *init *- Config operation >> >> /Note: >> All API requests return HTTP 200 (OK) with a JSON payload that includes a >> status key containing one of the following codes. [1] >> 0 Success >> 1 Not Authenticated >> 2 Invalid User Credentials >> 3 Invalid Request >> 4 Unknown User >> 5 System Error >> >> Example Response: >> { >> "data": { >> "completed": 10, >> "started": 1 >> }, >> "status": 0 >> }/ >> >> [0] https://developer.surveymonkey.com/mashery/authentication >> [1] https://developer.surveymonkey.com/mashery/requests_responses >> >> Thanks >> Indika Kularathne >> >> >> >> >> -- >> View this message in context: >> http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-SurveyMonkey-tp93510.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 >> > > > > -- > Dushan Abeyruwan | Associate Tech Lead > Integration Technologies Team > PMC Member Apache Synpase > WSO2 Inc. http://wso2.com/ > Blog:http://dushansview.blogspot.com/ > Mobile:(0094)713942042 > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
