Re: [Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Dilshani Subasinghe]

@Omindu - Thanks for the explanation and understood the point.

@Tharindu - Thanks and will refer them.

On Thu, Dec 14, 2017 at 3:22 AM, Tharindu Edirisinghe 
wrote:

> Hi Dilshani,
>
> The blog post [1] would be useful for you which is exactly the same
> scenario that you have faced. An example OAuth flow is explained in [2].
>
> [1] http://dinukshaish.blogspot.com/2017/02/mandatory-claims-
> in-oauth-20-with.html
> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-
> with-oauth-20-using.html
>
> Thanks,
> TharinduE
>
> On Wed, Dec 13, 2017 at 7:50 AM, Omindu Rathnaweera 
> wrote:
>
>> Hi Dilshani,
>>
>> If you have marked a requested claim in SP claim configs as mandatory, IS
>> will prompt this page if the claim is not available for the user in the
>> user store and it's not specific to the SPA. In your case, for the
>> authenticated user 'department' claim value is not available in the user
>> store hence the prompt. Refer 'Information on mapping claims' section in
>> [1] for a detailed explanation on mandatory claims.
>>
>> [1] - https://docs.wso2.com/display/IS530/Configuring+Claims+
>> for+a+Service+Provider
>>
>> Regards,
>> Omindu.
>>
>> On Wed, Dec 13, 2017 at 3:57 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am working on scenario 17 (Single Page Application (SPA) proxy) [1].
>>>
>>> In this scenario, I configure SP with OAuth 2.0 authorization code
>>> grant.  So I try out claims configurations in SP side. While testing that,
>>> noticed different behaviors in IS while requesting mandatory claims as
>>> follows;
>>>
>>>
>>> ​
>>>
>>> Above screenshot also showing that only requesting one claim
>>> (department), while it configured two mandatory claims in SP.
>>>
>>> I need to clarify exact way of requesting claims. Is that going to
>>> handle by IS or by web app? If it is going to handle by IS, it should show
>>> all mandatory claims. We tried claim mapping in SP with Travelocity and it
>>> works fine.
>>> According to this scenario, I have to use Single Page Application [2].
>>> Hence bit confuse about the functionality (Whether this is a limitation of
>>> SPA or issue in IS).
>>>
>>> Any help on this will be highly appreciated.
>>>
>>> [1] https://medium.facilelogin.com/thirty-solution-patterns-
>>> with-the-wso2-identity-server-16f9fd0c0389
>>> [2] https://github.com/facilelogin/aratuwa/tree/master/oauth
>>> 2.0-apps/org.wso2.carbon.identity.oauth.spa
>>>
>>> Thanks.
>>>
>>> --
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA *|* WSO2
>>> lean *|* enterprise *|* middleware
>>>
>>> Mobile : +94773375185 <+94%2077%20337%205185>
>>> Blog: dilshani.me
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Omindu Rathnaweera
>> Senior Software Engineer, WSO2 Inc.
>> Mobile: +94 771 197 211 <+94%2077%20119%207211>
>>
>
>
>
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : http://tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>



-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me


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

Re: [Dev] Exception while invoking the API with GET resource in ESB 5.0.0

[Gayan Dhanushka]

Hi Dilusha,

Are you using a port offset in DSS ? If you are using a port offset and
making a HTTPS call to the DSS make sure that you are using 9443 + offset
as the port to invoke the data service.

Regards
Gayan

On Wed, Dec 13, 2017 at 7:29 PM, Irham Iqbal  wrote:

> Hi Dilusha,
>
> Seems like you have a problem with your data service. Make sure it's
> working by accessing the wsdl from your browser as below.
> https://10.100.7.44:9773/services/CUSTOMER_INPUT_DataService?wsdl
>
> Thanks,
> Iqbal
>
> On Thu, Dec 14, 2017 at 12:10 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Dilusha,
>>
>> Based on the stack trace, it looks like you have a mismatch with the
>> protocol and the port. Make sure you have used the correct ports.
>>
>> Thank you!
>>
>> On Wed, Dec 13, 2017 at 7:49 PM, Firzhan Naqash  wrote:
>>
>>> Hi Dilusha,
>>>
>>> Can you set the Accept header with your CURL command?
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> email: firz...@wso2.com
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>>   *
>>> *twitter: https://twitter.com/firzhan007
>>>  | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> *
>>>
>>> On Wed, Dec 13, 2017 at 7:40 PM, Dilusha Alphonso 
>>> wrote:
>>>
 Hi All,

 I am trying to invoke an API deployed in WSO2ESB 5.0.0 with 'GET'
 resource. The endpoint of the API in a data service hosted in WSO2 DSS. I
 encountered an error in the console while invoking the API using cURL
 command

 Below is the error encountered in the console:

 [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "GET /getcardata/10 HTTP/1.1[\r][\n]"
 [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "Host: 10.100.7.44:8280[\r][\n]"
 [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "User-Agent: curl/7.52.1[\r][\n]"
 [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "Accept: */*[\r][\n]"
 [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "Authorization: Bearer 2ad64c91-2757-3a2d-834b-32ca671e08fe[\r][\n]"
 [2017-12-13 19:21:07,891] DEBUG - wire HTTP-Listener I/O dispatcher-3
 >> "[\r][\n]"
 [2017-12-13 19:21:07,997]  WARN - SynapseJsonPath Json Payload is empty.
 [2017-12-13 19:21:08,006] ERROR - TargetHandler I/O error: Unrecognized
 SSL message, plaintext connection?
 javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
 connection?
 at sun.security.ssl.EngineInputRecord.bytesInCompletePacket(Eng
 ineInputRecord.java:156)
 at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:868)
 at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
 at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
 at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS
 ession.java:245)
 at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
 IOSession.java:280)
 at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
 (SSLIOSession.java:410)
 at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
 dy(AbstractIODispatch.java:119)
 at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base
 IOReactor.java:159)
 at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
 ent(AbstractIOReactor.java:338)
 at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
 ents(AbstractIOReactor.java:316)
 at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A
 bstractIOReactor.java:277)
 at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
 OReactor.java:105)
 at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
 r$Worker.run(AbstractMultiworkerIOReactor.java:586)
 at java.lang.Thread.run(Thread.java:748)
 [2017-12-13 19:21:08,007]  WARN - EndpointContext Endpoint :
 AnonymousEndpoint with address https://10.100.7.44:9773/servi
 ces/CUSTOMER_INPUT_DataService/ will be marked SUSPENDED as it failed
 [2017-12-13 19:21:08,007]  WARN - EndpointContext Suspending endpoint :
 AnonymousEndpoint with address https://10.100.7.44:9773/servi
 ces/CUSTOMER_INPUT_DataService/ - current suspend duration is :
 3ms - Next retry after : Wed Dec 13 19:21:38 IST 2017
 [2017-12-13 19:21:08,008]  INFO - LogMediator To: /getcardata/10,
 MessageID: urn:uuid:ceff8fa9-bc8e-4cf5-9272-9ed612aad557, Direction:
 request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101500,
 ERROR_MESSAGE = Error in Sender, Envelope: >>> encoding='utf-8'?>http://www.w3.o
 rg/2003/05/soap-envelope" xmlns:p="https://car.input.wso2.com";>https://car.input.wso2.com"/ USTOMER_INPUT_operation>
 [

Re: [Dev] Call vs Callout mediator performance

[Chandana Napagoda]

Hi Isuru,

So, the only advantage over Callout mediator is that, the worker threads
can serve other incoming requests than waiting for backend response. Does
my understanding is correct?

Is there any other advantages of the underlying library used by call
mediator?

Regards,
Chandana

On 14 December 2017 at 12:02, Isuru Udana  wrote:

> Hi Chandana,
>
> In latest EI/ESB versions, defaultMaxConnectionsPerHost is already set to
> 200. That will solve the concurrency problem.
> In Callout mediator, engine resources (threads) kept waiting for backend
> to respond whereas in Call mediator (in non-blocking mode) threads get
> released once request is submitted to the backend.
> So due to the non-blocking nature of underlying transport implementation
> used in Call mediator, we could expect higher performance in Call mediator.
>
> Thanks.
>
> On Thu, Dec 14, 2017 at 6:54 AM, Chandana Napagoda 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 EI product documentation states that[1] call mediator has greater
>> performance than callout mediator.  As per my understanding callout
>> mediator has a limitation that its only allow two simultaneous connections
>> per host. However, we can mitigate that limitation by adding
>> "defaultMaxConnectionsPerHost" configuration[2].
>>
>> After adding above configuration does Callout mediator perform same as
>> Call mediator for less load per the same host? Is there any performance
>> round results for Callout vs Call scenario(blocking and non blocking)?
>>
>> [1]. *The Call mediator leverages the non-blocking transports for much
>> greater performance than the Callout mediator, so you should use the Call
>> mediator in most cases. *
>>
>> [2]. http://mytecheye.blogspot.com/2013/09/wso2-esb-improve-
>> callout-mediator.html
>>
>> Regards,
>> Chandana
>>
>> --
>>
>> Blog: http://blog.napagoda.com
>> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Udana*
> Senior Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887 <+94%2077%20379%201887>
> blog: http://mytecheye.blogspot.com/
>



-- 

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Call vs Callout mediator performance

[Isuru Udana]

Hi Chandana,

In latest EI/ESB versions, defaultMaxConnectionsPerHost is already set to
200. That will solve the concurrency problem.
In Callout mediator, engine resources (threads) kept waiting for backend to
respond whereas in Call mediator (in non-blocking mode) threads get
released once request is submitted to the backend.
So due to the non-blocking nature of underlying transport implementation
used in Call mediator, we could expect higher performance in Call mediator.

Thanks.

On Thu, Dec 14, 2017 at 6:54 AM, Chandana Napagoda 
wrote:

> Hi Devs,
>
> WSO2 EI product documentation states that[1] call mediator has greater
> performance than callout mediator.  As per my understanding callout
> mediator has a limitation that its only allow two simultaneous connections
> per host. However, we can mitigate that limitation by adding
> "defaultMaxConnectionsPerHost" configuration[2].
>
> After adding above configuration does Callout mediator perform same as
> Call mediator for less load per the same host? Is there any performance
> round results for Callout vs Call scenario(blocking and non blocking)?
>
> [1]. *The Call mediator leverages the non-blocking transports for much
> greater performance than the Callout mediator, so you should use the Call
> mediator in most cases. *
>
> [2]. http://mytecheye.blogspot.com/2013/09/wso2-esb-
> improve-callout-mediator.html
>
> Regards,
> Chandana
>
> --
>
> Blog: http://blog.napagoda.com
> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception while invoking the API with GET resource in ESB 5.0.0

[Irham Iqbal]

Hi Dilusha,

Seems like you have a problem with your data service. Make sure it's
working by accessing the wsdl from your browser as below.
https://10.100.7.44:9773/services/CUSTOMER_INPUT_DataService?wsdl

Thanks,
Iqbal

On Thu, Dec 14, 2017 at 12:10 AM, Pubudu Gunatilaka 
wrote:

> Hi Dilusha,
>
> Based on the stack trace, it looks like you have a mismatch with the
> protocol and the port. Make sure you have used the correct ports.
>
> Thank you!
>
> On Wed, Dec 13, 2017 at 7:49 PM, Firzhan Naqash  wrote:
>
>> Hi Dilusha,
>>
>> Can you set the Accept header with your CURL command?
>>
>> Regards,
>> Firzhan
>>
>>
>> email: firz...@wso2.com
>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>> blog: http://firzhanblogger.blogspot.com/
>>   *
>> *twitter: https://twitter.com/firzhan007
>>  | linked-in: 
>> **https://www.linkedin.com/in/firzhan
>> *
>>
>> On Wed, Dec 13, 2017 at 7:40 PM, Dilusha Alphonso 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am trying to invoke an API deployed in WSO2ESB 5.0.0 with 'GET'
>>> resource. The endpoint of the API in a data service hosted in WSO2 DSS. I
>>> encountered an error in the console while invoking the API using cURL
>>> command
>>>
>>> Below is the error encountered in the console:
>>>
>>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "GET /getcardata/10 HTTP/1.1[\r][\n]"
>>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "Host: 10.100.7.44:8280[\r][\n]"
>>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "User-Agent: curl/7.52.1[\r][\n]"
>>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "Accept: */*[\r][\n]"
>>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "Authorization: Bearer 2ad64c91-2757-3a2d-834b-32ca671e08fe[\r][\n]"
>>> [2017-12-13 19:21:07,891] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>>> "[\r][\n]"
>>> [2017-12-13 19:21:07,997]  WARN - SynapseJsonPath Json Payload is empty.
>>> [2017-12-13 19:21:08,006] ERROR - TargetHandler I/O error: Unrecognized
>>> SSL message, plaintext connection?
>>> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
>>> connection?
>>> at sun.security.ssl.EngineInputRecord.bytesInCompletePacket(Eng
>>> ineInputRecord.java:156)
>>> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:868)
>>> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
>>> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS
>>> ession.java:245)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
>>> IOSession.java:280)
>>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
>>> (SSLIOSession.java:410)
>>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
>>> dy(AbstractIODispatch.java:119)
>>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base
>>> IOReactor.java:159)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>>> ent(AbstractIOReactor.java:338)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>>> ents(AbstractIOReactor.java:316)
>>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A
>>> bstractIOReactor.java:277)
>>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
>>> OReactor.java:105)
>>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
>>> r$Worker.run(AbstractMultiworkerIOReactor.java:586)
>>> at java.lang.Thread.run(Thread.java:748)
>>> [2017-12-13 19:21:08,007]  WARN - EndpointContext Endpoint :
>>> AnonymousEndpoint with address https://10.100.7.44:9773/servi
>>> ces/CUSTOMER_INPUT_DataService/ will be marked SUSPENDED as it failed
>>> [2017-12-13 19:21:08,007]  WARN - EndpointContext Suspending endpoint :
>>> AnonymousEndpoint with address https://10.100.7.44:9773/servi
>>> ces/CUSTOMER_INPUT_DataService/ - current suspend duration is : 3ms
>>> - Next retry after : Wed Dec 13 19:21:38 IST 2017
>>> [2017-12-13 19:21:08,008]  INFO - LogMediator To: /getcardata/10,
>>> MessageID: urn:uuid:ceff8fa9-bc8e-4cf5-9272-9ed612aad557, Direction:
>>> request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101500,
>>> ERROR_MESSAGE = Error in Sender, Envelope: >> encoding='utf-8'?>http://www.w3.o
>>> rg/2003/05/soap-envelope">>> xmlns:p="https://car.input.wso2.com";>https://car.input.wso2.com"/>>> USTOMER_INPUT_operation>
>>> [2017-12-13 19:24:08,079]  WARN - SourceHandler Connection time out
>>> after request is read: http-incoming-43 Socket Timeout : 18 Remote
>>> Address : /10.100.7.44:57608
>>>
>>> Can you please suggest on overcoming this issue?
>>>
>>> Thanks,
>>> Dilusha
>>> --
>>>
>>>
>>> *Best Regards,Dilusha Alphonso*
>>>
>>> *Software Engineer - Support Team*
>>>
>>>
>>> *WSO2*
>>> *Mobile :

[Dev] Call vs Callout mediator performance

[Chandana Napagoda]

Hi Devs,

WSO2 EI product documentation states that[1] call mediator has greater
performance than callout mediator.  As per my understanding callout
mediator has a limitation that its only allow two simultaneous connections
per host. However, we can mitigate that limitation by adding
"defaultMaxConnectionsPerHost" configuration[2].

After adding above configuration does Callout mediator perform same as Call
mediator for less load per the same host? Is there any performance round
results for Callout vs Call scenario(blocking and non blocking)?

[1]. *The Call mediator leverages the non-blocking transports for much
greater performance than the Callout mediator, so you should use the Call
mediator in most cases. *

[2].
http://mytecheye.blogspot.com/2013/09/wso2-esb-improve-callout-mediator.html

Regards,
Chandana

-- 

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] AssertionConsumerServiceUrl Always set to server local IP

[Tharindu Edirisinghe]

Hi Lahiru,

Can you modify the
wso2appm-1.2.0/repository/conf/identity/application-authentication.xml file
and add SSOUrl parameter [1] under SAMLSSOAuthenticator configuration.
There you can add the URL you need to be included as the SAML
authentication request's ACS URL. The particular code that builds the
request is in [2].

 


[1]
https://github.com/wso2-attic/carbon-identity/blob/master/components/application-mgt/org.wso2.carbon.identity.application.common/src/main/java/org/wso2/carbon/identity/application/common/util/IdentityApplicationConstants.java#L107
[2]
https://github.com/wso2-attic/carbon-identity/blob/master/components/application-authenticators/org.wso2.carbon.identity.application.authenticator.samlsso/src/main/java/org/wso2/carbon/identity/application/authenticator/samlsso/SAMLSSOAuthenticator.java#L80

Thanks,
Tharindu Edirisinghe

On Wed, Nov 29, 2017 at 4:33 AM, Lahiru J Ekanayake <
ekanayakelah...@gmail.com> wrote:

> Hi,
>
> I'm using App Manager 1.2.0 in my AWS instance and IS 5.3.0 as external
> identity provider in another AWS instance. In order to competible IS 5.3.0
> with App Manager 1.2.0 , I have copied bellow jar files to App Manager
> dropins folder. *The setup is working fine in my local environment* but
> there is an issue when I'm using the same setup* in AWS.*
>
> 1. org.wso2.carbon.identity.sso.saml.stub_5.3.0.jar
> 2. org.wso2.carbon.identity.application.mgt.stub_5.7.5.jar
>
> *Steps to reproduce the issue.*
>
>1. Create a app uisng app manager publisher.
>2. Publish the app into the store.
>3. Log into the store and try to lunch the app.
>4. I'm getting an error saying invalid assertion consumer URL.
>
> I have used saml tracer and checked the saml request. As in the saml
> request *AssertionConsumerServiceUrl takes the server local IP (image
> attached - acs.png)*. I tried to change that IP by configuring carbon.xml
> and app-manager.xml . But i couldn't find a way to do that. Is this a know
> issue or are there any configuration to change this
> AssertionConsumerServiceUrl ? . Could you please tell me , where this
> request is being generated, when I lunch the app.
>
> Regards
>
>
>
> --
> Lahiru J Ekanayake.
> University Of Peradeniya
> Mobile : +94718812629 <+94%2071%20881%202629>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : http://tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS 5.3.0] Secondary LDAP User Store Properties - DNSUrl and DnsDomain

[Tharindu Edirisinghe]

Hi Javier,

The SVN URL you have given is applicable for Carbon 4.2.0 based products.

For IS 5.3.0, you can refer the link [1].

There, URLOfDNS [1] and DNSDomainName [2] properties are used in the given
lines.

I am adding few folks from the IAM Team to get you help with your query.

[1]
https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/LDAPConnectionContext.java
[2]
https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/LDAPConnectionContext.java#L69
[3]
https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/ldap/LDAPConnectionContext.java#L71

Thanks,
Tharindu Edirisinghe

On Thu, Nov 30, 2017 at 4:50 PM, Vazquez-Hidalgo, Javier <
javier.vazquez-hida...@tdsecurities.com> wrote:

> Hello,
>
>
>
> When configuring a secondary LDAP user store I see (in the carbon kernel
> source code)  that there are two properties named “URLOfDNS” and
> “DNSDomainName”, can someone explain how they work together and under which
> circumstances is recommended to set these properties.
>
>
>
> https://svn.wso2.org/repos/wso2/carbon/kernel/tags/4.2.0/
> core/org.wso2.carbon.user.core/4.2.0/src/main/java/org/
> wso2/carbon/user/core/ldap/LDAPConnectionContext.java
>
>
>
>
>
> Thanks,
>
> Javier Vazquez
>
>
>
>
>
> If you wish to unsubscribe from receiving commercial electronic messages
> from TD Bank Group, please click here  or go
> to the following web address: www.td.com/tdoptout
> Si vous souhaitez vous désabonner des messages électroniques de nature
> commerciale envoyés par Groupe Banque TD veuillez cliquer ici
>  ou vous rendre à l'adresse www.td.com/tddesab
>
>
> NOTICE: Confidential message which may be privileged. Unauthorized
> use/disclosure prohibited. If received in error, please go to
> www.td.com/legal for instructions.
> AVIS : Message confidentiel dont le contenu peut être privilégié.
> Utilisation/divulgation interdites sans permission. Si reçu par erreur,
> prière d'aller au www.td.com/francais/avis_juridique pour des
> instructions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : http://tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Tharindu Edirisinghe]

Hi Dilshani,

The blog post [1] would be useful for you which is exactly the same
scenario that you have faced. An example OAuth flow is explained in [2].

[1]
http://dinukshaish.blogspot.com/2017/02/mandatory-claims-in-oauth-20-with.html
[2]
http://dinukshaish.blogspot.com/2017/02/getting-started-with-oauth-20-using.html

Thanks,
TharinduE

On Wed, Dec 13, 2017 at 7:50 AM, Omindu Rathnaweera  wrote:

> Hi Dilshani,
>
> If you have marked a requested claim in SP claim configs as mandatory, IS
> will prompt this page if the claim is not available for the user in the
> user store and it's not specific to the SPA. In your case, for the
> authenticated user 'department' claim value is not available in the user
> store hence the prompt. Refer 'Information on mapping claims' section in
> [1] for a detailed explanation on mandatory claims.
>
> [1] - https://docs.wso2.com/display/IS530/Configuring+
> Claims+for+a+Service+Provider
>
> Regards,
> Omindu.
>
> On Wed, Dec 13, 2017 at 3:57 PM, Dilshani Subasinghe 
> wrote:
>
>> Hi All,
>>
>> I am working on scenario 17 (Single Page Application (SPA) proxy) [1].
>>
>> In this scenario, I configure SP with OAuth 2.0 authorization code
>> grant.  So I try out claims configurations in SP side. While testing that,
>> noticed different behaviors in IS while requesting mandatory claims as
>> follows;
>>
>>
>> ​
>>
>> Above screenshot also showing that only requesting one claim
>> (department), while it configured two mandatory claims in SP.
>>
>> I need to clarify exact way of requesting claims. Is that going to handle
>> by IS or by web app? If it is going to handle by IS, it should show all
>> mandatory claims. We tried claim mapping in SP with Travelocity and it
>> works fine.
>> According to this scenario, I have to use Single Page Application [2].
>> Hence bit confuse about the functionality (Whether this is a limitation of
>> SPA or issue in IS).
>>
>> Any help on this will be highly appreciated.
>>
>> [1] https://medium.facilelogin.com/thirty-solution-patterns-
>> with-the-wso2-identity-server-16f9fd0c0389
>> [2] https://github.com/facilelogin/aratuwa/tree/master/
>> oauth2.0-apps/org.wso2.carbon.identity.oauth.spa
>>
>> Thanks.
>>
>> --
>>
>> Dilshani Subasinghe
>> Software Engineer - QA *|* WSO2
>> lean *|* enterprise *|* middleware
>>
>> Mobile : +94773375185 <+94%2077%20337%205185>
>> Blog: dilshani.me
>>
>> 
>>
>
>
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211 <+94%2077%20119%207211>
>



-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : http://tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stream Processor Editor - Removing .siddhi file extension from showing on the ui

[Damith Wickramasinghe]

@Grainier . Thanks for pointing it out . yes we need to use the substring
method. we have use the same split in other areas. we need to fix this.

Regards,
Damith

On Thu, Dec 14, 2017 at 1:54 AM, Grainier Perera  wrote:

> @Raveen, You have used to text.split(".")[0] to to remove .siddhi postfix
> right. But Siddhi allows having full stop ".", and ".siddhi" in the Siddhi
> App name. So this might not work... Try something like text.substring(0,
> text.lastIndexOf(".siddhi"))
>
> @Others, please check whether the editor works properly when the App name
> have "." or ".siddhi" within. Cause I tried "Receive.And.Count" as the name
> and the editor log gave me "Receive.siddhi - undefined".
>
> Thanks,
> Grainier
>
> On Mon, Dec 11, 2017 at 9:20 AM, Raveen Rathnayake 
> wrote:
>
>> Hi all,
>>
>> I have removed  displaying ".siddhi" clause from the tab and removed the
>> ".siddhi" postfix from ".siddhi" in save to file placeholder as well.
>> This PR[1] relevant changes.
>>
>> [1] https://github.com/wso2/carbon-analytics/pull/849
>>
>> Thank you.
>> Raveen.
>>
>> On Sat, Dec 9, 2017 at 11:53 PM, Damith Wickramasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> Yes +1 . I will inc-operate the changes .
>>>
>>> Regards,
>>> Damith
>>>
>>> On Fri, Dec 8, 2017 at 6:57 PM, Ramindu De Silva 
>>> wrote:
>>>
 Hi all,

 +1 for Erangas suggestion.
 We may need to remove the ".siddhi" postfix from ".siddhi" in save
 to file placeholder as well. Currently, we, either way, add .siddhi
 extension when saving the file.

 Best Regards,
 Ramindu.

 On Fri, Dec 8, 2017 at 11:16 AM, Eranga Liyanage 
 wrote:

> Hi All,
>
> Yes, we can show the .siddhi extension on workspace tree.
>
> Users first interaction with the file is either Save, Open, or Import.
> On those interfaces also we show that it's a .siddhi extension file, so
> users won't get confused by removing it from the tab.
>
> Best regards.
> Eranga
>
> On Fri, Dec 8, 2017 at 7:18 AM, Jason De Silva 
> wrote:
>
>> Hi Damith / Eranga,
>>
>> If I am the user I would like to know the extension of the file. So
>> +1 to at least show the .siddhi extension in workspace tree/dropdown if 
>> we
>> are removing it from the tabs.
>>
>> Regards,
>> Jason
>>
>> Jason De Silva
>> *Software Engineer - QA*
>> Mobile: +94 (0) 772 097 678
>> Email: jas...@wso2.com
>> WSO2 Inc. www.wso2.com
>> 
>>
>> On Fri, Dec 8, 2017 at 6:19 AM, Damith Wickramasinghe <
>> dami...@wso2.com> wrote:
>>
>>> Hi Eranga,
>>>
>>> I understand your point but my only issue is not conveying user that
>>> these files use .siddhi extension. So shall we at least keep the .siddhi
>>> extension in workspace dropdown as we are showing the actual files 
>>> there.
>>> So that user knows it. And we can remove the .siddhi extensions in tabs.
>>> WDYT ?
>>>
>>> Regards,
>>> Damith
>>>
>>> On Thu, Dec 7, 2017 at 11:42 AM, Eranga Liyanage 
>>> wrote:
>>>
 Hi Damith,

 In editors usually, we can edit multiple file types. So when the
 respective file is opened it shows the file type with it for easy
 identification.

 But in our case, we support only .siddhi files and we open files
 from our own workspace which contains only siddhi files. Many single 
 file
 type applications usually do not show its file type on UI.

 In the Stream Processor Editor, we usually open multiple siddhi
 files and in the tab area, it takes unnecessary space to show the 
 .siddhi
 extension. IMHO it's better to hide it from tab section.

 [image: Inline image 1]

 We can show the .siddhi extension on workspace tree and other file
 open/import etc. modals.

 WDYT?

 Best regards,
 Eranga


 On Thu, Dec 7, 2017 at 8:48 AM, Damith Wickramasinghe <
 dami...@wso2.com> wrote:

> Hi Eranga/ All,
>
> In stream processor we support only files with .siddhi extension.
> Even though it is the case IMO user needs to know that the file 
> should have
> .siddhi extension. Because one can just copy paste a file to workspace
> directory of editor without adding the .siddhi extension when he see 
> only
> files without extension created. And having it there also will not 
> make any
> UX issues as I see it. Please raise any concerns if we need to 
> accommodate
> this requirement.
>
> Regards,
> Damith
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 

Re: [Dev] Stream Processor Editor - Removing .siddhi file extension from showing on the ui

[Grainier Perera]

@Raveen, You have used to text.split(".")[0] to to remove .siddhi postfix
right. But Siddhi allows having full stop ".", and ".siddhi" in the Siddhi
App name. So this might not work... Try something like text.substring(0,
text.lastIndexOf(".siddhi"))

@Others, please check whether the editor works properly when the App name
have "." or ".siddhi" within. Cause I tried "Receive.And.Count" as the name
and the editor log gave me "Receive.siddhi - undefined".

Thanks,
Grainier

On Mon, Dec 11, 2017 at 9:20 AM, Raveen Rathnayake  wrote:

> Hi all,
>
> I have removed  displaying ".siddhi" clause from the tab and removed the
> ".siddhi" postfix from ".siddhi" in save to file placeholder as well.
> This PR[1] relevant changes.
>
> [1] https://github.com/wso2/carbon-analytics/pull/849
>
> Thank you.
> Raveen.
>
> On Sat, Dec 9, 2017 at 11:53 PM, Damith Wickramasinghe 
> wrote:
>
>> Hi All,
>>
>> Yes +1 . I will inc-operate the changes .
>>
>> Regards,
>> Damith
>>
>> On Fri, Dec 8, 2017 at 6:57 PM, Ramindu De Silva 
>> wrote:
>>
>>> Hi all,
>>>
>>> +1 for Erangas suggestion.
>>> We may need to remove the ".siddhi" postfix from ".siddhi" in save
>>> to file placeholder as well. Currently, we, either way, add .siddhi
>>> extension when saving the file.
>>>
>>> Best Regards,
>>> Ramindu.
>>>
>>> On Fri, Dec 8, 2017 at 11:16 AM, Eranga Liyanage 
>>> wrote:
>>>
 Hi All,

 Yes, we can show the .siddhi extension on workspace tree.

 Users first interaction with the file is either Save, Open, or Import.
 On those interfaces also we show that it's a .siddhi extension file, so
 users won't get confused by removing it from the tab.

 Best regards.
 Eranga

 On Fri, Dec 8, 2017 at 7:18 AM, Jason De Silva  wrote:

> Hi Damith / Eranga,
>
> If I am the user I would like to know the extension of the file. So +1
> to at least show the .siddhi extension in workspace tree/dropdown if we 
> are
> removing it from the tabs.
>
> Regards,
> Jason
>
> Jason De Silva
> *Software Engineer - QA*
> Mobile: +94 (0) 772 097 678
> Email: jas...@wso2.com
> WSO2 Inc. www.wso2.com
> 
>
> On Fri, Dec 8, 2017 at 6:19 AM, Damith Wickramasinghe <
> dami...@wso2.com> wrote:
>
>> Hi Eranga,
>>
>> I understand your point but my only issue is not conveying user that
>> these files use .siddhi extension. So shall we at least keep the .siddhi
>> extension in workspace dropdown as we are showing the actual files there.
>> So that user knows it. And we can remove the .siddhi extensions in tabs.
>> WDYT ?
>>
>> Regards,
>> Damith
>>
>> On Thu, Dec 7, 2017 at 11:42 AM, Eranga Liyanage 
>> wrote:
>>
>>> Hi Damith,
>>>
>>> In editors usually, we can edit multiple file types. So when the
>>> respective file is opened it shows the file type with it for easy
>>> identification.
>>>
>>> But in our case, we support only .siddhi files and we open files
>>> from our own workspace which contains only siddhi files. Many single 
>>> file
>>> type applications usually do not show its file type on UI.
>>>
>>> In the Stream Processor Editor, we usually open multiple siddhi
>>> files and in the tab area, it takes unnecessary space to show the 
>>> .siddhi
>>> extension. IMHO it's better to hide it from tab section.
>>>
>>> [image: Inline image 1]
>>>
>>> We can show the .siddhi extension on workspace tree and other file
>>> open/import etc. modals.
>>>
>>> WDYT?
>>>
>>> Best regards,
>>> Eranga
>>>
>>>
>>> On Thu, Dec 7, 2017 at 8:48 AM, Damith Wickramasinghe <
>>> dami...@wso2.com> wrote:
>>>
 Hi Eranga/ All,

 In stream processor we support only files with .siddhi extension.
 Even though it is the case IMO user needs to know that the file should 
 have
 .siddhi extension. Because one can just copy paste a file to workspace
 directory of editor without adding the .siddhi extension when he see 
 only
 files without extension created. And having it there also will not 
 make any
 UX issues as I see it. Please raise any concerns if we need to 
 accommodate
 this requirement.

 Regards,
 Damith

 --
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 
 lean.enterprise.middleware

 mobile: *+94728671315 <+94%2072%20867%201315>*


>>>
>>>
>>> --
>>> *Eranga Liyanage*
>>> Senior UX Engineer | WSO2
>>> Mob : +94 77 395 
>>> Blog : https://medium.com/@erangatl
>>> Linkedin : https://www.linkedin.com/in/eran

Re: [Dev] Exception while invoking the API with GET resource in ESB 5.0.0

[Pubudu Gunatilaka]

Hi Dilusha,

Based on the stack trace, it looks like you have a mismatch with the
protocol and the port. Make sure you have used the correct ports.

Thank you!

On Wed, Dec 13, 2017 at 7:49 PM, Firzhan Naqash  wrote:

> Hi Dilusha,
>
> Can you set the Accept header with your CURL command?
>
> Regards,
> Firzhan
>
>
> email: firz...@wso2.com
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
>   *
> *twitter: https://twitter.com/firzhan007
>  | linked-in: 
> **https://www.linkedin.com/in/firzhan
> *
>
> On Wed, Dec 13, 2017 at 7:40 PM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> I am trying to invoke an API deployed in WSO2ESB 5.0.0 with 'GET'
>> resource. The endpoint of the API in a data service hosted in WSO2 DSS. I
>> encountered an error in the console while invoking the API using cURL
>> command
>>
>> Below is the error encountered in the console:
>>
>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "GET /getcardata/10 HTTP/1.1[\r][\n]"
>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "Host: 10.100.7.44:8280[\r][\n]"
>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "User-Agent: curl/7.52.1[\r][\n]"
>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "Accept: */*[\r][\n]"
>> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "Authorization: Bearer 2ad64c91-2757-3a2d-834b-32ca671e08fe[\r][\n]"
>> [2017-12-13 19:21:07,891] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
>> "[\r][\n]"
>> [2017-12-13 19:21:07,997]  WARN - SynapseJsonPath Json Payload is empty.
>> [2017-12-13 19:21:08,006] ERROR - TargetHandler I/O error: Unrecognized
>> SSL message, plaintext connection?
>> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
>> connection?
>> at sun.security.ssl.EngineInputRecord.bytesInCompletePacket(Eng
>> ineInputRecord.java:156)
>> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:868)
>> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
>> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS
>> ession.java:245)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
>> IOSession.java:280)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
>> (SSLIOSession.java:410)
>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
>> dy(AbstractIODispatch.java:119)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(
>> BaseIOReactor.java:159)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ent(AbstractIOReactor.java:338)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ents(AbstractIOReactor.java:316)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(
>> AbstractIOReactor.java:277)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
>> OReactor.java:105)
>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
>> r$Worker.run(AbstractMultiworkerIOReactor.java:586)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-12-13 19:21:08,007]  WARN - EndpointContext Endpoint :
>> AnonymousEndpoint with address https://10.100.7.44:9773/servi
>> ces/CUSTOMER_INPUT_DataService/ will be marked SUSPENDED as it failed
>> [2017-12-13 19:21:08,007]  WARN - EndpointContext Suspending endpoint :
>> AnonymousEndpoint with address https://10.100.7.44:9773/servi
>> ces/CUSTOMER_INPUT_DataService/ - current suspend duration is : 3ms
>> - Next retry after : Wed Dec 13 19:21:38 IST 2017
>> [2017-12-13 19:21:08,008]  INFO - LogMediator To: /getcardata/10,
>> MessageID: urn:uuid:ceff8fa9-bc8e-4cf5-9272-9ed612aad557, Direction:
>> request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101500,
>> ERROR_MESSAGE = Error in Sender, Envelope: > encoding='utf-8'?>http://www.w3.o
>> rg/2003/05/soap-envelope">> xmlns:p="https://car.input.wso2.com";>https://car.input.wso2.com"/>> CUSTOMER_INPUT_operation>
>> [2017-12-13 19:24:08,079]  WARN - SourceHandler Connection time out after
>> request is read: http-incoming-43 Socket Timeout : 18 Remote Address : /
>> 10.100.7.44:57608
>>
>> Can you please suggest on overcoming this issue?
>>
>> Thanks,
>> Dilusha
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>> ___
>> 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
>
>


-- 

Re: [Dev] Exception while invoking the API with GET resource in ESB 5.0.0

[Firzhan Naqash]

Hi Dilusha,

Can you set the Accept header with your CURL command?

Regards,
Firzhan


email: firz...@wso2.com
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Wed, Dec 13, 2017 at 7:40 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> I am trying to invoke an API deployed in WSO2ESB 5.0.0 with 'GET'
> resource. The endpoint of the API in a data service hosted in WSO2 DSS. I
> encountered an error in the console while invoking the API using cURL
> command
>
> Below is the error encountered in the console:
>
> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "GET /getcardata/10 HTTP/1.1[\r][\n]"
> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "Host: 10.100.7.44:8280[\r][\n]"
> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "User-Agent: curl/7.52.1[\r][\n]"
> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "Accept: */*[\r][\n]"
> [2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "Authorization: Bearer 2ad64c91-2757-3a2d-834b-32ca671e08fe[\r][\n]"
> [2017-12-13 19:21:07,891] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
> "[\r][\n]"
> [2017-12-13 19:21:07,997]  WARN - SynapseJsonPath Json Payload is empty.
> [2017-12-13 19:21:08,006] ERROR - TargetHandler I/O error: Unrecognized
> SSL message, plaintext connection?
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at sun.security.ssl.EngineInputRecord.bytesInCompletePacket(
> EngineInputRecord.java:156)
> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:868)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(
> SSLIOSession.java:245)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(
> SSLIOSession.java:280)
> at org.apache.http.nio.reactor.ssl.SSLIOSession.
> isAppInputReady(SSLIOSession.java:410)
> at org.apache.http.impl.nio.reactor.AbstractIODispatch.
> inputReady(AbstractIODispatch.java:119)
> at org.apache.http.impl.nio.reactor.BaseIOReactor.
> readable(BaseIOReactor.java:159)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(
> AbstractIOReactor.java:338)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(
> AbstractIOReactor.java:316)
> at org.apache.http.impl.nio.reactor.AbstractIOReactor.
> execute(AbstractIOReactor.java:277)
> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(
> BaseIOReactor.java:105)
> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$
> Worker.run(AbstractMultiworkerIOReactor.java:586)
> at java.lang.Thread.run(Thread.java:748)
> [2017-12-13 19:21:08,007]  WARN - EndpointContext Endpoint :
> AnonymousEndpoint with address https://10.100.7.44:9773/
> services/CUSTOMER_INPUT_DataService/ will be marked SUSPENDED as it failed
> [2017-12-13 19:21:08,007]  WARN - EndpointContext Suspending endpoint :
> AnonymousEndpoint with address https://10.100.7.44:9773/
> services/CUSTOMER_INPUT_DataService/ - current suspend duration is :
> 3ms - Next retry after : Wed Dec 13 19:21:38 IST 2017
> [2017-12-13 19:21:08,008]  INFO - LogMediator To: /getcardata/10,
> MessageID: urn:uuid:ceff8fa9-bc8e-4cf5-9272-9ed612aad557, Direction:
> request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101500,
> ERROR_MESSAGE = Error in Sender, Envelope:  encoding='utf-8'?>http://www.w3.
> org/2003/05/soap-envelope"> xmlns:p="https://car.input.wso2.com";>https://car.input.wso2.com"/> key_CUSTOMER_INPUT_operation>
> [2017-12-13 19:24:08,079]  WARN - SourceHandler Connection time out after
> request is read: http-incoming-43 Socket Timeout : 18 Remote Address : /
> 10.100.7.44:57608
>
> Can you please suggest on overcoming this issue?
>
> Thanks,
> Dilusha
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> 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

[Dev] Exception while invoking the API with GET resource in ESB 5.0.0

[Dilusha Alphonso]

Hi All,

I am trying to invoke an API deployed in WSO2ESB 5.0.0 with 'GET' resource.
The endpoint of the API in a data service hosted in WSO2 DSS. I encountered
an error in the console while invoking the API using cURL command

Below is the error encountered in the console:

[2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"GET /getcardata/10 HTTP/1.1[\r][\n]"
[2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"Host: 10.100.7.44:8280[\r][\n]"
[2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"User-Agent: curl/7.52.1[\r][\n]"
[2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"Accept: */*[\r][\n]"
[2017-12-13 19:21:07,890] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"Authorization: Bearer 2ad64c91-2757-3a2d-834b-32ca671e08fe[\r][\n]"
[2017-12-13 19:21:07,891] DEBUG - wire HTTP-Listener I/O dispatcher-3 >>
"[\r][\n]"
[2017-12-13 19:21:07,997]  WARN - SynapseJsonPath Json Payload is empty.
[2017-12-13 19:21:08,006] ERROR - TargetHandler I/O error: Unrecognized SSL
message, plaintext connection?
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at
sun.security.ssl.EngineInputRecord.bytesInCompletePacket(EngineInputRecord.java:156)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:868)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOSession.java:245)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:280)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:410)
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
at java.lang.Thread.run(Thread.java:748)
[2017-12-13 19:21:08,007]  WARN - EndpointContext Endpoint :
AnonymousEndpoint with address
https://10.100.7.44:9773/services/CUSTOMER_INPUT_DataService/ will be
marked SUSPENDED as it failed
[2017-12-13 19:21:08,007]  WARN - EndpointContext Suspending endpoint :
AnonymousEndpoint with address
https://10.100.7.44:9773/services/CUSTOMER_INPUT_DataService/ - current
suspend duration is : 3ms - Next retry after : Wed Dec 13 19:21:38 IST
2017
[2017-12-13 19:21:08,008]  INFO - LogMediator To: /getcardata/10,
MessageID: urn:uuid:ceff8fa9-bc8e-4cf5-9272-9ed612aad557, Direction:
request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 101500,
ERROR_MESSAGE = Error in Sender, Envelope: http://www.w3.org/2003/05/soap-envelope";>https://car.input.wso2.com";>https://car.input.wso2.com
"/>
[2017-12-13 19:24:08,079]  WARN - SourceHandler Connection time out after
request is read: http-incoming-43 Socket Timeout : 18 Remote Address : /
10.100.7.44:57608

Can you please suggest on overcoming this issue?

Thanks,
Dilusha
-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Omindu Rathnaweera]

Hi Dilshani,

If you have marked a requested claim in SP claim configs as mandatory, IS
will prompt this page if the claim is not available for the user in the
user store and it's not specific to the SPA. In your case, for the
authenticated user 'department' claim value is not available in the user
store hence the prompt. Refer 'Information on mapping claims' section in
[1] for a detailed explanation on mandatory claims.

[1] -
https://docs.wso2.com/display/IS530/Configuring+Claims+for+a+Service+Provider

Regards,
Omindu.

On Wed, Dec 13, 2017 at 3:57 PM, Dilshani Subasinghe 
wrote:

> Hi All,
>
> I am working on scenario 17 (Single Page Application (SPA) proxy) [1].
>
> In this scenario, I configure SP with OAuth 2.0 authorization code grant.
> So I try out claims configurations in SP side. While testing that, noticed
> different behaviors in IS while requesting mandatory claims as follows;
>
>
> ​
>
> Above screenshot also showing that only requesting one claim (department),
> while it configured two mandatory claims in SP.
>
> I need to clarify exact way of requesting claims. Is that going to handle
> by IS or by web app? If it is going to handle by IS, it should show all
> mandatory claims. We tried claim mapping in SP with Travelocity and it
> works fine.
> According to this scenario, I have to use Single Page Application [2].
> Hence bit confuse about the functionality (Whether this is a limitation of
> SPA or issue in IS).
>
> Any help on this will be highly appreciated.
>
> [1] https://medium.facilelogin.com/thirty-solution-patterns-with-the-
> wso2-identity-server-16f9fd0c0389
> [2] https://github.com/facilelogin/aratuwa/tree/
> master/oauth2.0-apps/org.wso2.carbon.identity.oauth.spa
>
> Thanks.
>
> --
>
> Dilshani Subasinghe
> Software Engineer - QA *|* WSO2
> lean *|* enterprise *|* middleware
>
> Mobile : +94773375185 <+94%2077%20337%205185>
> Blog: dilshani.me
>
> 
>



-- 
Omindu Rathnaweera
Senior Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ACK interleaving

[Marco Sessa]

Hi Vinod,
I have found the potential problem:
one instance of the class
*org.wso2.carbon.business.messaging.hl7.common.HL7ProcessingContext*  is
shared over multiple threads request for the same proxy and the
blockingQueue *applicationResponses *could contains all the responses(in
any order based on server response time).
When *handleApplicationACK *is called from each thread this method return *the
first *response in the queue(if available, otherwise the thread wait for
any), without making sure it is the answer(ACK) associated with the current
message(*hl7Msg *parameter).
I have observed that the order of the *applicationResponses *queue could be
different of the order of the waiting thread.
This causes the wrong ACK to be sent to the sender.

How to we proceed to the bug fix?

Many thanks
Marco

P.S.: I have already opened this issue:
https://github.com/wso2/carbon-mediation/issues/928



*Marco Sessa*


*Software Analyst / Developer*
CSP S.p.A.
Napoli - Centro Direzionale,
isola G/1, scala C
Tel: 081.191.38.607
Cel: 340.8689247
Email: marco.se...@cspnet.it
www.cspnet.it


2017-12-02 6:20 GMT+01:00 Vinod Kavinda :

> Hi Marco,
> The HL7 related code is in [1] inside carbon-mediation repo.
>
> [1] - https://github.com/wso2/carbon-mediation/tree/master/
> components/business-adaptors/hl7
>
> Regards,
> Vinod
>
> On Sat, Dec 2, 2017 at 10:01 AM, Jason De Silva  wrote:
>
>> Hi Marco,
>>
>> In order to debug the code you should be able to do so by checking out
>> the code in [1] as mentioned in [2].
>>
>> [1] https://github.com/wso2/product-ei
>> [2] https://github.com/wso2/product-ei#build-from-the-source
>>
>> Regards,
>> Jason
>>
>> Jason De Silva
>> *Software Engineer - QA*
>> Mobile: +94 (0) 772 097 678
>> Email: jas...@wso2.com
>> WSO2 Inc. www.wso2.com
>> 
>>
>> On Sat, Dec 2, 2017 at 1:54 AM, Marco Sessa 
>> wrote:
>>
>>> Hi Dev,
>>> I am analyzed the ACK interleaving with Wireshark and I have observed
>>> that WSO2 Integrator send back ACK in the wrong channel if receive parallel
>>> messages on a HL7 proxy.
>>> I have opened this issue
>>>  on github.
>>> I would try to debug the code, but I not know which source code of
>>> projects other then wso2/product-ei I should download.
>>>
>>> Thanks for help
>>> Marco
>>>
>>> *Marco Sessa*
>>>
>>>
>>> *Software Analyst / Developer*
>>> CSP S.p.A.
>>> Napoli - Centro Direzionale,
>>> isola G/1, scala C
>>> Tel: 081.191.38.607
>>> Cel: 340.8689247
>>> Email: marco.se...@cspnet.it
>>> www.cspnet.it
>>>
>>>
>>> 2017-11-29 11:59 GMT+01:00 Marco Sessa :
>>>
 Hi All,
 I am struggling with an drawback related to ACK interleaving on a HL7
 proxy (EI 6.1.0).
 In some conditions (parallel request to the same proxy) the system
 sender seems to receive Interleaved ACKs .
 I have no control on sender(and on receiver) system and in the log the
 ACKs come in to the correct sequence.
 In the Analytics profile the messages and relative ACK are paired
 correctly, but the sender receive a wrokg ACKs for some request.

 The proxy is in attachment

 My problem is know what IP and PORT is used by WSO2 Integrator to send
 back the ACKs for exclude an ESB problem.


 Thank in advance
 Marco

 *Marco Sessa*


 *Software Analyst / Developer*
 CSP S.p.A.
 Napoli - Centro Direzionale,
 isola G/1, scala C
 Tel: 081.191.38.607
 Cel: 340.8689247
 Email: marco.se...@cspnet.it
 www.cspnet.it


>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [WSO2 IS] Clarification on Claim Configuration in Service Provider

[Dilshani Subasinghe]

Hi All,

I am working on scenario 17 (Single Page Application (SPA) proxy) [1].

In this scenario, I configure SP with OAuth 2.0 authorization code grant.
So I try out claims configurations in SP side. While testing that, noticed
different behaviors in IS while requesting mandatory claims as follows;


​

Above screenshot also showing that only requesting one claim (department),
while it configured two mandatory claims in SP.

I need to clarify exact way of requesting claims. Is that going to handle
by IS or by web app? If it is going to handle by IS, it should show all
mandatory claims. We tried claim mapping in SP with Travelocity and it
works fine.
According to this scenario, I have to use Single Page Application [2].
Hence bit confuse about the functionality (Whether this is a limitation of
SPA or issue in IS).

Any help on this will be highly appreciated.

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
[2]
https://github.com/facilelogin/aratuwa/tree/master/oauth2.0-apps/org.wso2.carbon.identity.oauth.spa

Thanks.

-- 

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshani.me


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

Re: [Dev] API-Proxy for Single Page Application

[Cyril Rognon]

Hi all,

Indeed as Thilinda is saying it is completely distinct from APIM gateway
and it covers login/logout as well as api call.

It could be integrated into Identity Server : when you declare some SP then
it could parameter and deploy the server-side proxy

deploy site(s) and HA will have to be dealt with.

Since you mention login over Oauth I assulme you are considering
OpenIDConnect usage (from the proxy)?

Thanks
Cyril

2017-12-13 8:50 GMT+01:00 Thilina Madumal :

> Hi Youcef,
>
> This is not a replacement for APIM Gateway. APIM Gateway and this are two
> different things.
> This is an implementation of the security pattern no. 17 described in blog
> 1.
>
> [1] https://medium.facilelogin.com/thirty-solution-patterns-with-the-
> wso2-identity-server-16f9fd0c0389
>
> Regards,
> Thilina.
>
> On Tue, Dec 12, 2017 at 12:48 AM, Youcef HILEM 
> wrote:
>
>> Hi Thilina,
>>
>> Could you please explain why APIM Gateway is not suitable?
>> How to integrate this feature in WSO2 APIM?
>> In our distributed architecture, we already have enough components and
>> adding another seems inappropriate.
>>
>> Thanks
>> Youcef HILEM
>>
>>
>>
>> --
>> Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development
>> -f3.html
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> *Thilina Madumal*
> *Software Engineer | **WSO2*
> Email: thilina...@wso2.com
> Mobile: *+ <+94%2077%20767%201807>94 774553167*
> Web:  http://wso2.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

Re: [Dev] Error while configuring email notification in WSO2 DSS

[Piriya Sivalingam]

Hi Chanika,

I have already set it to true.


@ Dilusha
I tried as you mentioned and it works for me. I could receive the mail now.

Thank you.


On Wed, Dec 13, 2017 at 12:18 PM, Chanika Geeganage 
wrote:

> Since this is an authentication failure, this might be because of gmail
> account protection. To avoid that, you have to make your gmail account less
> secure. You can do that from following link
>
> https://www.google.com/settings/security/lesssecureapps
>
> On Wed, Dec 13, 2017 at 12:11 PM, Piriya Sivalingam 
> wrote:
>
>> Hi,
>>
>> I am trying to configure email notification scenario in WSO2 DSS. I have
>> generated a data service in DSS for exposing data in a database, and when a
>> request to that data service triggers an event the subscribers to that
>> event should receive an email notification. The use case is when I invoke
>> the data service the data should be added to the database and at the same
>> time the respective subscribers should receive a mail notification.
>>
>> The steps I followed are:
>>
>>- I configured the mailto transport sender in axis2_Client.xml file
>>located in /repository/conf/axis2 folder.
>>- In the insert query I added an event for identifying an
>>event_trigger used in the data service.
>>- I configured the Xpath accordingly for the response message, and
>>when this evaluation becomes true the event will be triggered.
>>- I configured the Event sink URL as well.
>>
>> When I invoke the service I found the following exception logged in the
>> console:
>>
>> ERROR {org.apache.axis2.transport.mail.MailTransportSender} -  Error
>> creating mail message or sending it to the configured server {
>> org.apache.axis2.transport.mail.MailTransportSender}
>> javax.mail.AuthenticationFailedException
>>
>> Can you please suggest whether there is anything wrong with my
>> configuration?
>> The document I referred is [1].
>>
>> [1] https://docs.wso2.com/display/DSS351/Receiving+Notificat
>> ions+from+Data+Services
>>
>> Thanks,
>> Piriya
>>
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> +94773522586 <+94%2077%20352%202586>
> WSO2, Inc.; http://wso2.com
>
>


-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev