from:"Thulasika Vijayanathan"

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

2017-01-19 Thread Thulasika Vijayanathan

Please ignore the above mentioned tested versions. I tested with IS 5.1.0 ,
5.2.0 and 5.3.0.

On Fri, Jan 20, 2017 at 9:08 AM, Thulasika Vijayanathan <thulas...@wso2.com>
wrote:

> Hi Malaka,
>
> I already fixed and checked with previous versions(5.0.1, 5.0.2, 5.0.3).
> It works fine with all versions.I released and published in the store as
> well.
>
> Thanks,
> Thulasika.
>
> On Fri, Jan 20, 2017 at 5:35 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Shall we fix. We need to,
>>
>>
>>1. Verify the fix with previous versions.
>>2. Update the store to mention that it supports IS 510, 520 and 530
>>
>> @Thulasika - Please check this after doc-sign.
>>
>> On Thu, Jan 19, 2017 at 9:17 AM, Thulasika Vijayanathan <
>> thulas...@wso2.com> wrote:
>>
>>> Hi Nuwandi,
>>>
>>> The solution you have provided is working, Thank you for your help.
>>>
>>> Thanks,
>>> Thulasika.
>>>
>>> On Wed, Jan 18, 2017 at 11:14 PM, Nuwandi Wickramasinghe <
>>> nuwan...@wso2.com> wrote:
>>>
>>>> Hi Thulasika,
>>>>
>>>> I could successfully load the iframe by getting rid of
>>>> *HttpServletResponse*.*encodeRedirectURL() *method at [1]. Since the 
>>>> *DuoUrl
>>>> *contain some data with special characters, you need to URL encode
>>>> them in order to get this working. I have attached the patch file with the
>>>> code changes I did to get it working.
>>>>
>>>> However, I could not figure out why 
>>>> *HttpServletResponse*.*encodeRedirectURL()
>>>> *causes issues only in 5.3.0. There's no javax.servlet api version
>>>> change between 5.2.0 and 5.3.0 AFAIS.
>>>>
>>>> [1] https://github.com/wso2-extensions/identity-outbound-aut
>>>> h-duo/blob/org.wso2.carbon.extension.identity.authenticator.
>>>> duo-1.0.1/component/authenticator/src/main/java/org/wso2/car
>>>> bon/identity/authenticator/duo/DuoAuthenticator.java#L134
>>>>
>>>> On Wed, Jan 18, 2017 at 10:09 PM, Thulasika Vijayanathan <
>>>> thulas...@wso2.com> wrote:
>>>>
>>>>> Hi Nuwandi,
>>>>>
>>>>> Yes, I use the same values.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Wed, Jan 18, 2017 at 9:59 PM, Nuwandi Wickramasinghe <
>>>>> nuwan...@wso2.com> wrote:
>>>>>
>>>>>> Hi Thulasika,
>>>>>>
>>>>>> Are you using same duo API configuration values (i.e Secret Key,
>>>>>> Integration Key, Admin Secret Key, Admin Integration key ) in both
>>>>>> 5.2.0 and 5.3.0?
>>>>>>
>>>>>> thanks
>>>>>> Nuwandi
>>>>>>
>>>>>> On Tue, Jan 17, 2017 at 2:24 PM, Thulasika Vijayanathan <
>>>>>> thulas...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am verifying the authenticators with IS 5.3.0. When I test Duo
>>>>>>> security authenticator with IS 5.3.0, I got the blank page, but it works
>>>>>>> with IS 5.2.0. It seems redirect URL and signature are correct, because 
>>>>>>> If
>>>>>>> we give the wrong signature, the page will display as Access denied, Duo
>>>>>>> Provisioning connector works fine with both IS 5.2.0 and 5.3.0.
>>>>>>>
>>>>>>> Redirect URL in IS 5.3.0
>>>>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDUwMg==|f4345a7f5
>>>>>>> 17828d259b235703310c09b594b736c:APP|YWRtaW58REkySjlaVk40NEM4
>>>>>>> UlZRQzdTUkJ8MTQ4NDY0MzgwMg==|f65d989f837105e4a4d77167911f5ab
>>>>>>> f09b7095c=bd19a4d8-f08e-4322-b0a8-cbbb31a144a
>>>>>>> 7=api-.duosecurity.com
>>>>>>>
>>>>>>> [image: Inline image 3]
>>>>>>>
>>>>>>> Redirect URL in IS 5.2.0
>>>>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDcxMQ==|969c487f9

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

2017-01-19 Thread Thulasika Vijayanathan

Hi Malaka,

I already fixed and checked with previous versions(5.0.1, 5.0.2, 5.0.3). It
works fine with all versions.I released and published in the store as well.

Thanks,
Thulasika.

On Fri, Jan 20, 2017 at 5:35 AM, Malaka Silva <mal...@wso2.com> wrote:

> Shall we fix. We need to,
>
>
>1. Verify the fix with previous versions.
>2. Update the store to mention that it supports IS 510, 520 and 530
>
> @Thulasika - Please check this after doc-sign.
>
> On Thu, Jan 19, 2017 at 9:17 AM, Thulasika Vijayanathan <
> thulas...@wso2.com> wrote:
>
>> Hi Nuwandi,
>>
>> The solution you have provided is working, Thank you for your help.
>>
>> Thanks,
>> Thulasika.
>>
>> On Wed, Jan 18, 2017 at 11:14 PM, Nuwandi Wickramasinghe <
>> nuwan...@wso2.com> wrote:
>>
>>> Hi Thulasika,
>>>
>>> I could successfully load the iframe by getting rid of
>>> *HttpServletResponse*.*encodeRedirectURL() *method at [1]. Since the *DuoUrl
>>> *contain some data with special characters, you need to URL encode them
>>> in order to get this working. I have attached the patch file with the code
>>> changes I did to get it working.
>>>
>>> However, I could not figure out why 
>>> *HttpServletResponse*.*encodeRedirectURL()
>>> *causes issues only in 5.3.0. There's no javax.servlet api version
>>> change between 5.2.0 and 5.3.0 AFAIS.
>>>
>>> [1] https://github.com/wso2-extensions/identity-outbound-aut
>>> h-duo/blob/org.wso2.carbon.extension.identity.authenticator.
>>> duo-1.0.1/component/authenticator/src/main/java/org/wso2/
>>> carbon/identity/authenticator/duo/DuoAuthenticator.java#L134
>>>
>>> On Wed, Jan 18, 2017 at 10:09 PM, Thulasika Vijayanathan <
>>> thulas...@wso2.com> wrote:
>>>
>>>> Hi Nuwandi,
>>>>
>>>> Yes, I use the same values.
>>>>
>>>> Thanks.
>>>>
>>>> On Wed, Jan 18, 2017 at 9:59 PM, Nuwandi Wickramasinghe <
>>>> nuwan...@wso2.com> wrote:
>>>>
>>>>> Hi Thulasika,
>>>>>
>>>>> Are you using same duo API configuration values (i.e Secret Key,
>>>>> Integration Key, Admin Secret Key, Admin Integration key ) in both
>>>>> 5.2.0 and 5.3.0?
>>>>>
>>>>> thanks
>>>>> Nuwandi
>>>>>
>>>>> On Tue, Jan 17, 2017 at 2:24 PM, Thulasika Vijayanathan <
>>>>> thulas...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am verifying the authenticators with IS 5.3.0. When I test Duo
>>>>>> security authenticator with IS 5.3.0, I got the blank page, but it works
>>>>>> with IS 5.2.0. It seems redirect URL and signature are correct, because 
>>>>>> If
>>>>>> we give the wrong signature, the page will display as Access denied, Duo
>>>>>> Provisioning connector works fine with both IS 5.2.0 and 5.3.0.
>>>>>>
>>>>>> Redirect URL in IS 5.3.0
>>>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDUwMg==|f4345a7f5
>>>>>> 17828d259b235703310c09b594b736c:APP|YWRtaW58REkySjlaVk40NEM4
>>>>>> UlZRQzdTUkJ8MTQ4NDY0MzgwMg==|f65d989f837105e4a4d77167911f5ab
>>>>>> f09b7095c=bd19a4d8-f08e-4322-b0a8-cbbb31a144a
>>>>>> 7=api-.duosecurity.com
>>>>>>
>>>>>> [image: Inline image 3]
>>>>>>
>>>>>> Redirect URL in IS 5.2.0
>>>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDcxMQ==|969c487f9
>>>>>> 80bfb10e7a45a4b43d06543a78b9500:APP|YWRtaW58REkySjlaVk40NEM4
>>>>>> UlZRQzdTUkJ8MTQ4NDY0NDAxMQ==|bb3be42f90aa3cfc38a5f42600fa4a9
>>>>>> ed8776421=04c82f8e-ce66-454b-9cbf-a671404109d
>>>>>> 7=api-.duosecurity.com
>>>>>>
>>>>>> [image: Inline image 2]
>>>>>> Can you please suggest what could be the reason?
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Thulasika.
>>>>>>
>>>>>> --

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

2017-01-18 Thread Thulasika Vijayanathan

Hi Nuwandi,

The solution you have provided is working, Thank you for your help.

Thanks,
Thulasika.

On Wed, Jan 18, 2017 at 11:14 PM, Nuwandi Wickramasinghe <nuwan...@wso2.com>
wrote:

> Hi Thulasika,
>
> I could successfully load the iframe by getting rid of
> *HttpServletResponse*.*encodeRedirectURL() *method at [1]. Since the *DuoUrl
> *contain some data with special characters, you need to URL encode them
> in order to get this working. I have attached the patch file with the code
> changes I did to get it working.
>
> However, I could not figure out why *HttpServletResponse*.*encodeRedirectURL()
> *causes issues only in 5.3.0. There's no javax.servlet api version change
> between 5.2.0 and 5.3.0 AFAIS.
>
> [1] https://github.com/wso2-extensions/identity-outbound-
> auth-duo/blob/org.wso2.carbon.extension.identity.authenticator.duo-1.0.1/
> component/authenticator/src/main/java/org/wso2/carbon/
> identity/authenticator/duo/DuoAuthenticator.java#L134
>
> On Wed, Jan 18, 2017 at 10:09 PM, Thulasika Vijayanathan <
> thulas...@wso2.com> wrote:
>
>> Hi Nuwandi,
>>
>> Yes, I use the same values.
>>
>> Thanks.
>>
>> On Wed, Jan 18, 2017 at 9:59 PM, Nuwandi Wickramasinghe <
>> nuwan...@wso2.com> wrote:
>>
>>> Hi Thulasika,
>>>
>>> Are you using same duo API configuration values (i.e Secret Key,
>>> Integration Key, Admin Secret Key, Admin Integration key ) in both
>>> 5.2.0 and 5.3.0?
>>>
>>> thanks
>>> Nuwandi
>>>
>>> On Tue, Jan 17, 2017 at 2:24 PM, Thulasika Vijayanathan <
>>> thulas...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am verifying the authenticators with IS 5.3.0. When I test Duo
>>>> security authenticator with IS 5.3.0, I got the blank page, but it works
>>>> with IS 5.2.0. It seems redirect URL and signature are correct, because If
>>>> we give the wrong signature, the page will display as Access denied, Duo
>>>> Provisioning connector works fine with both IS 5.2.0 and 5.3.0.
>>>>
>>>> Redirect URL in IS 5.3.0
>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDUwMg==|f4345a7f5
>>>> 17828d259b235703310c09b594b736c:APP|YWRtaW58REkySjlaVk40NEM4
>>>> UlZRQzdTUkJ8MTQ4NDY0MzgwMg==|f65d989f837105e4a4d77167911f5a
>>>> bf09b7095c=bd19a4d8-f08e-4322-b0a8-cbbb31a144
>>>> a7=api-.duosecurity.com
>>>>
>>>> [image: Inline image 3]
>>>>
>>>> Redirect URL in IS 5.2.0
>>>> https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp
>>>> ?authenticator=DuoAuthenticator:LOCAL=duo=TX|YW
>>>> RtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDcxMQ==|969c487f9
>>>> 80bfb10e7a45a4b43d06543a78b9500:APP|YWRtaW58REkySjlaVk40NEM4
>>>> UlZRQzdTUkJ8MTQ4NDY0NDAxMQ==|bb3be42f90aa3cfc38a5f42600fa4a
>>>> 9ed8776421=04c82f8e-ce66-454b-9cbf-a671404109
>>>> d7=api-.duosecurity.com
>>>>
>>>> [image: Inline image 2]
>>>> Can you please suggest what could be the reason?
>>>>
>>>>
>>>> Thanks,
>>>> Thulasika.
>>>>
>>>> --
>>>> Thulasika
>>>> Associate Software Engineer
>>>> Mobile:0778014295
>>>> email: thulas...@wso2.com <sanj...@wso2.com>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Nuwandi Wickramasinghe
>>>
>>> Software Engineer
>>>
>>> WSO2 Inc.
>>>
>>> Web : http://wso2.com
>>>
>>> Mobile : 0719214873
>>>
>>
>>
>>
>> --
>> Thulasika
>> Associate Software Engineer
>> Mobile:0778014295
>> email: thulas...@wso2.com <sanj...@wso2.com>
>>
>
>
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>



-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com <sanj...@wso2.com>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

2017-01-18 Thread Thulasika Vijayanathan

Hi Nuwandi,

Yes, I use the same values.

Thanks.

On Wed, Jan 18, 2017 at 9:59 PM, Nuwandi Wickramasinghe <nuwan...@wso2.com>
wrote:

> Hi Thulasika,
>
> Are you using same duo API configuration values (i.e Secret Key,
> Integration Key, Admin Secret Key, Admin Integration key ) in both 5.2.0
> and 5.3.0?
>
> thanks
> Nuwandi
>
> On Tue, Jan 17, 2017 at 2:24 PM, Thulasika Vijayanathan <
> thulas...@wso2.com> wrote:
>
>> Hi,
>>
>> I am verifying the authenticators with IS 5.3.0. When I test Duo security
>> authenticator with IS 5.3.0, I got the blank page, but it works with IS
>> 5.2.0. It seems redirect URL and signature are correct, because If we give
>> the wrong signature, the page will display as Access denied, Duo
>> Provisioning connector works fine with both IS 5.2.0 and 5.3.0.
>>
>> Redirect URL in IS 5.3.0
>> https://localhost:9443/duoauthenticationendpoint/duoAuth.
>> jsp?authenticator=DuoAuthenticator:LOCAL=duo=
>> TX|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDUwMg==|f434
>> 5a7f517828d259b235703310c09b594b736c:APP|YWRtaW58REkySjlaVk4
>> 0NEM4UlZRQzdTUkJ8MTQ4NDY0MzgwMg==|f65d989f837105e4a4d7716791
>> 1f5abf09b7095c=bd19a4d8-f08e-4322-b0a8-cbbb31
>> a144a7=api-.duosecurity.com
>>
>> [image: Inline image 3]
>>
>> Redirect URL in IS 5.2.0
>> https://localhost:9443/duoauthenticationendpoint/duoAuth.
>> jsp?authenticator=DuoAuthenticator:LOCAL=duo=
>> TX|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDcxMQ==|969c
>> 487f980bfb10e7a45a4b43d06543a78b9500:APP|YWRtaW58REkySjlaVk4
>> 0NEM4UlZRQzdTUkJ8MTQ4NDY0NDAxMQ==|bb3be42f90aa3cfc38a5f42600
>> fa4a9ed8776421=04c82f8e-ce66-454b-9cbf-a67140
>> 4109d7=api-.duosecurity.com
>>
>> [image: Inline image 2]
>> Can you please suggest what could be the reason?
>>
>>
>> Thanks,
>> Thulasika.
>>
>> --
>> Thulasika
>> Associate Software Engineer
>> Mobile:0778014295
>> email: thulas...@wso2.com <sanj...@wso2.com>
>>
>
>
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>



-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com <sanj...@wso2.com>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

2017-01-17 Thread Thulasika Vijayanathan

Hi,

I am verifying the authenticators with IS 5.3.0. When I test Duo security
authenticator with IS 5.3.0, I got the blank page, but it works with IS
5.2.0. It seems redirect URL and signature are correct, because If we give
the wrong signature, the page will display as Access denied, Duo
Provisioning connector works fine with both IS 5.2.0 and 5.3.0.

Redirect URL in IS 5.3.0
https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp?authenticator=DuoAuthenticator:LOCAL=duo=TX|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDUwMg==|f4345a7f517828d259b235703310c09b594b736c:APP|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MzgwMg==|f65d989f837105e4a4d77167911f5abf09b7095c=bd19a4d8-f08e-4322-b0a8-cbbb31a144a7=api-.duosecurity.com

[image: Inline image 3]

Redirect URL in IS 5.2.0
https://localhost:9443/duoauthenticationendpoint/duoAuth.jsp?authenticator=DuoAuthenticator:LOCAL=duo=TX|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0MDcxMQ==|969c487f980bfb10e7a45a4b43d06543a78b9500:APP|YWRtaW58REkySjlaVk40NEM4UlZRQzdTUkJ8MTQ4NDY0NDAxMQ==|bb3be42f90aa3cfc38a5f42600fa4a9ed8776421=04c82f8e-ce66-454b-9cbf-a671404109d7=api-.duosecurity.com

[image: Inline image 2]
Can you please suggest what could be the reason?


Thanks,
Thulasika.

-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

2016-11-16 Thread Thulasika Vijayanathan

Hi,

Since there is no option to enable the JWT grant type with IS 5.2.0, as a
fix we skip the validation of the grant type. Please find the published jwt
connector[1].

[1]
https://store.wso2.com/store/assets/isconnector/details/8affec9a-706f-4e72-83ec-f65c42895d40

Thanks,
Thulasika.

On Wed, Nov 16, 2016 at 12:28 PM, Thulasika Vijayanathan <thulas...@wso2.com
> wrote:

> Noted Malaka.
>
> On Wed, Nov 16, 2016 at 11:35 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Thulasika,
>>
>> As we discussed offline please check the fix.
>>
>> On Wed, Nov 16, 2016 at 10:30 AM, Farasath Ahamed <farasa...@wso2.com>
>> wrote:
>>
>>> Hi Malaka/Thulasika,
>>>
>>> Since we can't fix this for IS 5.2.0 now as it is already released.
>>> Shall we fix it from JWT bearer grant connector side for IS 5.2.0 only?
>>> Otherwise, we won't have a JWT connector that is working with IS 5.2.0.
>>>
>>> WDYT?
>>>
>>> Thanks,
>>>
>>> Farasath Ahamed
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>> Mobile: +94777603866
>>> Blog: blog.farazath.com
>>> Twitter: @farazath619 <https://twitter.com/farazath619>
>>> <http://wso2.com/signature>
>>>
>>>
>>>
>>> On Wed, Nov 16, 2016 at 10:18 AM, Thulasika Vijayanathan <
>>> thulas...@wso2.com> wrote:
>>>
>>>> yes Malaka, It doesn't work with fresh 5.2.0 pack.
>>>>
>>>> On Tue, Nov 15, 2016 at 1:57 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> If this does not work with fresh pack we can't say it's supported.
>>>>>
>>>>> On Tue, Nov 15, 2016 at 9:38 AM, Thulasika Vijayanathan <
>>>>> thulas...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have applied this fixed as a patch in 5.2.0 it works.
>>>>>>
>>>>>> Thanks,
>>>>>> Thulasika.
>>>>>>
>>>>>> On Mon, Nov 14, 2016 at 12:25 AM, Farasath Ahamed <farasa...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Yes. This is now fixed with [1] by Maduranga. Now we can enable to
>>>>>>> disable custom grant types using the Service Provider UI.
>>>>>>>
>>>>>>> Shall we update the JWT Grant Type connector docs with this change?
>>>>>>>
>>>>>>>
>>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Farasath Ahamed
>>>>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>>>> Mobile: +94777603866
>>>>>>> Blog: blog.farazath.com
>>>>>>> Twitter: @farazath619 <https://twitter.com/farazath619>
>>>>>>> <http://wso2.com/signature>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Nov 11, 2016 at 5:36 PM, Malaka Silva <mal...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> So the fix needs to come from IS side I guess?
>>>>>>>>
>>>>>>>> On Fri, Nov 11, 2016 at 4:44 PM, Maduranga Siriwardena <
>>>>>>>> madura...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Thulasika,
>>>>>>>>>
>>>>>>>>> This issue is already reported with [1].
>>>>>>>>>
>>>>>>>>> As a fix we are planning to add the custom grant types also to the
>>>>>>>>> OAuth application configuration page to enable or disable.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Maduranga.
>>>>>>>>>
>>>>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>>>>>>>
>>>>>>>>> On Nov 11, 2016 4:23 PM, "Thulasika Vijayanathan" <
>>>>>>>>> thulas...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi ,
>>>>>>>>>>
>>>>>>>>>> I have checked the JWT grant type[1] in IS 5.2.0. It does not
>>>>>>>>>>  work, when val

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

2016-11-15 Thread Thulasika Vijayanathan

Noted Malaka.

On Wed, Nov 16, 2016 at 11:35 AM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Thulasika,
>
> As we discussed offline please check the fix.
>
> On Wed, Nov 16, 2016 at 10:30 AM, Farasath Ahamed <farasa...@wso2.com>
> wrote:
>
>> Hi Malaka/Thulasika,
>>
>> Since we can't fix this for IS 5.2.0 now as it is already released. Shall
>> we fix it from JWT bearer grant connector side for IS 5.2.0 only?
>> Otherwise, we won't have a JWT connector that is working with IS 5.2.0.
>>
>> WDYT?
>>
>> Thanks,
>>
>> Farasath Ahamed
>> Software Engineer, WSO2 Inc.; http://wso2.com
>> Mobile: +94777603866
>> Blog: blog.farazath.com
>> Twitter: @farazath619 <https://twitter.com/farazath619>
>> <http://wso2.com/signature>
>>
>>
>>
>> On Wed, Nov 16, 2016 at 10:18 AM, Thulasika Vijayanathan <
>> thulas...@wso2.com> wrote:
>>
>>> yes Malaka, It doesn't work with fresh 5.2.0 pack.
>>>
>>> On Tue, Nov 15, 2016 at 1:57 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> If this does not work with fresh pack we can't say it's supported.
>>>>
>>>> On Tue, Nov 15, 2016 at 9:38 AM, Thulasika Vijayanathan <
>>>> thulas...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have applied this fixed as a patch in 5.2.0 it works.
>>>>>
>>>>> Thanks,
>>>>> Thulasika.
>>>>>
>>>>> On Mon, Nov 14, 2016 at 12:25 AM, Farasath Ahamed <farasa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Yes. This is now fixed with [1] by Maduranga. Now we can enable to
>>>>>> disable custom grant types using the Service Provider UI.
>>>>>>
>>>>>> Shall we update the JWT Grant Type connector docs with this change?
>>>>>>
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>>>>
>>>>>> Thanks,
>>>>>> Farasath Ahamed
>>>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>>> Mobile: +94777603866
>>>>>> Blog: blog.farazath.com
>>>>>> Twitter: @farazath619 <https://twitter.com/farazath619>
>>>>>> <http://wso2.com/signature>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 11, 2016 at 5:36 PM, Malaka Silva <mal...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> So the fix needs to come from IS side I guess?
>>>>>>>
>>>>>>> On Fri, Nov 11, 2016 at 4:44 PM, Maduranga Siriwardena <
>>>>>>> madura...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Thulasika,
>>>>>>>>
>>>>>>>> This issue is already reported with [1].
>>>>>>>>
>>>>>>>> As a fix we are planning to add the custom grant types also to the
>>>>>>>> OAuth application configuration page to enable or disable.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Maduranga.
>>>>>>>>
>>>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>>>>>>
>>>>>>>> On Nov 11, 2016 4:23 PM, "Thulasika Vijayanathan" <
>>>>>>>> thulas...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi ,
>>>>>>>>>
>>>>>>>>> I have checked the JWT grant type[1] in IS 5.2.0. It does not
>>>>>>>>>  work, when validating the grant type it throws the exception[2].
>>>>>>>>>
>>>>>>>>> We need to get the  Allowed grant types as JWT,  but there is no
>>>>>>>>> option to thick the JWT grant type in UI. is there any way to get the 
>>>>>>>>> JWT
>>>>>>>>> grant type?
>>>>>>>>> [image: Inline image 2]
>>>>>>>>>
>>>>>>>>> [1] https://github.com/wso2-extensions/identity-oauth2-grant
>>>>>>>>> -jwt/blob/master/component/grant-type/src/main/java/org/wso2
>>>>>>>>> /carbon/identity/oauth2/grant/jwt/JWTBearerGrantHandler.java#L125

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

2016-11-15 Thread Thulasika Vijayanathan

yes Malaka, It doesn't work with fresh 5.2.0 pack.

On Tue, Nov 15, 2016 at 1:57 PM, Malaka Silva <mal...@wso2.com> wrote:

> If this does not work with fresh pack we can't say it's supported.
>
> On Tue, Nov 15, 2016 at 9:38 AM, Thulasika Vijayanathan <
> thulas...@wso2.com> wrote:
>
>> Hi,
>>
>> I have applied this fixed as a patch in 5.2.0 it works.
>>
>> Thanks,
>> Thulasika.
>>
>> On Mon, Nov 14, 2016 at 12:25 AM, Farasath Ahamed <farasa...@wso2.com>
>> wrote:
>>
>>> Yes. This is now fixed with [1] by Maduranga. Now we can enable to
>>> disable custom grant types using the Service Provider UI.
>>>
>>> Shall we update the JWT Grant Type connector docs with this change?
>>>
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>
>>> Thanks,
>>> Farasath Ahamed
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>> Mobile: +94777603866
>>> Blog: blog.farazath.com
>>> Twitter: @farazath619 <https://twitter.com/farazath619>
>>> <http://wso2.com/signature>
>>>
>>>
>>>
>>> On Fri, Nov 11, 2016 at 5:36 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> So the fix needs to come from IS side I guess?
>>>>
>>>> On Fri, Nov 11, 2016 at 4:44 PM, Maduranga Siriwardena <
>>>> madura...@wso2.com> wrote:
>>>>
>>>>> Hi Thulasika,
>>>>>
>>>>> This issue is already reported with [1].
>>>>>
>>>>> As a fix we are planning to add the custom grant types also to the
>>>>> OAuth application configuration page to enable or disable.
>>>>>
>>>>> Thanks,
>>>>> Maduranga.
>>>>>
>>>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>>>
>>>>> On Nov 11, 2016 4:23 PM, "Thulasika Vijayanathan" <thulas...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi ,
>>>>>>
>>>>>> I have checked the JWT grant type[1] in IS 5.2.0. It does not  work,
>>>>>> when validating the grant type it throws the exception[2].
>>>>>>
>>>>>> We need to get the  Allowed grant types as JWT,  but there is no
>>>>>> option to thick the JWT grant type in UI. is there any way to get the JWT
>>>>>> grant type?
>>>>>> [image: Inline image 2]
>>>>>>
>>>>>> [1] https://github.com/wso2-extensions/identity-oauth2-grant
>>>>>> -jwt/blob/master/component/grant-type/src/main/java/org/wso2
>>>>>> /carbon/identity/oauth2/grant/jwt/JWTBearerGrantHandler.java#L125
>>>>>>
>>>>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>>>>> -oauth/blob/v5.1.3/components/org.wso2.carbon.identity.oauth
>>>>>> /src/main/java/org/wso2/carbon/identity/oauth2/token/handler
>>>>>> s/grant/AbstractAuthorizationGrantHandler.java#L507
>>>>>>
>>>>>> Thanks,
>>>>>> Thulasika.
>>>>>> --
>>>>>> Thulasika
>>>>>> Associate Software Engineer
>>>>>> Mobile:0778014295
>>>>>> email: thulas...@wso2.com <sanj...@wso2.com>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Technical 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
>>>> https://wso2.com/signature
>>>> http://www.wso2.com/about/team/malaka-silva/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Don't make Trees rare, we should keep them with care
>>>>
>>>
>>>
>>
>>
>> --
>> Thulasika
>> Associate Software Engineer
>> Mobile:0778014295
>> email: thulas...@wso2.com <sanj...@wso2.com>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical 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
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>



-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com <sanj...@wso2.com>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

2016-11-14 Thread Thulasika Vijayanathan

Hi,

I have applied this fixed as a patch in 5.2.0 it works.

Thanks,
Thulasika.

On Mon, Nov 14, 2016 at 12:25 AM, Farasath Ahamed <farasa...@wso2.com>
wrote:

> Yes. This is now fixed with [1] by Maduranga. Now we can enable to disable
> custom grant types using the Service Provider UI.
>
> Shall we update the JWT Grant Type connector docs with this change?
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-5260
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>
> On Fri, Nov 11, 2016 at 5:36 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> So the fix needs to come from IS side I guess?
>>
>> On Fri, Nov 11, 2016 at 4:44 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Thulasika,
>>>
>>> This issue is already reported with [1].
>>>
>>> As a fix we are planning to add the custom grant types also to the OAuth
>>> application configuration page to enable or disable.
>>>
>>> Thanks,
>>> Maduranga.
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-5260
>>>
>>> On Nov 11, 2016 4:23 PM, "Thulasika Vijayanathan" <thulas...@wso2.com>
>>> wrote:
>>>
>>>> Hi ,
>>>>
>>>> I have checked the JWT grant type[1] in IS 5.2.0. It does not  work,
>>>> when validating the grant type it throws the exception[2].
>>>>
>>>> We need to get the  Allowed grant types as JWT,  but there is no option
>>>> to thick the JWT grant type in UI. is there any way to get the JWT grant
>>>> type?
>>>> [image: Inline image 2]
>>>>
>>>> [1] https://github.com/wso2-extensions/identity-oauth2-grant
>>>> -jwt/blob/master/component/grant-type/src/main/java/org/wso2
>>>> /carbon/identity/oauth2/grant/jwt/JWTBearerGrantHandler.java#L125
>>>>
>>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>>> -oauth/blob/v5.1.3/components/org.wso2.carbon.identity.oauth
>>>> /src/main/java/org/wso2/carbon/identity/oauth2/token/handler
>>>> s/grant/AbstractAuthorizationGrantHandler.java#L507
>>>>
>>>> Thanks,
>>>> Thulasika.
>>>> --
>>>> Thulasika
>>>> Associate Software Engineer
>>>> Mobile:0778014295
>>>> email: thulas...@wso2.com <sanj...@wso2.com>
>>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Technical 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
>> https://wso2.com/signature
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Don't make Trees rare, we should keep them with care
>>
>
>


-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com <sanj...@wso2.com>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] JWT Bearer Grant not working with IS 5.2.0

2016-11-11 Thread Thulasika Vijayanathan

Hi ,

I have checked the JWT grant type[1] in IS 5.2.0. It does not  work, when
validating the grant type it throws the exception[2].

We need to get the  Allowed grant types as JWT,  but there is no option to
thick the JWT grant type in UI. is there any way to get the JWT grant type?
[image: Inline image 2]

[1]
https://github.com/wso2-extensions/identity-oauth2-grant-jwt/blob/master/component/grant-type/src/main/java/org/wso2/carbon/identity/oauth2/grant/jwt/JWTBearerGrantHandler.java#L125

[2]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/v5.1.3/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/handlers/grant/AbstractAuthorizationGrantHandler.java#L507

Thanks,
Thulasika.
-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking Query type API call via People HR connector

2016-03-01 Thread Thulasika Vijayanathan

Hi Amalka,

Please find the updated peoplehr connector in store[1].
[1]
https://store.wso2.com/store/assets/esbconnector/875a8019-8fe9-42ff-9cd2-acb0ea7e2d3a

Thanks,
Thulasika.

On Mon, Feb 29, 2016 at 12:05 PM, Amalka Subasinghe  wrote:

> Hi,
>
> is it possible to $subject?
> According to the documentation I couldn't find a way
>
> [1] https://api.peoplehr.net/Pages/Functional/Default.aspx
> [2]
> https://docs.wso2.com/display/ESBCONNECTORS/Configuring+PeopleHR+Operations
>
> Thanks
> Amalka
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking Query type API call via People HR connector

2016-02-29 Thread Thulasika Vijayanathan

Hi,

yes, I will check this.

Thanks.
Thulasika.

On Mon, Feb 29, 2016 at 2:28 PM, Malaka Silva  wrote:

> Thulasika can you check this pls.
>
> On Mon, Feb 29, 2016 at 2:26 PM, Amalka Subasinghe 
> wrote:
>
>> Created a jira
>> https://wso2.org/jira/browse/ESBCONNECT-83
>>
>> Amalka Subasinghe
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile: +94 77 9401267
>>
>> On Mon, Feb 29, 2016 at 12:09 PM, Keerthika Mahendralingam <
>> keerth...@wso2.com> wrote:
>>
>>> Hi Amalka,
>>>
>>> We don't have that operation in current implemented connector. Could you
>>> please create a jira ticket for this?
>>>
>>> Thanks,
>>>
>>>
>>> On Mon, Feb 29, 2016 at 12:05 PM, Amalka Subasinghe 
>>> wrote:
>>>
 Hi,

 is it possible to $subject?
 According to the documentation I couldn't find a way

 [1] https://api.peoplehr.net/Pages/Functional/Default.aspx
 [2]
 https://docs.wso2.com/display/ESBCONNECTORS/Configuring+PeopleHR+Operations

 Thanks
 Amalka


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> 
>>> Keerthika Mahendralingam
>>> Associate Software Engineer
>>> Mobile :+94 (0) 776 121144
>>> keerth...@wso2.com
>>> WSO2, Inc.
>>> 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/
> 
> 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: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Connectors] Connectors with Refresh token support

2016-02-11 Thread Thulasika Vijayanathan

Hi Kasun,

We have automated init method to avoid the access token expiration and
applied  it for the following connectors:

   -  Google Prediction
   -  Google Task
   -  Google Spreadsheet
   -  SalesforceREST


Thank you

On Wed, Feb 10, 2016 at 10:49 AM, Kesavan Yogarajah 
wrote:

> Hi Kasun,
>
> Please find progress in mail thread [1].
>
> [1] - [Architecture] Fully automate cloud to cloud (iPaaS) use cases
>
> Thanks
>
> Kesavan Yogarajah
> Associate Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> On Wed, Feb 10, 2016 at 10:35 AM, Kasun Indrasiri  wrote:
>
>> Have we upgraded connectors to support refresh token persisting mechanism
>> in the latest ESB?
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Unable to configure Siebel CRM

2016-02-03 Thread Thulasika Vijayanathan

I have planned to do the siebel connector.So I am trying to install Siebel
CRM with the latest release of Siebel Innovation Pack 2015 (Siebel 15.0)
using  link[1].To install the siebel CRM  the following  jar file needs to
download from the "Oracle Software Delivery Cloud".

   -

   Siebel Industry Applications Version 15.0 Siebel Client (Starter
   Installation Requirement)
   -

  SBA_15.0.0.0_Base_Windows_Siebel_Web_Client.jar
  -

  SBA_15.0.0.0_enu_Windows_Siebel_Web_Client.jar
  -

   Siebel Industry Applications Version 15.0 Siebel Tools (Starter
   Installation Requirement)
   -

  SBA_15.0.0.0_Base_Windows_Siebel_Tools.jar
  -

  SBA_15.0.0.0_enu_Windows_Siebel_Tools.jar
  -

   Siebel Industry Applications Version 15.0 Sample Database Files
   -

  SBA_15.0.0.0_Base_Windows_Siebel_Sample_Database.jar
  -

  SBA_15.0.0.0_enu_Windows_Siebel_Sample_Database.jar
  -

   Siebel Industry Applications Version 15.0 ImageCreator Files (Starter
   Installation Requirement)
   -

  all files

But I am unable to find the below files in edelivery oracle site ,

Siebel Industry Applications Version 15.0 Sample Database Files

   -

   SBA_15.0.0.0_Base_Windows_Siebel_Sample_Database.jar
   -

   SBA_15.0.0.0_enu_Windows_Siebel_Sample_Database.jar

Can you please tell if you have any experience on this or suggest any other
solution for this?

[1] https://www.youtube.com/watch?v=7E_RYaB1v0k


Thanks,

Thulasika

-- 
Thulasika
Associate Software Engineer
Mobile:0778014295
email: thulas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Exceptions thrown when using salesforce and google-spreadsheet connectors together inside an iterator of a proxy service

2015-12-07 Thread Thulasika Vijayanathan

Hi Riyafa,

For the google spreadsheet connector, you need to enable the following
builders and formatters.









Thanks,
Thulasika

On Mon, Dec 7, 2015 at 1:15 PM, Malaka Silva  wrote:

> Riyafa seems like a builder error. Can you try enabling wire logs and
> analyse the response from the APIs.
>
> Also what is your use case?
>
> On Mon, Dec 7, 2015 at 12:08 PM, Riyafa Abdul Hameed 
> wrote:
>
>> Hi,
>>
>> I have a proxy service which I have attached with the mail which makes
>> several one call to the salesforce api using the salesforce connector and
>> two calls to the google spreadsheet api using the google-spreadsheet
>> connector in each iteration. When the number of rows I call (or the number
>> of iterations) increase beyond 35 the proxy service starts throwing the
>> following two exceptions:
>>
>>
>> *[2015-12-07 11:22:03,785] ERROR - RelayUtils Error while building
>> Passthrough stream *
>>
>> *org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException:
>> DOCTYPE is not allowed *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:149)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:400)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>> *
>>
>> * at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) *
>>
>> * at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>> *
>>
>> * at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> *
>>
>> * at java.lang.Thread.run(Thread.java:745) *
>>
>> *Caused by: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed *
>>
>> * at
>> org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:36)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>> *
>>
>> * ... 14 more *
>>
>> And
>>
>>
>> *[2015-12-07 11:22:04,040] ERROR - RelayUtils Error while building
>> Passthrough stream *
>>
>> *org.apache.axiom.om.OMException:
>> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'I'
>> (code 73) in prolog; expected '<' *
>>
>> *at [row,col {unknown-source}]: [1,1] *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:149)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:400)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>> *
>>
>> * at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) *
>>
>> * at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>> *
>>
>> * at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> *
>>
>> * at java.lang.Thread.run(Thread.java:745) *
>>
>> *Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> character 'I' (code 73) in prolog;

Re: [Dev] Removing Google Spread Sheet Connector

2015-09-28 Thread Thulasika Vijayanathan

Hi Malaka,

yes, I can do this.

Thanks,

On Mon, Sep 28, 2015 at 2:48 PM, Malaka Silva  wrote:

> Hi Thulasika,
>
> As discussed offline can you start on this please?
>
> On Wed, Sep 23, 2015 at 2:16 PM, Madusanka Premaratne  > wrote:
>
>> The real reason to worry about Google Plus Connector is MySelf +
>> TharinduA developed it as one of our training work sometimes back.
>> Anyway thanks for the response.
>>
>> Madusanka
>>
>> On Wed, Sep 23, 2015 at 2:10 PM, Malaka Silva  wrote:
>>
>>> Yes we have done some of those and will do in future as well.
>>>
>>> We will not be doing google plus since it not widely used anymore.
>>>
>>> On Wed, Sep 23, 2015 at 1:55 PM, Madusanka Premaratne <
>>> madusan...@wso2.com> wrote:
>>>
 Hi Malaka,
 AFAIK most of the google APIs got changed with that particular update
 mentioned by Rajjaz. We might need to change GooglePlus and other Google
 connectors also.

 Thanks,
 Madusanka

 On Wed, Sep 23, 2015 at 11:12 AM, Rajjaz Mohammed 
 wrote:

> +1
> some methods(Create Spreadsheet) are still not changed to OAuth 2.0 so
> there are not working.  since Spreadsheet one of important Connector 
> better
> if we can rewrite quickly.
>
> On Wed, Sep 23, 2015 at 10:44 AM, Malaka Silva 
> wrote:
>
>> Hi,
>>
>> We will be removing this connector, since the api this connector was
>> written is deprecated by google. Only some of the methods are currently
>> working.
>>
>> Will add a new version soon.
>>
>> https://store.wso2.com/store/
>>
>> 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/
>> 
>>
>> Save a tree -Conserve nature & Save the world for your future. Print
>> this email only if it is absolutely necessary.
>>
>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Madusanka Premaratne* | Associate Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 835 70 73| Work: +94 112 145 345
 Email: madusan...@wso2.com | Web: www.wso2.com

 [image: Facebook]  [image: Twitter]
  [image: Google Plus]
  [image:
 Linkedin]  [image: Instagram]
  [image: Skype]
 


>>>
>>>
>>> --
>>>
>>> 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/
>>> 
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
>
> 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 :

[Dev] [ESB] Error while starting the ESB-4.9.0-Alpha

2015-07-20 Thread Thulasika Vijayanathan

Hi,

I am getting the following error when I start the ESB-4.9.0-Alpha.I am able
to start the ESB-4.8.1 without any issue. what could be the reason for this?


thulasi@thulasi-ThinkPad-T540p
:~/Documents/ESB_4.9.0_Alpha/wso2esb-4.9.0-ALPHA/bin$ ./wso2server.sh
JAVA_HOME environment variable is set to /usr/local/java/jdk1.7.0_79
CARBON_HOME environment variable is set to
/home/thulasi/Documents/ESB_4.9.0_Alpha/wso2esb-4.9.0-ALPHA
[2015-07-20 13:24:47,260]  INFO - CarbonCoreActivator Starting WSO2
Carbon...
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Operating System :
Linux 3.13.0-24-generic, amd64
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Java Home:
/usr/local/java/jdk1.7.0_79/jre
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Java Version :
1.7.0_79
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Java VM  :
Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Carbon Home  :
/home/thulasi/Documents/ESB_4.9.0_Alpha/wso2esb-4.9.0-ALPHA
[2015-07-20 13:24:47,263]  INFO - CarbonCoreActivator Java Temp Dir:
/home/thulasi/Documents/ESB_4.9.0_Alpha/wso2esb-4.9.0-ALPHA/tmp
[2015-07-20 13:24:47,264]  INFO - CarbonCoreActivator User :
thulasi, en-US, Asia/Colombo
[2015-07-20 13:24:47,334]  WARN - ValidationResultPrinter Carbon is
configured to use the default keystore (wso2carbon.jks). To maximize
security when deploying to a production environment, configure a new
keystore with a unique password in the production server profile.
[2015-07-20 13:24:47,335]  WARN - ValidationResultPrinter Swap Memory size
(MB): 0 of the system is below the recommended minimum size :2047
[2015-07-20 13:24:47,342]  INFO - AgentHolder Agent created !
[2015-07-20 13:24:47,356]  INFO - AgentDS Successfully deployed Agent Client
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for http://cxf.apache.org/blueprint/core
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for http://cxf.apache.org/configuration/beans
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for
http://cxf.apache.org/configuration/parameterized-types
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for http://cxf.apache.org/configuration/security
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for http://schemas.xmlsoap.org/wsdl/
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for http://www.w3.org/2005/08/addressing
[2015-07-20 13:24:47,527]  INFO - NamespaceHandlerRegisterer Registered
blueprint namespace handler for
http://schemas.xmlsoap.org/ws/2004/08/addressing
[2015-07-20 13:24:49,122] ERROR - ContainerBase A child container failed
during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/]]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:816)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
... 6 more
Caused by: java.lang.IllegalStateException: Unable to complete the scan for
annotations for web application [/] due to a StackOverflowError. Possible
root causes include a too low setting for -Xss and illegal cyclic
inheritance dependencies. The class hierarchy being processed was
[org.bouncycastle.asn1.ASN1EncodableVector-org.bouncycastle.asn1.DEREncodableVector-org.bouncycastle.asn1.ASN1EncodableVector]
at
org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2144)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2090)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1965)
at

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

Re: [Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

[Dev] Getting blank page while verifying the Duo Security authenticator with IS 5.3.0

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

Re: [Dev] JWT Bearer Grant not working with IS 5.2.0

[Dev] JWT Bearer Grant not working with IS 5.2.0

Re: [Dev] Invoking Query type API call via People HR connector

Re: [Dev] Invoking Query type API call via People HR connector

Re: [Dev] [ESB Connectors] Connectors with Refresh token support

[Dev] Unable to configure Siebel CRM

Re: [Dev] [ESB] Exceptions thrown when using salesforce and google-spreadsheet connectors together inside an iterator of a proxy service

Re: [Dev] Removing Google Spread Sheet Connector

[Dev] [ESB] Error while starting the ESB-4.9.0-Alpha

17 matches

Site Navigation

Mail list logo

Footer information