Looks good please proceed. For your point #2 don't store the token in files but rather keep that in memory.
Regards Suho On Wed, Jun 1, 2016 at 10:19 PM, Geesara Prathap <[email protected]> wrote: > Hi All, > > I am to implement a new data provider which requires getting data from > some third party REST API for gadgets generation wizard in DS. These are > the authorization methods which are to support in this implementation. > > > Authorization Method > > Required Fields > > No Auth > > Basic Auth > > Username, password > > OAuth2 with password grant type > > Auth URL > > Client id and client secret > > Scope > > Username > > Password > > OAuth2 with client credentials grant type > > Auth URL > > Client id and client secret > > Scope > > 1. Do we need to support any additional authorization mechanisms? > 2. The access token is temporally stored in a configuration file since > this is only required for gadget generation. Is there any concern on this? > > Thanks, > Geesara > > -- > Geesara Prathap Kulathunga > Software Engineer > WSO2 Inc; http://wso2.com > Mobile : +940772684174 > > -- *S. Suhothayan* Technical Lead & Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
