On Fri, Dec 4, 2015 at 7:57 PM, Malaka Silva wrote:
> Well IMO we don't need a new set of connectors to support esb 4.10. What
> we need to do is enhance existing connector base.
>
I meant that we need new versions of connectors that are capable of
supporting refresh tokens. But they will be comp
Well IMO we don't need a new set of connectors to support esb 4.10. What we
need to do is enhance existing connector base.
We are already planning to do this based on automation scnarios/use cases
(Starting with internal operations).
The idea is to increase method coverage and include method as K
We need to get started with the new version of connectors (compatible with
4.10) that includes refresh token support for most commonly used
connectors. Can we prioritize all such connectors and come up with a list
please. They should be released along with 4.10.
On Wed, Dec 2, 2015 at 10:51 AM, Ma
Resolved the jira. Check the functionality on pre release pack and seems to
be working.
On Wed, Dec 2, 2015 at 10:14 AM, Kasun Indrasiri wrote:
> I think all the required changes are already merged into ESB 4.10. If so
> can we resolve the jira?
>
> On Wed, Dec 2, 2015 at 9:45 AM, Rajjaz Mohamme
I think all the required changes are already merged into ESB 4.10. If so
can we resolve the jira?
On Wed, Dec 2, 2015 at 9:45 AM, Rajjaz Mohammed wrote:
> Hi Nadeeshan,
> avoiding the access token expiration is really important feature for
> connector's stability. i hope it will work with all ki
Hi Nadeeshan,
avoiding the access token expiration is really important feature for
connector's stability. i hope it will work with all kind of connectors
which are need access tokens not only with Google connectors.
On Wed, Dec 2, 2015 at 9:23 AM, Malaka Silva wrote:
> Yes this is a required fea
Yes this is a required feature for many use cases. I guess we have missed
it from esb 490 release.
Added jira[1] to track this for esb 4.10 release.
[1] https://wso2.org/jira/browse/ESBJAVA-4346
On Tue, Dec 1, 2015 at 10:12 PM, Nadeeshaan Gunasinghe
wrote:
> Hi all,
> It has become a vital req
Hi all,
It has become a vital requirement to avoid access tokens being expired
which are used in the connectors. This issue can be avoided at the
connector level, using the refresh tokens provided by the corresponding
api. In order to have this requirement fulfilled we wanted to use the
persistent
