Hi Riyafa,

I attached updated Google Spreadsheet connector zip file [1].
[1]
https://drive.google.com/a/wso2.com/file/d/0B-II6tSqN5NBeW9uN1lpc3F0WjQ/view?usp=sharing

Thanks

On Thu, Dec 3, 2015 at 11:55 AM, Malaka Silva <[email protected]> wrote:

> Connector (as well as the doc) is not officially released yet and at the
> final stage.
>
> You can build the connector from the pr or get a copy from Thulasika.
>
> On Thu, Dec 3, 2015 at 11:42 AM, Riyafa Abdul Hameed <[email protected]>
> wrote:
>
>> Hi,
>>
>> Where can we download the updated connector? The link [1] provided in the
>> documentation leads to capsule connector.
>>
>> [1]
>> https://store.wso2.com/store/assets/esbconnector/22bd0804-e67a-45b8-9351-af82b8b22e0a
>>
>> Thanks.
>>
>> On Thu, Dec 3, 2015 at 11:29 AM, Thulasika Vijayanathan <
>> [email protected]> wrote:
>>
>>> Hi All,
>>>
>>> Please find the updated documentation [1].
>>> 1.
>>> https://docs.wso2.com/display/CONNECTORS/Google+Spreadsheet+REST+Connector
>>>
>>> Thanks
>>>
>>> On Thu, Dec 3, 2015 at 9:56 AM, Dimuthu Leelarathne <[email protected]>
>>> wrote:
>>>
>>>> Hi Nadeeshan,
>>>>
>>>> Documentation says, refresh token never expires. From google - [1]. But
>>>> this is OAuth, and according to spec, Consumer secret and key doesn't
>>>> expire and can be stored in application. Could we see how that can be
>>>> applied to the Connector?
>>>>
>>>>
>>>> [1] Note: The OAuth Playground does not store refresh tokens, but as
>>>> refresh tokens never expire, user should go to their Google Account 
>>>> Authorized
>>>> Access <https://accounts.google.com/IssuedAuthSubTokens> page if they
>>>> would like to manually revoke them.
>>>>
>>>> thanks,
>>>> Dimuthu
>>>>
>>>> On Thu, Dec 3, 2015 at 9:51 AM, Nadeeshaan Gunasinghe <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Dimuthu,
>>>>>
>>>>> I think we cannot use the same refresh token over and over again to
>>>>> get new access tokens. When we get a new access token, we get a new 
>>>>> refresh
>>>>> token along with. So we have to use that new refresh token to get the the
>>>>> next access token. Please clarify if I am wrong :)
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> *Nadeeshaan Gunasinghe*
>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>> +94770596754 | [email protected] | Skype: nadeeshaan.gunasinghe
>>>>> <#1516684674b69206_15166789bd94fbb8_151666c28f29545d_1516617907ad2eb6_1516612dccbec008_>
>>>>> <http://www.facebook.com/nadeeshaan.gunasinghe>
>>>>> <http://lk.linkedin.com/in/nadeeshaan>
>>>>> <http://twitter.com/Nadeeshaan>  <http://nadeeshaan.blogspot.com/>
>>>>> Get a signature like this: Click here!
>>>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=>
>>>>>
>>>>> On Thu, Dec 3, 2015 at 9:04 AM, Malaka Silva <[email protected]> wrote:
>>>>>
>>>>>> Thulasika guess we have done it. Seems missing in the docs. [1]?
>>>>>>
>>>>>> This will become handy with esb 4.10 property mediator
>>>>>> registry persistence improvement.
>>>>>>
>>>>>> [1]
>>>>>> https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Google+Spreadsheet+Operations
>>>>>>
>>>>>> On Thu, Dec 3, 2015 at 8:58 AM, Dimuthu Leelarathne <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi Thulasika,
>>>>>>>
>>>>>>> Could we improve the Google Connector such that given the refresh
>>>>>>> token, it would self generate an access token, as Refresh tokens never
>>>>>>> expire?
>>>>>>>
>>>>>>> Right now app has to take the responsibility of generating an access
>>>>>>> token.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Dimuthu
>>>>>>>
>>>>>>> --
>>>>>>> Dimuthu Leelarathne
>>>>>>> Director
>>>>>>>
>>>>>>> WSO2, Inc. (http://wso2.com)
>>>>>>> email: [email protected]
>>>>>>> Mobile : 0773661935
>>>>>>>
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Malaka Silva
>>>>>> Senior Tech Lead
>>>>>> M: +94 777 219 791
>>>>>> Tel : 94 11 214 5345
>>>>>> Fax :94 11 2145300
>>>>>> Skype : malaka.sampath.silva
>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>>>
>>>>>> WSO2, Inc.
>>>>>> lean . enterprise . middleware
>>>>>> http://www.wso2.com/
>>>>>> http://www.wso2.com/about/team/malaka-silva/
>>>>>> <http://wso2.com/about/team/malaka-silva/>
>>>>>> https://store.wso2.com/store/
>>>>>>
>>>>>> Save a tree -Conserve nature & Save the world for your future. Print
>>>>>> this email only if it is absolutely necessary.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Dimuthu Leelarathne
>>>> Director
>>>>
>>>> WSO2, Inc. (http://wso2.com)
>>>> email: [email protected]
>>>> Mobile : 0773661935
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Thulasika
>>> Associate Software Engineer
>>> Mobile:0778014295
>>> email: [email protected] <[email protected]>
>>>
>>
>>
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineering intern, WSO2
>>
>> Email: [email protected]
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: [email protected] <[email protected]>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to