subject:"\[Dev\] \[Gmail Connector\] Error connecting to gmail connector"

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-06 Thread Shakila Sivagnanarajah

Hi Maheeka,

The request payload is overridden by your payload [1]. So it can't get the
fields using json-eval which come from the request body. If you get the
value and put into the message context using property mediator, you can use
those values from context using {$ctx:from}. I tried with [2].

[1] 
{"subject":"XXX","messageBody":"This is message
body"}

 


[2]
Configuration:
http://ws.apache.org/ns/synapse;>

https://www.googleapis.com/gmail"/>






http://org.apache.synapse/xsd"/>

{$ctx:refreshToken}
{$ctx:clientId}
{$ctx:clientSecret}

{$ctx:accessTokenRegistryPath}
{$ctx:accessToken}
{$ctx:apiUrl}
{$ctx:userId}


{"to":"wso2jaffnade...@gmail.com","subject":"Test
Mail","messageBody":"This is message body","cc":"iamcoolm...@gmail.com
","bcc":"iamcoolm...@gmail.com"}


{json-eval($.to)}
{json-eval($.subject)}
{$ctx:from}
{json-eval($.messageBody)}
{json-eval($.cc)}
{json-eval($.bcc)}






Request Body:
{
  "from": "wso2jaffnad...@gmail.com"
}

Thanks

On Mon, Jun 6, 2016 at 3:12 AM, Hariprasath Thanarajah  wrote:

> Hi Maheeka,
>
> For the createAMail operation the required Parameter is raw and it is have
> the entire message(eg: to, cc, subject ,etc) and it should be in the
> base64url encoded string[1]. From that payload we are getting the "raw"[2]
> object and it is in the encoded format, that's why we can't get the
> {json-eval($.subject)}. Because in [2] we don't have the json object "
>
> *subject".*
> The connector was implemented with above logic(It is in the api
> documentaion [1])
>
> [1] -
> https://developers.google.com/gmail/api/v1/reference/users/messages/send#auth
>
> [2] -  DEBUG - wire <<
> "{"raw":"dG86dGhhcmlzNjNAZ21haWwuY29tCnN1YmplY3Q6dGVzdApmcm9tOnRoYXJpczYzQGdtYWlsLmNvbQpjYzp0aGFyaXM2M0BvdXRsb29rLmNvbQpiY2M6dGhhcmlzNjNAeWFob28uY29tCmlkOjE1NGI4YjIyNDVhZmYyMGUKdGhyZWFkSWQ6MTU0YjhiMjI0NWFmZjIwZQoKSGkgaGFyaXByYXNhdGgK"}[\r][\n]"
>
>
> On Sun, Jun 5, 2016 at 11:55 PM, Maheeka Jayasuriya 
> wrote:
>
>> Hi Hariprasath,
>>
>> I am using the connector's input schema and the default values property
>> file to set the parameters for invoking the connector's createAMail
>> operation. However, the parameter values are not picked up by the connector
>> operation. Maybe the expressions are not correct. Can you please take a
>> look? If I set as {$func:Recipient} from template parameters it works. It
>> doesn't work for {json-eval($.subject)} type parameters.
>>
>> Please find below a sample proxy service. You can use this proxy to
>> verify.
>>
>> 
>> http://ws.apache.org/ns/synapse;
>>name="SampleProxy"
>>transports="https,http"
>>statistics="disable"
>>trace="disable"
>>startOnLoad="true">
>>
>>   
>>  
>> {"subject":"XXX","messageBody":"This is message
>> body"}
>> 
>>  
>>  
>>  > scope="axis2"/>
>>  
>>  
>> {$ctx:TO}
>> {json-eval($.subject)}
>> {json-eval($.from)}
>> {json-eval($.messageBody)}
>> {json-eval($.cc)}
>> {json-eval($.bcc)}
>> {json-eval($.id)}
>> {json-eval($.threadId)}
>>  
>>  
>>   
>>
>>
>> 
>>
>> Thanks,
>> Maheeka
>>
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>> On Sat, Jun 4, 2016 at 11:55 AM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Thanks Hariprasad for taking time on helping to resolve the issue. The
>>> mentioned approach is now working.
>>>
>>> Maheeka Jayasuriya
>>> Senior Software Engineer
>>> Mobile : +9450661
>>>
>>> On Sat, Jun 4, 2016 at 10:49 AM, Hariprasath Thanarajah <
>>> haripras...@wso2.com> wrote:
>>>
 Hi Maheeka,

 If you are trying to get the refresh token and accessToken from oAuth
 playground you should refresh the refreshToken in oAuth playground only
 because in oAuth playground it sets the redirect_uri as https%3A%2F%
 2Fdevelopers.google.com%2Foauthplayground is not your app
 redirect_uri. So after one hour if you trying any method it gave the error.
 Better trying below url[1] to get the code and using [2] to get the
 refresh token.

 [1] - https://accounts.google.com/o/oauth2/auth?redirect_uri=*>>> redirect-uri>*_type=code_id=**=
 https://mail.google.com/+https://www.googleapis.com/auth/gmail.compose+https://www.googleapis.com/auth/gmail.insert+https://www.googleapis.com/auth/gmail.labels+https://www.googleapis.com/auth/gmail.modify+https://www.googleapis.com/auth/gmail.readonly+https://www.googleapis.com/auth/gmail.send_prompt=force_type=offline

 [2] - I have attached below


 From [2]  you can get the refresh_token and you can use it

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-05 Thread Hariprasath Thanarajah

Hi Maheeka,

For the createAMail operation the required Parameter is raw and it is have
the entire message(eg: to, cc, subject ,etc) and it should be in the
base64url encoded string[1]. From that payload we are getting the "raw"[2]
object and it is in the encoded format, that's why we can't get the
{json-eval($.subject)}. Because in [2] we don't have the json object "

*subject".*
The connector was implemented with above logic(It is in the api
documentaion [1])

[1] -
https://developers.google.com/gmail/api/v1/reference/users/messages/send#auth

[2] -  DEBUG - wire <<
"{"raw":"dG86dGhhcmlzNjNAZ21haWwuY29tCnN1YmplY3Q6dGVzdApmcm9tOnRoYXJpczYzQGdtYWlsLmNvbQpjYzp0aGFyaXM2M0BvdXRsb29rLmNvbQpiY2M6dGhhcmlzNjNAeWFob28uY29tCmlkOjE1NGI4YjIyNDVhZmYyMGUKdGhyZWFkSWQ6MTU0YjhiMjI0NWFmZjIwZQoKSGkgaGFyaXByYXNhdGgK"}[\r][\n]"


On Sun, Jun 5, 2016 at 11:55 PM, Maheeka Jayasuriya 
wrote:

> Hi Hariprasath,
>
> I am using the connector's input schema and the default values property
> file to set the parameters for invoking the connector's createAMail
> operation. However, the parameter values are not picked up by the connector
> operation. Maybe the expressions are not correct. Can you please take a
> look? If I set as {$func:Recipient} from template parameters it works. It
> doesn't work for {json-eval($.subject)} type parameters.
>
> Please find below a sample proxy service. You can use this proxy to verify.
>
> 
> http://ws.apache.org/ns/synapse;
>name="SampleProxy"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
> {"subject":"XXX","messageBody":"This is message
> body"}
> 
>  
>  
>   scope="axis2"/>
>  
>  
> {$ctx:TO}
> {json-eval($.subject)}
> {json-eval($.from)}
> {json-eval($.messageBody)}
> {json-eval($.cc)}
> {json-eval($.bcc)}
> {json-eval($.id)}
> {json-eval($.threadId)}
>  
>  
>   
>
>
> 
>
> Thanks,
> Maheeka
>
>
> Maheeka Jayasuriya
> Senior Software Engineer
> Mobile : +9450661
>
> On Sat, Jun 4, 2016 at 11:55 AM, Maheeka Jayasuriya 
> wrote:
>
>> Thanks Hariprasad for taking time on helping to resolve the issue. The
>> mentioned approach is now working.
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>> On Sat, Jun 4, 2016 at 10:49 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi Maheeka,
>>>
>>> If you are trying to get the refresh token and accessToken from oAuth
>>> playground you should refresh the refreshToken in oAuth playground only
>>> because in oAuth playground it sets the redirect_uri as https%3A%2F%
>>> 2Fdevelopers.google.com%2Foauthplayground is not your app redirect_uri.
>>> So after one hour if you trying any method it gave the error.
>>> Better trying below url[1] to get the code and using [2] to get the
>>> refresh token.
>>>
>>> [1] - https://accounts.google.com/o/oauth2/auth?redirect_uri=*>> redirect-uri>*_type=code_id=**=
>>> https://mail.google.com/+https://www.googleapis.com/auth/gmail.compose+https://www.googleapis.com/auth/gmail.insert+https://www.googleapis.com/auth/gmail.labels+https://www.googleapis.com/auth/gmail.modify+https://www.googleapis.com/auth/gmail.readonly+https://www.googleapis.com/auth/gmail.send_prompt=force_type=offline
>>>
>>> [2] - I have attached below
>>>
>>>
>>> From [2]  you can get the refresh_token and you can use it in the init
>>> call. Then you won't get the error.
>>>
>>> On Sat, Jun 4, 2016 at 8:09 AM, Malaka Silva  wrote:
>>>
 Yes this should be the way. Only use init method before each call.

 On Sat, Jun 4, 2016 at 8:00 AM, Shakila Sivagnanarajah <
 shak...@wso2.com> wrote:

> Hi Maheeka,
>
> Since the refreshing access token is automated in the connector, you
> can use following init configuration.
>
>  
> {$ctx:refreshToken}
> {$ctx:clientId}
> {$ctx:clientSecret}
>
> {$ctx:accessTokenRegistryPath}
> {$ctx:accessToken}
> {$ctx:apiUrl}
> {$ctx:userId}
> 
> 
> {$ctx:to}
> {$ctx:subject}
> {$ctx:from}
> {$ctx:messageBody}
> {$ctx:cc}
> {$ctx:bcc}
> 
> 
>
> Thanks
>
> On Sat, Jun 4, 2016 at 7:40 AM, Shakila Sivagnanarajah <
> shak...@wso2.com> wrote:
>
>> Hi Maheeka,
>>
>> I Just have tested it, it is working fine. It seems the access token
>> is not set in your call.
>>
>> Please try with this configuration.
>>
>> 
>> {$ctx:refreshToken}
>> {$ctx:clientId}
>> {$ctx:clientSecret}
>> {$ctx:grantType}
>> 
>>

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-05 Thread Maheeka Jayasuriya

Hi Hariprasath,

I am using the connector's input schema and the default values property
file to set the parameters for invoking the connector's createAMail
operation. However, the parameter values are not picked up by the connector
operation. Maybe the expressions are not correct. Can you please take a
look? If I set as {$func:Recipient} from template parameters it works. It
doesn't work for {json-eval($.subject)} type parameters.

Please find below a sample proxy service. You can use this proxy to verify.


http://ws.apache.org/ns/synapse;
   name="SampleProxy"
   transports="https,http"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
{"subject":"XXX","messageBody":"This is message
body"}

 
 
 
 
 
{$ctx:TO}
{json-eval($.subject)}
{json-eval($.from)}
{json-eval($.messageBody)}
{json-eval($.cc)}
{json-eval($.bcc)}
{json-eval($.id)}
{json-eval($.threadId)}
 
 
  
   
   


Thanks,
Maheeka


Maheeka Jayasuriya
Senior Software Engineer
Mobile : +9450661

On Sat, Jun 4, 2016 at 11:55 AM, Maheeka Jayasuriya 
wrote:

> Thanks Hariprasad for taking time on helping to resolve the issue. The
> mentioned approach is now working.
>
> Maheeka Jayasuriya
> Senior Software Engineer
> Mobile : +9450661
>
> On Sat, Jun 4, 2016 at 10:49 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Maheeka,
>>
>> If you are trying to get the refresh token and accessToken from oAuth
>> playground you should refresh the refreshToken in oAuth playground only
>> because in oAuth playground it sets the redirect_uri as https%3A%2F%
>> 2Fdevelopers.google.com%2Foauthplayground is not your app redirect_uri.
>> So after one hour if you trying any method it gave the error.
>> Better trying below url[1] to get the code and using [2] to get the
>> refresh token.
>>
>> [1] - https://accounts.google.com/o/oauth2/auth?redirect_uri=*> redirect-uri>*_type=code_id=**=
>> https://mail.google.com/+https://www.googleapis.com/auth/gmail.compose+https://www.googleapis.com/auth/gmail.insert+https://www.googleapis.com/auth/gmail.labels+https://www.googleapis.com/auth/gmail.modify+https://www.googleapis.com/auth/gmail.readonly+https://www.googleapis.com/auth/gmail.send_prompt=force_type=offline
>>
>> [2] - I have attached below
>>
>>
>> From [2]  you can get the refresh_token and you can use it in the init
>> call. Then you won't get the error.
>>
>> On Sat, Jun 4, 2016 at 8:09 AM, Malaka Silva  wrote:
>>
>>> Yes this should be the way. Only use init method before each call.
>>>
>>> On Sat, Jun 4, 2016 at 8:00 AM, Shakila Sivagnanarajah >> > wrote:
>>>
 Hi Maheeka,

 Since the refreshing access token is automated in the connector, you
 can use following init configuration.

  
 {$ctx:refreshToken}
 {$ctx:clientId}
 {$ctx:clientSecret}

 {$ctx:accessTokenRegistryPath}
 {$ctx:accessToken}
 {$ctx:apiUrl}
 {$ctx:userId}
 
 
 {$ctx:to}
 {$ctx:subject}
 {$ctx:from}
 {$ctx:messageBody}
 {$ctx:cc}
 {$ctx:bcc}
 
 

 Thanks

 On Sat, Jun 4, 2016 at 7:40 AM, Shakila Sivagnanarajah <
 shak...@wso2.com> wrote:

> Hi Maheeka,
>
> I Just have tested it, it is working fine. It seems the access token
> is not set in your call.
>
> Please try with this configuration.
>
> 
> {$ctx:refreshToken}
> {$ctx:clientId}
> {$ctx:clientSecret}
> {$ctx:grantType}
> 
> 
> {$ctx:apiUrl}
> {$ctx:userId}
> 
> 
> {$ctx:to}
> {$ctx:subject}
> {$ctx:from}
> {$ctx:messageBody}
> {$ctx:cc}
> {$ctx:bcc}
> 
> 
>
>
> Thanks
>
> On Sat, Jun 4, 2016 at 7:33 AM, Malaka Silva  wrote:
>
>> Looping Hariprasath.
>>
>> On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah <
>> shak...@wso2.com> wrote:
>>
>>> Hi Maheeka,
>>>
>>> I will check and update you
>>>
>>> Thanks
>>>
>>> On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya >> > wrote:
>>>
 Hi Shakila/Malaka,

 I am getting the following errors when using the latest gmail
 connector from connector store. I am getting the clientId and 
 clientSecret
 from the app and the refresh token and access token from playground 
 app.
 Used apiUrl as https://www.googleapis.com/gmail.

 Am I doing any

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-04 Thread Maheeka Jayasuriya

Thanks Hariprasad for taking time on helping to resolve the issue. The
mentioned approach is now working.

Maheeka Jayasuriya
Senior Software Engineer
Mobile : +9450661

On Sat, Jun 4, 2016 at 10:49 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Maheeka,
>
> If you are trying to get the refresh token and accessToken from oAuth
> playground you should refresh the refreshToken in oAuth playground only
> because in oAuth playground it sets the redirect_uri as https%3A%2F%
> 2Fdevelopers.google.com%2Foauthplayground is not your app redirect_uri.
> So after one hour if you trying any method it gave the error.
> Better trying below url[1] to get the code and using [2] to get the
> refresh token.
>
> [1] - https://accounts.google.com/o/oauth2/auth?redirect_uri=* redirect-uri>*_type=code_id=**=
> https://mail.google.com/+https://www.googleapis.com/auth/gmail.compose+https://www.googleapis.com/auth/gmail.insert+https://www.googleapis.com/auth/gmail.labels+https://www.googleapis.com/auth/gmail.modify+https://www.googleapis.com/auth/gmail.readonly+https://www.googleapis.com/auth/gmail.send_prompt=force_type=offline
>
> [2] - I have attached below
>
>
> From [2]  you can get the refresh_token and you can use it in the init
> call. Then you won't get the error.
>
> On Sat, Jun 4, 2016 at 8:09 AM, Malaka Silva  wrote:
>
>> Yes this should be the way. Only use init method before each call.
>>
>> On Sat, Jun 4, 2016 at 8:00 AM, Shakila Sivagnanarajah 
>> wrote:
>>
>>> Hi Maheeka,
>>>
>>> Since the refreshing access token is automated in the connector, you can
>>> use following init configuration.
>>>
>>>  
>>> {$ctx:refreshToken}
>>> {$ctx:clientId}
>>> {$ctx:clientSecret}
>>>
>>> {$ctx:accessTokenRegistryPath}
>>> {$ctx:accessToken}
>>> {$ctx:apiUrl}
>>> {$ctx:userId}
>>> 
>>> 
>>> {$ctx:to}
>>> {$ctx:subject}
>>> {$ctx:from}
>>> {$ctx:messageBody}
>>> {$ctx:cc}
>>> {$ctx:bcc}
>>> 
>>> 
>>>
>>> Thanks
>>>
>>> On Sat, Jun 4, 2016 at 7:40 AM, Shakila Sivagnanarajah >> > wrote:
>>>
 Hi Maheeka,

 I Just have tested it, it is working fine. It seems the access token is
 not set in your call.

 Please try with this configuration.

 
 {$ctx:refreshToken}
 {$ctx:clientId}
 {$ctx:clientSecret}
 {$ctx:grantType}
 
 
 {$ctx:apiUrl}
 {$ctx:userId}
 
 
 {$ctx:to}
 {$ctx:subject}
 {$ctx:from}
 {$ctx:messageBody}
 {$ctx:cc}
 {$ctx:bcc}
 
 


 Thanks

 On Sat, Jun 4, 2016 at 7:33 AM, Malaka Silva  wrote:

> Looping Hariprasath.
>
> On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah <
> shak...@wso2.com> wrote:
>
>> Hi Maheeka,
>>
>> I will check and update you
>>
>> Thanks
>>
>> On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Hi Shakila/Malaka,
>>>
>>> I am getting the following errors when using the latest gmail
>>> connector from connector store. I am getting the clientId and 
>>> clientSecret
>>> from the app and the refresh token and access token from playground app.
>>> Used apiUrl as https://www.googleapis.com/gmail.
>>>
>>> Am I doing any configuration wrong?
>>>
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "POST //v1/users/johndoeintcl...@gmail.com/messages/send
>>> HTTP/1.1[\r][\n]"
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "X-Frame-Options: SAMEORIGIN[\r][\n]"
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Authorization: Bearer [\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Alt-Svc: quic=":443"; ma=2592000;
>>> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Vary: X-Origin[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "X-XSS-Protection: 1; mode=block[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Alternate-Protocol: 443:quic[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Content-Type: application/json; charset=UTF-8[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
>>> << "Accept-Ranges: none[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Malaka Silva

Yes this should be the way. Only use init method before each call.

On Sat, Jun 4, 2016 at 8:00 AM, Shakila Sivagnanarajah 
wrote:

> Hi Maheeka,
>
> Since the refreshing access token is automated in the connector, you can
> use following init configuration.
>
>  
> {$ctx:refreshToken}
> {$ctx:clientId}
> {$ctx:clientSecret}
>
> {$ctx:accessTokenRegistryPath}
> {$ctx:accessToken}
> {$ctx:apiUrl}
> {$ctx:userId}
> 
> 
> {$ctx:to}
> {$ctx:subject}
> {$ctx:from}
> {$ctx:messageBody}
> {$ctx:cc}
> {$ctx:bcc}
> 
> 
>
> Thanks
>
> On Sat, Jun 4, 2016 at 7:40 AM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi Maheeka,
>>
>> I Just have tested it, it is working fine. It seems the access token is
>> not set in your call.
>>
>> Please try with this configuration.
>>
>> 
>> {$ctx:refreshToken}
>> {$ctx:clientId}
>> {$ctx:clientSecret}
>> {$ctx:grantType}
>> 
>> 
>> {$ctx:apiUrl}
>> {$ctx:userId}
>> 
>> 
>> {$ctx:to}
>> {$ctx:subject}
>> {$ctx:from}
>> {$ctx:messageBody}
>> {$ctx:cc}
>> {$ctx:bcc}
>> 
>> 
>>
>>
>> Thanks
>>
>> On Sat, Jun 4, 2016 at 7:33 AM, Malaka Silva  wrote:
>>
>>> Looping Hariprasath.
>>>
>>> On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah >> > wrote:
>>>
 Hi Maheeka,

 I will check and update you

 Thanks

 On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya 
 wrote:

> Hi Shakila/Malaka,
>
> I am getting the following errors when using the latest gmail
> connector from connector store. I am getting the clientId and clientSecret
> from the app and the refresh token and access token from playground app.
> Used apiUrl as https://www.googleapis.com/gmail.
>
> Am I doing any configuration wrong?
>
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "POST //v1/users/johndoeintcl...@gmail.com/messages/send
> HTTP/1.1[\r][\n]"
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "X-Frame-Options: SAMEORIGIN[\r][\n]"
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Authorization: Bearer [\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Alt-Svc: quic=":443"; ma=2592000;
> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Vary: X-Origin[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "X-XSS-Protection: 1; mode=block[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Alternate-Protocol: 443:quic[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Content-Type: application/json; charset=UTF-8[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Accept-Ranges: none[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "X-Content-Type-Options: nosniff[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Content-Length: 38[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Host: mail.google.com[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "Connection: Keep-Alive[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "[\r][\n]"
> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> << "{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "HTTP/1.1 301 Moved Permanently[\r][\n]"
> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "Location:
> https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
> "
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "Content-Type: text/html; charset=UTF-8[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "X-Content-Type-Options: nosniff[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3
> >> "Expires: Sun, 03 Jul 2016 18:34:44

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Shakila Sivagnanarajah

Hi Maheeka,

Since the refreshing access token is automated in the connector, you can
use following init configuration.

 
{$ctx:refreshToken}
{$ctx:clientId}
{$ctx:clientSecret}

{$ctx:accessTokenRegistryPath}
{$ctx:accessToken}
{$ctx:apiUrl}
{$ctx:userId}


{$ctx:to}
{$ctx:subject}
{$ctx:from}
{$ctx:messageBody}
{$ctx:cc}
{$ctx:bcc}



Thanks

On Sat, Jun 4, 2016 at 7:40 AM, Shakila Sivagnanarajah 
wrote:

> Hi Maheeka,
>
> I Just have tested it, it is working fine. It seems the access token is
> not set in your call.
>
> Please try with this configuration.
>
> 
> {$ctx:refreshToken}
> {$ctx:clientId}
> {$ctx:clientSecret}
> {$ctx:grantType}
> 
> 
> {$ctx:apiUrl}
> {$ctx:userId}
> 
> 
> {$ctx:to}
> {$ctx:subject}
> {$ctx:from}
> {$ctx:messageBody}
> {$ctx:cc}
> {$ctx:bcc}
> 
> 
>
>
> Thanks
>
> On Sat, Jun 4, 2016 at 7:33 AM, Malaka Silva  wrote:
>
>> Looping Hariprasath.
>>
>> On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah 
>> wrote:
>>
>>> Hi Maheeka,
>>>
>>> I will check and update you
>>>
>>> Thanks
>>>
>>> On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya 
>>> wrote:
>>>
 Hi Shakila/Malaka,

 I am getting the following errors when using the latest gmail connector
 from connector store. I am getting the clientId and clientSecret from the
 app and the refresh token and access token from playground app. Used apiUrl
 as https://www.googleapis.com/gmail.

 Am I doing any configuration wrong?

 [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "POST //v1/users/johndoeintcl...@gmail.com/messages/send
 HTTP/1.1[\r][\n]"
 [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "X-Frame-Options: SAMEORIGIN[\r][\n]"
 [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Authorization: Bearer [\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Alt-Svc: quic=":443"; ma=2592000;
 v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Vary: X-Origin[\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "X-XSS-Protection: 1; mode=block[\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Alternate-Protocol: 443:quic[\r][\n]"
 [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Content-Type: application/json; charset=UTF-8[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Accept-Ranges: none[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "X-Content-Type-Options: nosniff[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Content-Length: 38[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Host: mail.google.com[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "Connection: Keep-Alive[\r][\n]"
 [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
 [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "[\r][\n]"
 [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
 "{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
 [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "HTTP/1.1 301 Moved Permanently[\r][\n]"
 [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Location:
 https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
 "
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Content-Type: text/html; charset=UTF-8[\r][\n]"
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "X-Content-Type-Options: nosniff[\r][\n]"
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Expires: Sun, 03 Jul 2016 18:34:44 GMT[\r][\n]"
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Cache-Control: public, max-age=2592000[\r][\n]"
 [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
 "Server: sffe[\r][\n]"
 [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Shakila Sivagnanarajah

Hi Maheeka,

I Just have tested it, it is working fine. It seems the access token is not
set in your call.

Please try with this configuration.


{$ctx:refreshToken}
{$ctx:clientId}
{$ctx:clientSecret}
{$ctx:grantType}


{$ctx:apiUrl}
{$ctx:userId}


{$ctx:to}
{$ctx:subject}
{$ctx:from}
{$ctx:messageBody}
{$ctx:cc}
{$ctx:bcc}




Thanks

On Sat, Jun 4, 2016 at 7:33 AM, Malaka Silva  wrote:

> Looping Hariprasath.
>
> On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi Maheeka,
>>
>> I will check and update you
>>
>> Thanks
>>
>> On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Hi Shakila/Malaka,
>>>
>>> I am getting the following errors when using the latest gmail connector
>>> from connector store. I am getting the clientId and clientSecret from the
>>> app and the refresh token and access token from playground app. Used apiUrl
>>> as https://www.googleapis.com/gmail.
>>>
>>> Am I doing any configuration wrong?
>>>
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "POST //v1/users/johndoeintcl...@gmail.com/messages/send
>>> HTTP/1.1[\r][\n]"
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "X-Frame-Options: SAMEORIGIN[\r][\n]"
>>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Authorization: Bearer [\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Alt-Svc: quic=":443"; ma=2592000;
>>> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Vary: X-Origin[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Alternate-Protocol: 443:quic[\r][\n]"
>>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Content-Type: application/json; charset=UTF-8[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Accept-Ranges: none[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "X-Content-Type-Options: nosniff[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Content-Length: 38[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Host: mail.google.com[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "Connection: Keep-Alive[\r][\n]"
>>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
>>> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "[\r][\n]"
>>> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>>> "{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
>>> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "HTTP/1.1 301 Moved Permanently[\r][\n]"
>>> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Location:
>>> https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
>>> "
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Content-Type: text/html; charset=UTF-8[\r][\n]"
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "X-Content-Type-Options: nosniff[\r][\n]"
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Expires: Sun, 03 Jul 2016 18:34:44 GMT[\r][\n]"
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Cache-Control: public, max-age=2592000[\r][\n]"
>>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Server: sffe[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Content-Length: 268[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Alternate-Protocol: 443:quic[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "Alt-Svc: quic=":443"; ma=2592000;
>>> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> "[\r][\n]"
>>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>>> ">> content="text/html;charset=utf-8">[\n]"
>>>

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Malaka Silva

Looping Hariprasath.

On Sat, Jun 4, 2016 at 7:25 AM, Shakila Sivagnanarajah 
wrote:

> Hi Maheeka,
>
> I will check and update you
>
> Thanks
>
> On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya 
> wrote:
>
>> Hi Shakila/Malaka,
>>
>> I am getting the following errors when using the latest gmail connector
>> from connector store. I am getting the clientId and clientSecret from the
>> app and the refresh token and access token from playground app. Used apiUrl
>> as https://www.googleapis.com/gmail.
>>
>> Am I doing any configuration wrong?
>>
>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "POST //v1/users/johndoeintcl...@gmail.com/messages/send
>> HTTP/1.1[\r][\n]"
>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "X-Frame-Options: SAMEORIGIN[\r][\n]"
>> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Authorization: Bearer [\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Alt-Svc: quic=":443"; ma=2592000;
>> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Vary: X-Origin[\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Alternate-Protocol: 443:quic[\r][\n]"
>> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Content-Type: application/json; charset=UTF-8[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Accept-Ranges: none[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "X-Content-Type-Options: nosniff[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Content-Length: 38[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Host: mail.google.com[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "Connection: Keep-Alive[\r][\n]"
>> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
>> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "[\r][\n]"
>> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
>> "{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
>> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "HTTP/1.1 301 Moved Permanently[\r][\n]"
>> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Location:
>> https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
>> "
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Content-Type: text/html; charset=UTF-8[\r][\n]"
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "X-Content-Type-Options: nosniff[\r][\n]"
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Expires: Sun, 03 Jul 2016 18:34:44 GMT[\r][\n]"
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Cache-Control: public, max-age=2592000[\r][\n]"
>> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Server: sffe[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Content-Length: 268[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Alternate-Protocol: 443:quic[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "Alt-Svc: quic=":443"; ma=2592000;
>> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "[\r][\n]"
>> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "> content="text/html;charset=utf-8">[\n]"
>> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "301 Moved[\n]"
>> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "301 Moved[\n]"
>> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "The document has moved[\n]"
>> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send
>> ">here.[\r][\n]"
>> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
>> "[\r][\n]"
>>
>>
>>
>>

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Shakila Sivagnanarajah

Hi Maheeka,

I will check and update you

Thanks

On Sat, Jun 4, 2016 at 1:05 AM, Maheeka Jayasuriya  wrote:

> Hi Shakila/Malaka,
>
> I am getting the following errors when using the latest gmail connector
> from connector store. I am getting the clientId and clientSecret from the
> app and the refresh token and access token from playground app. Used apiUrl
> as https://www.googleapis.com/gmail.
>
> Am I doing any configuration wrong?
>
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "POST //v1/users/johndoeintcl...@gmail.com/messages/send HTTP/1.1[\r][\n]"
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "X-Frame-Options: SAMEORIGIN[\r][\n]"
> [2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Authorization: Bearer [\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Alt-Svc: quic=":443"; ma=2592000;
> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Vary: X-Origin[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "X-XSS-Protection: 1; mode=block[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Alternate-Protocol: 443:quic[\r][\n]"
> [2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Content-Type: application/json; charset=UTF-8[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Accept-Ranges: none[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "X-Content-Type-Options: nosniff[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Content-Length: 38[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Host: mail.google.com[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "Connection: Keep-Alive[\r][\n]"
> [2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "[\r][\n]"
> [2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
> "{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "HTTP/1.1 301 Moved Permanently[\r][\n]"
> [2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Location:
> https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
> "
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Content-Type: text/html; charset=UTF-8[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "X-Content-Type-Options: nosniff[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Expires: Sun, 03 Jul 2016 18:34:44 GMT[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Cache-Control: public, max-age=2592000[\r][\n]"
> [2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Server: sffe[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Content-Length: 268[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "X-XSS-Protection: 1; mode=block[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Alternate-Protocol: 443:quic[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "Alt-Svc: quic=":443"; ma=2592000;
> v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "[\r][\n]"
> [2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> " content="text/html;charset=utf-8">[\n]"
> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "301 Moved[\n]"
> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "301 Moved[\n]"
> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "The document has moved[\n]"
> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send
> ">here.[\r][\n]"
> [2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "[\r][\n]"
>
>
>
> -
>
> [2016-06-04 00:53:56,567] ERROR - ClientUtils The system cannot infer the
> transport information from the //users//messages/send URL.
> [2016-06-04

[Dev] [Gmail Connector] Error connecting to gmail connector

2016-06-03 Thread Maheeka Jayasuriya

Hi Shakila/Malaka,

I am getting the following errors when using the latest gmail connector
from connector store. I am getting the clientId and clientSecret from the
app and the refresh token and access token from playground app. Used apiUrl
as https://www.googleapis.com/gmail.

Am I doing any configuration wrong?

[2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"POST //v1/users/johndoeintcl...@gmail.com/messages/send HTTP/1.1[\r][\n]"
[2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"X-Frame-Options: SAMEORIGIN[\r][\n]"
[2016-06-04 00:04:44,784] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Authorization: Bearer [\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Alt-Svc: quic=":443"; ma=2592000;
v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Vary: X-Origin[\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"X-XSS-Protection: 1; mode=block[\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Expires: Fri, 03 Jun 2016 18:34:43 GMT[\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Alternate-Protocol: 443:quic[\r][\n]"
[2016-06-04 00:04:44,785] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Content-Type: application/json; charset=UTF-8[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Accept-Ranges: none[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"X-Content-Type-Options: nosniff[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Content-Length: 38[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Host: mail.google.com[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"Connection: Keep-Alive[\r][\n]"
[2016-06-04 00:04:44,786] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"[\r][\n]"
[2016-06-04 00:04:44,787] DEBUG - wire HTTPS-Sender I/O dispatcher-3 <<
"{"raw":"dG86bWFoZWVrYUB3c28yLmNvbQo="}"
[2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"HTTP/1.1 301 Moved Permanently[\r][\n]"
[2016-06-04 00:04:45,052] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Location:
https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send[\r][\n]
"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Content-Type: text/html; charset=UTF-8[\r][\n]"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"X-Content-Type-Options: nosniff[\r][\n]"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Date: Fri, 03 Jun 2016 18:34:44 GMT[\r][\n]"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Expires: Sun, 03 Jul 2016 18:34:44 GMT[\r][\n]"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Cache-Control: public, max-age=2592000[\r][\n]"
[2016-06-04 00:04:45,053] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Server: sffe[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Content-Length: 268[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"X-XSS-Protection: 1; mode=block[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Alternate-Protocol: 443:quic[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"Alt-Svc: quic=":443"; ma=2592000;
v="34,33,32,31,30,29,28,27,26,25"[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"[\r][\n]"
[2016-06-04 00:04:45,054] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"[\n]"
[2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"301 Moved[\n]"
[2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"301 Moved[\n]"
[2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"The document has moved[\n]"
[2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "https://www.google.com/v1/users/johndoeintcl...@gmail.com/messages/send
">here.[\r][\n]"
[2016-06-04 00:04:45,055] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
"[\r][\n]"


-

[2016-06-04 00:53:56,567] ERROR - ClientUtils The system cannot infer the
transport information from the //users//messages/send URL.
[2016-06-04 00:53:56,573] ERROR - Axis2Sender Unexpected error during
sending message out
org.apache.axis2.AxisFault: The system cannot infer the transport
information from the //users//messages/send URL.
at
org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
at

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

Re: [Dev] [Gmail Connector] Error connecting to gmail connector

[Dev] [Gmail Connector] Error connecting to gmail connector

10 matches

Site Navigation

Mail list logo

Footer information