Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Malaka Silva]

Hi Hasitha,

Sounds good. It'll be good if you can come up with the list of IBM specific
options.

On Tue, May 23, 2017 at 7:08 AM, Hasitha Jayasundara <
hasithajayasunda...@gmail.com> wrote:

> Hi all,
>
> I tried to implement sample MQ-Client that can connect to IBM MQ and we
> can improve that to implement inbound endpoint and the connector.Will improve
> that MQ-Client to support more ibm specific options such as SSL connections
> within next few days.
>
> On Fri, May 19, 2017 at 11:07 AM, Hasitha Jayasundara <
> hasithajayasunda...@gmail.com> wrote:
>
>> Hi all,
>>
>> Thanks for the replies.I'll go through the links and let you know if
>> there's any issue.
>>
>> On Fri, May 19, 2017 at 8:50 AM, Riyafa Abdul Hameed 
>> wrote:
>>
>>> Hi,
>>>
>>> See if this blog post could be of help:
>>> https://riyafa.wordpress.com/2016/02/21/sample-java-client-f
>>> or-websphere-mq-consumer-and-producer/
>>>
>>> Regards,
>>> Riyafa
>>>
>>> On Thu, May 18, 2017 at 9:13 PM, Malaka Silva  wrote:
>>>
 Hi Hasitha,

 You can find sample code done for IBM MQ 7.5. Here ESB acts as the
 consumer.

 What is required to do is ESB act as the consumer and producer for IBM
 MQ 8.0.

 Let me know if something is not clear?

 [1] https://github.com/wso2-attic/esb-connectors/pull/483/files

 On Tue, May 16, 2017 at 9:39 PM, Hasitha Jayasundara <
 hasithajayasunda...@gmail.com> wrote:

> Hi ayya,
>
> As we discussed today can you provide me some materials to get more
> familiar with IBM MQ 8.0?
>
> thanks
>
> --
> *D.M.Hasitha Nadishan Jayasundara*
> *Department of Electronic and Telecommunication Engineering*
> University of Moratuwa
> *mobile:* *+94711959266 <071%20195%209266>*
> *blogspot*: learnjavawithisla.blogspot.com/  *email:*
> hasithajayasunda...@gmail.com
> 
> 
> 
>



 --

 Best Regards,

 Malaka Silva
 Associate Director / Architect
 M: +94 777 219 791 <+94%2077%20721%209791>
 Tel : 94 11 214 5345
 Fax :94 11 2145300 <011%202%20145300>
 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/
 
 https://store.wso2.com/store/

 Don't make Trees rare, we should keep them with care

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


>>>
>>>
>>> --
>>> Riyafa Abdul Hameed
>>> Software Engineer, WSO2 Lanka (Pvt) Ltd 
>>>
>>> Email: riy...@wso2.com 
>>> Website: https://riyafa.wordpress.com/ 
>>>   
>>> 
>>>
>>
>>
>>
>> --
>> *D.M.Hasitha Nadishan Jayasundara*
>> *Department of Electronic and Telecommunication Engineering*
>> University of Moratuwa
>> *mobile:* *+94711959266 <+94%2071%20195%209266>*
>> *blogspot*: learnjavawithisla.blogspot.com/  *email:*
>> hasithajayasunda...@gmail.com
>> 
>> 
>> 
>>
>
>
>
> --
> *D.M.Hasitha Nadishan Jayasundara*
> *Department of Electronic and Telecommunication Engineering*
> University of Moratuwa
> *mobile:* *+94711959266 <+94%2071%20195%209266>*
> *blogspot*: learnjavawithisla.blogspot.com/  *email:* hasithajayasundara1@
> gmail.com
> 
> 
> 
>



-- 

Best Regards,

Malaka Silva
Associate Director / Architect
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/

https://store.wso2.com/store/

Don't make Trees rare, we should keep them with care
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Hasitha Jayasundara]

Hi all,

I tried to implement sample MQ-Client that can connect to IBM MQ and we can
improve that to implement inbound endpoint and the connector.Will improve
that MQ-Client to support more ibm specific options such as SSL connections
within next few days.

On Fri, May 19, 2017 at 11:07 AM, Hasitha Jayasundara <
hasithajayasunda...@gmail.com> wrote:

> Hi all,
>
> Thanks for the replies.I'll go through the links and let you know if
> there's any issue.
>
> On Fri, May 19, 2017 at 8:50 AM, Riyafa Abdul Hameed 
> wrote:
>
>> Hi,
>>
>> See if this blog post could be of help:
>> https://riyafa.wordpress.com/2016/02/21/sample-java-client-f
>> or-websphere-mq-consumer-and-producer/
>>
>> Regards,
>> Riyafa
>>
>> On Thu, May 18, 2017 at 9:13 PM, Malaka Silva  wrote:
>>
>>> Hi Hasitha,
>>>
>>> You can find sample code done for IBM MQ 7.5. Here ESB acts as the
>>> consumer.
>>>
>>> What is required to do is ESB act as the consumer and producer for IBM
>>> MQ 8.0.
>>>
>>> Let me know if something is not clear?
>>>
>>> [1] https://github.com/wso2-attic/esb-connectors/pull/483/files
>>>
>>> On Tue, May 16, 2017 at 9:39 PM, Hasitha Jayasundara <
>>> hasithajayasunda...@gmail.com> wrote:
>>>
 Hi ayya,

 As we discussed today can you provide me some materials to get more
 familiar with IBM MQ 8.0?

 thanks

 --
 *D.M.Hasitha Nadishan Jayasundara*
 *Department of Electronic and Telecommunication Engineering*
 University of Moratuwa
 *mobile:* *+94711959266 <071%20195%209266>*
 *blogspot*: learnjavawithisla.blogspot.com/  *email:*
 hasithajayasunda...@gmail.com
 
 
 

>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Associate Director / Architect
>>> M: +94 777 219 791 <+94%2077%20721%209791>
>>> 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/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Don't make Trees rare, we should keep them with care
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineer, WSO2 Lanka (Pvt) Ltd 
>>
>> Email: riy...@wso2.com 
>> Website: https://riyafa.wordpress.com/ 
>>   
>> 
>>
>
>
>
> --
> *D.M.Hasitha Nadishan Jayasundara*
> *Department of Electronic and Telecommunication Engineering*
> University of Moratuwa
> *mobile:* *+94711959266 <+94%2071%20195%209266>*
> *blogspot*: learnjavawithisla.blogspot.com/  *email:* hasithajayasundara1@
> gmail.com
> 
> 
> 
>



-- 
*D.M.Hasitha Nadishan Jayasundara*
*Department of Electronic and Telecommunication Engineering*
University of Moratuwa
*mobile:* *+94711959266 <+94%2071%20195%209266>*
*blogspot*: learnjavawithisla.blogspot.com/  *email:* hasithajayasundar
a...@gmail.com



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

[Dev] [IS] 6.0.0 roadmap

[Hanen Ben Rhouma]

Hello,

Could you please state the new features and bug fixes introduced within IS
6.0.0.m2

And what's coming within the major release and it's date please?

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

Re: [Dev] [DEV] [BPS] BPS 3.5.0. signals

[Lakshman Udayakantha]

On Mon, May 22, 2017 at 6:22 PM, Igor Golovko 
wrote:

> Thanks for a quick answer.
>
>
>
> We use BPS 3.5.0 because of kubernetes support. But as far as I know BPS
> 3.6.0 doesn’t support kubernetes.
>
> Do you plan to fix BPS 3.5.0. signals or maybe you plan add kubernetes
> support on 3.6.0 ?
>

How you build the kubernets artifacts?

Thanks,
Lakshman.

>
>
> Thanks,
>
> Igor Golovko
>
>
>
>
>
> *From:* Lakshman Udayakantha [mailto:lakshm...@wso2.com]
> *Sent:* Monday, May 22, 2017 3:11 PM
> *To:* Igor Golovko 
> *Cc:* dev@wso2.org; Hasitha Aravinda ; Amal Gunatilake <
> am...@wso2.com>; Vinod Kavinda ; Isuru Wijesinghe <
> isur...@ws02.com>; Milinda Perera 
> *Subject:* Re: [Dev] [DEV] [BPS] BPS 3.5.0. signals
>
>
>
> Hi Igor,
>
>
>
> You can migrate to the 3.6.0 by following migration doc [1] version since
> this issue is resolved there.
>
>
>
> [1] https://docs.wso2.com/display/BPS360/Upgrading+to+
> the+Latest+BPS+Version
>
>
>
> Thanks,
>
> Lakshman.
>
>
>
> On Mon, May 22, 2017 at 5:34 PM, Lakshman Udayakantha 
> wrote:
>
> [Adding BPS folks]
>
>
>
> On Mon, May 22, 2017 at 5:26 PM, Igor Golovko 
> wrote:
>
> Dear dev team, we have a problem with wso2 BPS 3.5.0.
>
> We have bps-process with signal boundary events.
>
> We try to activate request and when send request from rest api, this
> signal events didn’t activate.
>
> We send next request:
>
>
>
>
>
> Response:
>
> P.S In version 3.6.0 of WSO2 BPS, that works well.
>
>
>
> Best regards,
>
> Igor Golovko
>
>
>
>
> --
>
>
> This e-mail may contain privileged and confidential information. If you
> are not the intended recipient, be aware that any use, disclosure, copying
> or distribution of this e-mail or any attachments is prohibited. If you
> have received this e-mail in error, please notify us immediately by
> returning it to the sender and delete this copy from your system. Thank you.
>
>
> --
>
>
> This e-mail may contain privileged and confidential information. If you
> are not the intended recipient, be aware that any use, disclosure, copying
> or distribution of this e-mail or any attachments is prohibited. If you
> have received this e-mail in error, please notify us immediately by
> returning it to the sender and delete this copy from your system. Thank you.
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
>
> --
>
> Lakshman Udayakantha
>
> WSO2 Inc. www.wso2.com
>
> lean.enterprise.middleware
>
> Mobile: *0717429601*
>
>
>
>
>
>
>
> --
>
> Lakshman Udayakantha
>
> WSO2 Inc. www.wso2.com
>
> lean.enterprise.middleware
>
> Mobile: *0717429601*
>
>
>
> --
>
> This e-mail may contain privileged and confidential information. If you
> are not the intended recipient, be aware that any use, disclosure, copying
> or distribution of this e-mail or any attachments is prohibited. If you
> have received this e-mail in error, please notify us immediately by
> returning it to the sender and delete this copy from your system. Thank you.
>



-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM C5 - Exception handling inconsistencies

[Malintha Amarasinghe]

Hi,

On Mon, May 22, 2017 at 5:14 PM, Uvindra Dias Jayasinha 
wrote:

>
> Noticed a few inconsistencies when it comes to how we are doing exception
> handling in C5.
>
> *1. Logging the same exception in multiple places.*
>
> The practice of logging and throwing exception has been a long time
> practice at WSO2 but this is leading to cluttering of the logs.
>
> Quoting from the following Oracle blog[1] when it comes to logging and
> throwing,
>
> *"This is one of the most annoying error-handling antipatterns. Either log
> the exception, or throw it, but never do both. Logging and throwing results
> in multiple log messages for a single problem in the code, and makes life
> hell for the support engineer who is trying to dig through the logs."*
>
> Having experienced this first hand with our products this can lead to
> unwanted confusion. Since we are working with a single APIM code base it
> does not make sense to log and throw the same error up the call tree. I
> propose we only log the exception at the Microservice layer where we
> actually handle the exception in order to do the response mapping as
> follows.
>
I remeber there were some discussions about this before, few downsides are:

1. The Microservice layer becoming the only level of logging exceptions. If
someone forgots to log a particular exception, there are no backup
exception.
2. Even if we did this perfectly, someone else uses our components in osgi
level and does not log properly.

I understand that digging through duplicated logs are bit hard. But we know
if someone forgots logging the exception (since there is only one place,
the probability is high), it gives us a even more difficult situation.
Instead of completely avoiding it, shall we at least put a debug log with
the stack trace?


>

> catch (APIManagementException e) {
> String errorMessage = "Error while retrieving API : " + apiId;
> HashMap paramList = new HashMap();
> paramList.put(APIMgtConstants.ExceptionsConstants.API_ID, apiId);
> ErrorDTO errorDTO = RestApiUtil.getErrorDTO(e.getErrorHandler(),
> paramList);
> log.error(errorMessage, e);
> return Response.status(e.getErrorHandler().getHttpStatusCode()).
> entity(errorDTO).build();
> }
>
>
>
> *2. Destructive Exception Wrapping is done leading to the stack trace
> being swallowed*
>
> This also seems to be happening in our code base at certain places like
> shown below
>
> catch (APIMgtDAOException e) {
> String msg = "Error occurred while retrieving labels";
> log.error(msg, e);
> throw new LabelException(msg, ExceptionCodes.LABEL_EXCEPTION);
> }
>
>
> In this case the original stack trace which is part of the
> APIMgtDAOException is lost and not propagated along with the
> LabelException. I believe this incorrect practice has led to the adoption
> of the log and throw anti pattern. Correcting the above code as follows
> will allow for the complete stack trace to be printed when logging the
> exception at the Microservice layer
>
>
> catch (APIMgtDAOException e) {
> String msg = "Error occurred while retrieving labels";
> throw new LabelException(msg, e, ExceptionCodes.LABEL_EXCEPTION);
> }
>
> +1 we must propergate the original exception.

Thanks!
Malintha

>
> With the above proposal, anyone who uses the Impl layer of our Java code
> directly(instead of via the Microservice layer) will need to log exceptions
> as part of their exception handling logic. I don't see this as a problem
> since by throwing exceptions we are mandating that exception handling code
> has to be written.
>
>
> WDYT?
>
>
> [1] https://community.oracle.com/docs/DOC-983543#antipatterns
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

Mobile : +94 712383306 <+94%2071%20238%203306>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon] Clarifications about keystores in WSO2 Products

[Niranjan Karunanandham]

Hi Dilan,

On Mon, May 22, 2017 at 5:11 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Niranjan,
>
> On Mon, May 22, 2017 at 2:48 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Dilan,
>>
>> On Fri, May 5, 2017 at 7:15 PM, Dilan Udara Ariyaratne 
>> wrote:
>>
>>> Hi Folks,
>>>
>>> Following conceptions are still there regarding keystores used in WSO2
>>> products.
>>>
>>>1. Primary KeyStore must contain only one private key. There can not
>>>be two private keys. (This is due to some issue in WSO2 products which 
>>> may
>>>be fixed in future).
>>>2. Primary KeyStore must contain *same* password as KeyStore
>>>password and private key password. (This is due to some issue in WSO2
>>>products which may be fixed in future)
>>>
>>> Are these conceptions still valid or have these issues been already
>>> fixed ?
>>>
>>
>> In WSO2 Carbon there are multiple keystores. I believe the above keystore
>> that you have mentioned is only the Keystore [1] in carbon.xml. In 4.4.x,
>> this keystore is only used for secure vault only.
>>
>
> Aren't those secure vault configurations for keystores configured in 
> secret-conf.properties
> ?
>

This file is created by the cipher tool script file. It reads the
carbon.xml and creates this file. You can find info on these files in [1].


>
>
> As you have mentioned, in 4.4.x, if secure vault is enabled, then at the
>> server startup, it will ask for a single password which it uses for both
>> the Keystore and private key password.
>>
>
> In https://docs.wso2.com/display/ADMIN44x/Using+Asymmetric+Encryption, it
> says that "You must have the same password for both keystore and private
> key due to a Tomcat limitation"
> and therefore, it seems not because of secure vault.
>

I was referring to the limitation on the same password to be used at the
server started which uses the secure vault JKS which is used to decrypt the
passwords. With regard to this, you need to check the tomcat documentation
and verify this. Anyway here if we have separate JKS for secure vault and
tomcat ssl we can have separate passwords for both JKS. Any particular
reason as to why you need to have a separate keystore password and private
key password for SSL which is in an isolated JKS?


>
>
>> IMO since this is only for secure vault, we can have the same password.
>> In-addition AFAIK we can have multiple private key here. In 4.4.x, the JKS
>> for ssl has been moved to catalina-server.xml. Therefore a separate
>> keystore can be maintained for this. These two configuration are mentioned
>> in [2].
>>
>>> Thanks.
>>> *Dilan U. Ariyaratne*
>>> Senior Software Engineer
>>> WSO2 Inc. 
>>> Mobile: +94766405580 <%2B94766405580>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> [1] -
>> 
>> 
>> ${carbon.home}/repository/resources/security/wso2c
>> arbon.jks
>> 
>> JKS
>> 
>> wso2carbon
>> 
>> wso2carbon
>> 
>> wso2carbon
>> 
>>
>> [2] - https://docs.wso2.com/display/ADMIN44x/Configuring+Keystor
>> es+in+WSO2+Products
>>
>> Regards,
>> Nira
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>>
>
[1] -
https://docs.wso2.com/display/ADMIN44x/Carbon+Secure+Vault+Implementation

Regards,
Nira

-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [DAS] Error while passing the data through publishEvent mediator

[Chanuka Dissanayake]

>
>  xmlns:abc="urn:xyz.antz.com">
> 
>   
> 
>   UD_DAS


On Mon, May 22, 2017 at 5:41 PM, Gayan Yalpathwala  wrote:

> Please note that I was able to get through this by enabling sequential
> mediation in Iterate mediator.
>
> Thanks,
>
> On Mon, May 22, 2017 at 3:45 PM, Gayan Yalpathwala 
> wrote:
>
>> Hi team,
>>
>> I am getting an error similar to above, when PublishEvent mediator in the
>> target sequence of an Iterate mediator. ESB version is 5.0.0.
>> [2017-05-22 15:36:24,135] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'TestEventSink'. Error: Event sink
>> "TestEventSink" not found.
>>
>> I can see the following jira too: https://wso2.org/jira/browse/E
>> SBJAVA-4899.
>> Is there a possible solution or a workaround for this?
>>
>> Thanks,
>>
>>
>>
>> On Thu, Sep 10, 2015 at 5:03 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi Chanuka,
>>> It seems you haven't defined the event sink. Make sure you have defined
>>> one with the name eventSink14.
>>> Regards
>>>
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_6342050506033639433_m_-8717959336583478941_m_86378577479624110_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 
>>>
>>> On Thu, Sep 10, 2015 at 8:55 AM, Chanuka Dissanayake 
>>> wrote:
>>>
 Hi,

 I'm retrieving data set from Salesforce through ESB by using the
 Salesforce connector [1]. My intention is here to pass the data set to
 DAS as a payload. Therefore I used 'iterate' mediator [2] to iterate
 the data and inside that I used publishEvent mediator to pass the data
 to DAS as wso2events. But I'm getting this error [3] during the
 operation. First I created a Sample static data and pass it successfully to
 the DAS without getting the error and using the same 'EventSink'
 (which is 'eventSink14'). Proxy source [4]. What can be the possible error
 here?

 Additionally: Also when I update the PublishEvent stream Pay load
 attributes and trying to add a receiver from DAS, It is not
 identifying the newly added Pay Load attribute(s) (which may be a bug).
 Because of that it'll categorize as a inactive receiver [5]. Need to change
 the Stream name or the version of the Stream as a workaround.

 [1] https://docs.wso2.com/display/ESBCONNECTORS/Salesforce+Connector
 [2] https://docs.wso2.com/display/ESB480/Iterate+Mediator
 [3]

 2015-09-09 17:09:53,741] ERROR - PublishEventMediator Cannot mediate
 message. Failed to load event sink 'eventSink14'. Error: Event sink
 "eventSink14" not found

 [2015-09-09 17:09:53,741]  INFO - LogMediator To:
 http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
 , MessageID: urn:uuid:0877c7fb-3e22-41d3-83ab-629edc9b59e9, Direction:
 request, message = aa, Envelope: >>> encoding='utf-8'?>http://schemas.
 xmlsoap.org/soap/envelope/" ="urn:partner.soap.sforce.com">http://www.w3.org/2
 001/XMLSchema-instance" xsi:type="QueryResult">true<
 queryLocator xsi:nil="true"/>9>>> soapenv:Body>

 [2015-09-09 17:09:53,742] ERROR - PublishEventMediator Cannot mediate
 message. Failed to load event sink 'eventSink14'. Error: Event sink
 "eventSink14" not found

 [2015-09-09 17:09:53,743] ERROR - PublishEventMediator Cannot mediate
 message. Failed to load event sink 'eventSink14'. Error: Event sink
 "eventSink14" not found

 [2015-09-09 17:09:53,743]  INFO - LogMediator To:
 http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
 , MessageID: urn:uuid:e16bc0a2-586c-4aa7-9d34-f03773b09efb, Direction:
 request, message = aa, Envelope: >>> encoding='utf-8'?>http://schemas.
 xmlsoap.org/soap/envelope/" ="urn:partner.soap.sforce.com">http://www.w3.org/2
 001/XMLSchema-instance" xsi:type="QueryResult">true<
 queryLocator xsi:nil="true"/>9>>> soapenv:Body>

 [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
 message. Failed to load event sink 'eventSink14'. Error: Event sink
 "eventSink14" not found

 [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
 message. Failed to load event sink 'eventSink14'. Error: Event sink
 "eventSink14" not found

 [2015-09-09 17:09:53,746]  INFO - 

Re: [Dev] [Carbon] Clarifications about keystores in WSO2 Products

[Niranjan Karunanandham]

Hi Dilan,

On Mon, May 22, 2017 at 5:27 PM, Dilan Udara Ariyaratne 
wrote:

> And also there is a concept called encrypting registry data.
> Is this feature supported in carbon 4.4.x and if "YES", is this done via
> the keystore configured in carbon.xml ? I could not find proper
> documentation for this.
>
Can you explain about this please? Are you referring to data being
encrypted when added to the registry from the UI say password field. If so,
then this uses the secure vault.


> Thanks,
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Mon, May 22, 2017 at 5:11 PM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Niranjan,
>>
>> On Mon, May 22, 2017 at 2:48 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Dilan,
>>>
>>> On Fri, May 5, 2017 at 7:15 PM, Dilan Udara Ariyaratne 
>>> wrote:
>>>
 Hi Folks,

 Following conceptions are still there regarding keystores used in WSO2
 products.

1. Primary KeyStore must contain only one private key. There can
not be two private keys. (This is due to some issue in WSO2 products 
 which
may be fixed in future).
2. Primary KeyStore must contain *same* password as KeyStore
password and private key password. (This is due to some issue in WSO2
products which may be fixed in future)

 Are these conceptions still valid or have these issues been already
 fixed ?

>>>
>>> In WSO2 Carbon there are multiple keystores. I believe the above
>>> keystore that you have mentioned is only the Keystore [1] in carbon.xml. In
>>> 4.4.x, this keystore is only used for secure vault only.
>>>
>>
>> Aren't those secure vault configurations for keystores configured in 
>> secret-conf.properties
>> ?
>>
>> As you have mentioned, in 4.4.x, if secure vault is enabled, then at the
>>> server startup, it will ask for a single password which it uses for both
>>> the Keystore and private key password.
>>>
>>
>> In https://docs.wso2.com/display/ADMIN44x/Using+Asymmetric+Encryption,
>> it says that "You must have the same password for both keystore and
>> private key due to a Tomcat limitation"
>> and therefore, it seems not because of secure vault.
>>
>>
>>> IMO since this is only for secure vault, we can have the same password.
>>> In-addition AFAIK we can have multiple private key here. In 4.4.x, the JKS
>>> for ssl has been moved to catalina-server.xml. Therefore a separate
>>> keystore can be maintained for this. These two configuration are mentioned
>>> in [2].
>>>
 Thanks.
 *Dilan U. Ariyaratne*
 Senior Software Engineer
 WSO2 Inc. 
 Mobile: +94766405580 <%2B94766405580>
 lean . enterprise . middleware


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


>>> [1] -
>>> 
>>> 
>>> ${carbon.home}/repository/resources/security/wso2c
>>> arbon.jks
>>> 
>>> JKS
>>> 
>>> wso2carbon
>>> 
>>> wso2carbon
>>> 
>>> wso2carbon
>>> 
>>>
>>> [2] - https://docs.wso2.com/display/ADMIN44x/Configuring+Keystor
>>> es+in+WSO2+Products
>>>
>>> Regards,
>>> Nira
>>>
>>> --
>>>
>>>
>>> *Niranjan Karunanandham*
>>> Associate Technical Lead - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>>
>>
>


-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [BPS] BPS 3.5.0. signals

[Lakshman Udayakantha]

Hi Igor,

You can migrate to the 3.6.0 by following migration doc [1] version since
this issue is resolved there.

[1] https://docs.wso2.com/display/BPS360/Upgrading+to+the+Latest+BPS+Version

Thanks,
Lakshman.

On Mon, May 22, 2017 at 5:34 PM, Lakshman Udayakantha 
wrote:

> [Adding BPS folks]
>
> On Mon, May 22, 2017 at 5:26 PM, Igor Golovko 
> wrote:
>
>> Dear dev team, we have a problem with wso2 BPS 3.5.0.
>>
>> We have bps-process with signal boundary events.
>>
>> We try to activate request and when send request from rest api, this
>> signal events didn’t activate.
>>
>> We send next request:
>>
>>
>>
>>
>>
>> Response:
>>
>> P.S In version 3.6.0 of WSO2 BPS, that works well.
>>
>>
>>
>> Best regards,
>>
>> Igor Golovko
>>
>>
>>
>>
>> --
>>
>>
>> This e-mail may contain privileged and confidential information. If you
>> are not the intended recipient, be aware that any use, disclosure, copying
>> or distribution of this e-mail or any attachments is prohibited. If you
>> have received this e-mail in error, please notify us immediately by
>> returning it to the sender and delete this copy from your system. Thank you.
>>
>> --
>>
>> This e-mail may contain privileged and confidential information. If you
>> are not the intended recipient, be aware that any use, disclosure, copying
>> or distribution of this e-mail or any attachments is prohibited. If you
>> have received this e-mail in error, please notify us immediately by
>> returning it to the sender and delete this copy from your system. Thank you.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0717429601*
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [DAS] Error while passing the data through publishEvent mediator

[Gayan Yalpathwala]

Please note that I was able to get through this by enabling sequential
mediation in Iterate mediator.

Thanks,

On Mon, May 22, 2017 at 3:45 PM, Gayan Yalpathwala  wrote:

> Hi team,
>
> I am getting an error similar to above, when PublishEvent mediator in the
> target sequence of an Iterate mediator. ESB version is 5.0.0.
> [2017-05-22 15:36:24,135] ERROR - PublishEventMediator Cannot mediate
> message. Failed to load event sink 'TestEventSink'. Error: Event sink
> "TestEventSink" not found.
>
> I can see the following jira too: https://wso2.org/jira/browse/
> ESBJAVA-4899.
> Is there a possible solution or a workaround for this?
>
> Thanks,
>
>
>
> On Thu, Sep 10, 2015 at 5:03 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi Chanuka,
>> It seems you haven't defined the event sink. Make sure you have defined
>> one with the name eventSink14.
>> Regards
>>
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_-8717959336583478941_m_86378577479624110_>
>> 
>>   
>> 
>> Get a signature like this: Click here!
>> 
>>
>> On Thu, Sep 10, 2015 at 8:55 AM, Chanuka Dissanayake 
>> wrote:
>>
>>> Hi,
>>>
>>> I'm retrieving data set from Salesforce through ESB by using the
>>> Salesforce connector [1]. My intention is here to pass the data set to
>>> DAS as a payload. Therefore I used 'iterate' mediator [2] to iterate
>>> the data and inside that I used publishEvent mediator to pass the data
>>> to DAS as wso2events. But I'm getting this error [3] during the
>>> operation. First I created a Sample static data and pass it successfully to
>>> the DAS without getting the error and using the same 'EventSink' (which
>>> is 'eventSink14'). Proxy source [4]. What can be the possible error here?
>>>
>>> Additionally: Also when I update the PublishEvent stream Pay load
>>> attributes and trying to add a receiver from DAS, It is not identifying
>>> the newly added Pay Load attribute(s) (which may be a bug). Because of that
>>> it'll categorize as a inactive receiver [5]. Need to change the Stream name
>>> or the version of the Stream as a workaround.
>>>
>>> [1] https://docs.wso2.com/display/ESBCONNECTORS/Salesforce+Connector
>>> [2] https://docs.wso2.com/display/ESB480/Iterate+Mediator
>>> [3]
>>>
>>> 2015-09-09 17:09:53,741] ERROR - PublishEventMediator Cannot mediate
>>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>>> "eventSink14" not found
>>>
>>> [2015-09-09 17:09:53,741]  INFO - LogMediator To:
>>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>>> , MessageID: urn:uuid:0877c7fb-3e22-41d3-83ab-629edc9b59e9, Direction:
>>> request, message = aa, Envelope: >> encoding='utf-8'?>http://schemas.
>>> xmlsoap.org/soap/envelope/">>> ="urn:partner.soap.sforce.com">http://www.w3.org/2
>>> 001/XMLSchema-instance" xsi:type="QueryResult">true<
>>> queryLocator xsi:nil="true"/>9>> soapenv:Body>
>>>
>>> [2015-09-09 17:09:53,742] ERROR - PublishEventMediator Cannot mediate
>>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>>> "eventSink14" not found
>>>
>>> [2015-09-09 17:09:53,743] ERROR - PublishEventMediator Cannot mediate
>>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>>> "eventSink14" not found
>>>
>>> [2015-09-09 17:09:53,743]  INFO - LogMediator To:
>>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>>> , MessageID: urn:uuid:e16bc0a2-586c-4aa7-9d34-f03773b09efb, Direction:
>>> request, message = aa, Envelope: >> encoding='utf-8'?>http://schemas.
>>> xmlsoap.org/soap/envelope/">>> ="urn:partner.soap.sforce.com">http://www.w3.org/2
>>> 001/XMLSchema-instance" xsi:type="QueryResult">true<
>>> queryLocator xsi:nil="true"/>9>> soapenv:Body>
>>>
>>> [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
>>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>>> "eventSink14" not found
>>>
>>> [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
>>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>>> "eventSink14" not found
>>>
>>> [2015-09-09 17:09:53,746]  INFO - LogMediator To:
>>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>>> , MessageID: urn:uuid:08a723ab-9232-43db-ab66-be3feeac6fc1, Direction:
>>> request, message = aa, Envelope: >> encoding='utf-8'?>http://schemas.
>>> xmlsoap.org/soap/envelope/">>> 

Re: [Dev] [DEV] [BPS] BPS 3.5.0. signals

[Lakshman Udayakantha]

[Adding BPS folks]

On Mon, May 22, 2017 at 5:26 PM, Igor Golovko 
wrote:

> Dear dev team, we have a problem with wso2 BPS 3.5.0.
>
> We have bps-process with signal boundary events.
>
> We try to activate request and when send request from rest api, this
> signal events didn’t activate.
>
> We send next request:
>
>
>
>
>
> Response:
>
> P.S In version 3.6.0 of WSO2 BPS, that works well.
>
>
>
> Best regards,
>
> Igor Golovko
>
>
>
>
> --
>
>
> This e-mail may contain privileged and confidential information. If you
> are not the intended recipient, be aware that any use, disclosure, copying
> or distribution of this e-mail or any attachments is prohibited. If you
> have received this e-mail in error, please notify us immediately by
> returning it to the sender and delete this copy from your system. Thank you.
>
> --
>
> This e-mail may contain privileged and confidential information. If you
> are not the intended recipient, be aware that any use, disclosure, copying
> or distribution of this e-mail or any attachments is prohibited. If you
> have received this e-mail in error, please notify us immediately by
> returning it to the sender and delete this copy from your system. Thank you.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [BPS] BPS 3.5.0. signals

[Igor Golovko]

Dear dev team, we have a problem with wso2 BPS 3.5.0.
We have bps-process with signal boundary events.
We try to activate request and when send request from rest api, this signal 
events didn't activate.
We send next request:

[cid:image001.png@01D2CFE8.722F7200]

Response:
[cid:image002.jpg@01D2CFE8.722F7200]
P.S In version 3.6.0 of WSO2 BPS, that works well.

Best regards,
Igor Golovko




This e-mail may contain privileged and confidential information. If you are not 
the intended recipient, be aware that any use, disclosure, copying or 
distribution of this e-mail or any attachments is prohibited. If you have 
received this e-mail in error, please notify us immediately by returning it to 
the sender and delete this copy from your system. Thank you.



This e-mail may contain privileged and confidential information. If you are not 
the intended recipient, be aware that any use, disclosure, copying or 
distribution of this e-mail or any attachments is prohibited. If you have 
received this e-mail in error, please notify us immediately by returning it to 
the sender and delete this copy from your system. Thank you.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon] Clarifications about keystores in WSO2 Products

[Dilan Udara Ariyaratne]

And also there is a concept called encrypting registry data.
Is this feature supported in carbon 4.4.x and if "YES", is this done via
the keystore configured in carbon.xml ? I could not find proper
documentation for this.

Thanks,
Dilan.


*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Mon, May 22, 2017 at 5:11 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Niranjan,
>
> On Mon, May 22, 2017 at 2:48 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Dilan,
>>
>> On Fri, May 5, 2017 at 7:15 PM, Dilan Udara Ariyaratne 
>> wrote:
>>
>>> Hi Folks,
>>>
>>> Following conceptions are still there regarding keystores used in WSO2
>>> products.
>>>
>>>1. Primary KeyStore must contain only one private key. There can not
>>>be two private keys. (This is due to some issue in WSO2 products which 
>>> may
>>>be fixed in future).
>>>2. Primary KeyStore must contain *same* password as KeyStore
>>>password and private key password. (This is due to some issue in WSO2
>>>products which may be fixed in future)
>>>
>>> Are these conceptions still valid or have these issues been already
>>> fixed ?
>>>
>>
>> In WSO2 Carbon there are multiple keystores. I believe the above keystore
>> that you have mentioned is only the Keystore [1] in carbon.xml. In 4.4.x,
>> this keystore is only used for secure vault only.
>>
>
> Aren't those secure vault configurations for keystores configured in 
> secret-conf.properties
> ?
>
> As you have mentioned, in 4.4.x, if secure vault is enabled, then at the
>> server startup, it will ask for a single password which it uses for both
>> the Keystore and private key password.
>>
>
> In https://docs.wso2.com/display/ADMIN44x/Using+Asymmetric+Encryption, it
> says that "You must have the same password for both keystore and private
> key due to a Tomcat limitation"
> and therefore, it seems not because of secure vault.
>
>
>> IMO since this is only for secure vault, we can have the same password.
>> In-addition AFAIK we can have multiple private key here. In 4.4.x, the JKS
>> for ssl has been moved to catalina-server.xml. Therefore a separate
>> keystore can be maintained for this. These two configuration are mentioned
>> in [2].
>>
>>> Thanks.
>>> *Dilan U. Ariyaratne*
>>> Senior Software Engineer
>>> WSO2 Inc. 
>>> Mobile: +94766405580 <%2B94766405580>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> [1] -
>> 
>> 
>> ${carbon.home}/repository/resources/security/wso2c
>> arbon.jks
>> 
>> JKS
>> 
>> wso2carbon
>> 
>> wso2carbon
>> 
>> wso2carbon
>> 
>>
>> [2] - https://docs.wso2.com/display/ADMIN44x/Configuring+Keystor
>> es+in+WSO2+Products
>>
>> Regards,
>> Nira
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon] Clarifications about keystores in WSO2 Products

[Dilan Udara Ariyaratne]

Hi Niranjan,

On Mon, May 22, 2017 at 2:48 PM, Niranjan Karunanandham 
wrote:

> Hi Dilan,
>
> On Fri, May 5, 2017 at 7:15 PM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Folks,
>>
>> Following conceptions are still there regarding keystores used in WSO2
>> products.
>>
>>1. Primary KeyStore must contain only one private key. There can not
>>be two private keys. (This is due to some issue in WSO2 products which may
>>be fixed in future).
>>2. Primary KeyStore must contain *same* password as KeyStore password
>>and private key password. (This is due to some issue in WSO2 products 
>> which
>>may be fixed in future)
>>
>> Are these conceptions still valid or have these issues been already fixed
>> ?
>>
>
> In WSO2 Carbon there are multiple keystores. I believe the above keystore
> that you have mentioned is only the Keystore [1] in carbon.xml. In 4.4.x,
> this keystore is only used for secure vault only.
>

Aren't those secure vault configurations for keystores configured in
secret-conf.properties
?

As you have mentioned, in 4.4.x, if secure vault is enabled, then at the
> server startup, it will ask for a single password which it uses for both
> the Keystore and private key password.
>

In https://docs.wso2.com/display/ADMIN44x/Using+Asymmetric+Encryption, it
says that "You must have the same password for both keystore and private
key due to a Tomcat limitation"
and therefore, it seems not because of secure vault.


> IMO since this is only for secure vault, we can have the same password.
> In-addition AFAIK we can have multiple private key here. In 4.4.x, the JKS
> for ssl has been moved to catalina-server.xml. Therefore a separate
> keystore can be maintained for this. These two configuration are mentioned
> in [2].
>
>> Thanks.
>> *Dilan U. Ariyaratne*
>> Senior Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
> [1] -
> 
> 
> ${carbon.home}/repository/resources/security/
> wso2carbon.jks
> 
> JKS
> 
> wso2carbon
> 
> wso2carbon
> 
> wso2carbon
> 
>
> [2] - https://docs.wso2.com/display/ADMIN44x/Configuring+
> Keystores+in+WSO2+Products
>
> Regards,
> Nira
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC : OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Abilashini Thiyagarajah]

Yeah that would be great.

In the proposal, I have included the specifications of DCRM and the initial
design. So can we start from it and modify according to requirements.

For your reference,

Link to the proposal




*Thiyagarajah Abilashini*
Student
Department of Computer Science and Engineering
University of Moratuwa, Sri Lanka

On 22 May 2017 at 16:37, Pushpalanka Jayawardhana  wrote:

> Hi Abilashini,
>
> On Mon, May 22, 2017 at 4:25 PM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi Pushpalanka,
>>
>> Currently I am working on "Allow multiple locale-specific values for
>> redirect URI like human-readable values in the client meta data section"
>> in the issue https://wso2.org/jira/browse/IDENTITY-5879. Once I complete
>> this part, I will be able to send a pull request as I have fixed the other
>> parts of the specific issue.
>>
>> Yeah I can work on the DCRM specification as well as the DCR issue
>> fixing.
>>
> That's great! Thanks for the quick reply.
> Hope others will also agree that it will be good if we can prioritize DCRM
> implementation to be completed first, so that it can be tested for issues
> while others been fixed. WDYT?
>
>
>> Thanks,
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 22 May 2017 at 15:12, Pushpalanka Jayawardhana  wrote:
>>
>>> Hi Abilashini,
>>>
>>> Appreciate if you can give an update on the current progress of the
>>> project.
>>> Were you able to work on DCRM specification and other DCR stabilization
>>> issues.
>>>
>>> This is just to know the information for planning activities.
>>>
>>> Thanks,
>>>
>>> On Fri, May 5, 2017 at 11:01 AM, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:
>>>
 Yeah sure.

 Thank you

 *Thiyagarajah Abilashini*
 Student
 Department of Computer Science and Engineering
 University of Moratuwa, Sri Lanka

 On 5 May 2017 at 10:59, Ishara Karunarathna  wrote:

>
>
> On Fri, May 5, 2017 at 10:53 AM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Yeah we can have.
>>
> Then lets arrange a hangout from 2-3 pm
>
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 5 May 2017 at 10:25, Ishara Karunarathna  wrote:
>>
>>>
>>>
>>> On Fri, May 5, 2017 at 10:21 AM, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:
>>>
 Hi Ishara,

 Thank you.

 Tomorrow in the sense do you mean Saturday(6.4.2017)?

>>> Its today 5/5/2017 if you available we can have a meeting in the
>>> evening.
>>>
>>> -Ishara
>>>



 *Thiyagarajah Abilashini*
 Student
 Department of Computer Science and Engineering
 University of Moratuwa, Sri Lanka

 On 5 May 2017 at 00:51, Ishara Karunarathna 
 wrote:

> Hi,
>
> Congratz Abilashini,
>
> On Thu, May 4, 2017 at 11:42 PM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi all,
>>
>> Thank you so much for accepting my proposal and selecting me to
>> work on the project "*OAuth 2.0 Dynamic Client Registration
>> Management Protocol support for WSO2 Identity Server*" in GSOC
>> 2017. I am so happy to work on a WSO2 project after the internship.
>>
>> I would like to clarify the plan through out the program. Shall
>> we stick to my project plan in my proposal?
>>
> We may have to do some slight modification. Shall we arrange a
> meeting and discuss tomorrow. ?
>
> Thanks,
> Ishara
>
>>
>> Looking forward to have a fabulous project experience with WSO2
>> for next 4 months of period.
>>
>> Thankyou and best regards,
>> Abilashini
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>

Re: [Dev] GSOC : OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Pushpalanka Jayawardhana]

Hi Abilashini,

On Mon, May 22, 2017 at 4:25 PM, Abilashini Thiyagarajah <
abilashini...@cse.mrt.ac.lk> wrote:

> Hi Pushpalanka,
>
> Currently I am working on "Allow multiple locale-specific values for
> redirect URI like human-readable values in the client meta data section"
> in the issue https://wso2.org/jira/browse/IDENTITY-5879. Once I complete
> this part, I will be able to send a pull request as I have fixed the other
> parts of the specific issue.
>
> Yeah I can work on the DCRM specification as well as the DCR issue fixing.
>
That's great! Thanks for the quick reply.
Hope others will also agree that it will be good if we can prioritize DCRM
implementation to be completed first, so that it can be tested for issues
while others been fixed. WDYT?


> Thanks,
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 22 May 2017 at 15:12, Pushpalanka Jayawardhana  wrote:
>
>> Hi Abilashini,
>>
>> Appreciate if you can give an update on the current progress of the
>> project.
>> Were you able to work on DCRM specification and other DCR stabilization
>> issues.
>>
>> This is just to know the information for planning activities.
>>
>> Thanks,
>>
>> On Fri, May 5, 2017 at 11:01 AM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Yeah sure.
>>>
>>> Thank you
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 5 May 2017 at 10:59, Ishara Karunarathna  wrote:
>>>


 On Fri, May 5, 2017 at 10:53 AM, Abilashini Thiyagarajah <
 abilashini...@cse.mrt.ac.lk> wrote:

> Yeah we can have.
>
 Then lets arrange a hangout from 2-3 pm

>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 5 May 2017 at 10:25, Ishara Karunarathna  wrote:
>
>>
>>
>> On Fri, May 5, 2017 at 10:21 AM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Hi Ishara,
>>>
>>> Thank you.
>>>
>>> Tomorrow in the sense do you mean Saturday(6.4.2017)?
>>>
>> Its today 5/5/2017 if you available we can have a meeting in the
>> evening.
>>
>> -Ishara
>>
>>>
>>>
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 5 May 2017 at 00:51, Ishara Karunarathna 
>>> wrote:
>>>
 Hi,

 Congratz Abilashini,

 On Thu, May 4, 2017 at 11:42 PM, Abilashini Thiyagarajah <
 abilashini...@cse.mrt.ac.lk> wrote:

> Hi all,
>
> Thank you so much for accepting my proposal and selecting me to
> work on the project "*OAuth 2.0 Dynamic Client Registration
> Management Protocol support for WSO2 Identity Server*" in GSOC
> 2017. I am so happy to work on a WSO2 project after the internship.
>
> I would like to clarify the plan through out the program. Shall we
> stick to my project plan in my proposal?
>
 We may have to do some slight modification. Shall we arrange a
 meeting and discuss tomorrow. ?

 Thanks,
 Ishara

>
> Looking forward to have a fabulous project experience with WSO2
> for next 4 months of period.
>
> Thankyou and best regards,
> Abilashini
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 3 April 2017 at 20:15, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi Maduranga,
>>
>> I have already submitted the final proposal. I would like to
>> thank you for your guidance throughout the process of understanding 
>> the
>> project and preparing the proposal. Looking forward to work on the 
>> project.
>>
>> Best Regards,
>> Abilashini
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 3 April 2017 at 19:54, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Abishalani,
>>>
>>> I will not have time to go through your proposal now. As the
>>> deadline is getting closer, please go ahead and submit the proposal.
>>>
>>> Thanks,
>>>
>>> On Sun, Apr 2, 2017 at 10:12 PM, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:

Re: [Dev] GSOC : OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Abilashini Thiyagarajah]

Hi Pushpalanka,

Currently I am working on "Allow multiple locale-specific values for
redirect URI like human-readable values in the client meta data section" in
the issue https://wso2.org/jira/browse/IDENTITY-5879. Once I complete this
part, I will be able to send a pull request as I have fixed the other parts
of the specific issue.

Yeah I can work on the DCRM specification as well as the DCR issue fixing.

Thanks,

*Thiyagarajah Abilashini*
Student
Department of Computer Science and Engineering
University of Moratuwa, Sri Lanka

On 22 May 2017 at 15:12, Pushpalanka Jayawardhana  wrote:

> Hi Abilashini,
>
> Appreciate if you can give an update on the current progress of the
> project.
> Were you able to work on DCRM specification and other DCR stabilization
> issues.
>
> This is just to know the information for planning activities.
>
> Thanks,
>
> On Fri, May 5, 2017 at 11:01 AM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Yeah sure.
>>
>> Thank you
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 5 May 2017 at 10:59, Ishara Karunarathna  wrote:
>>
>>>
>>>
>>> On Fri, May 5, 2017 at 10:53 AM, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:
>>>
 Yeah we can have.

>>> Then lets arrange a hangout from 2-3 pm
>>>

 *Thiyagarajah Abilashini*
 Student
 Department of Computer Science and Engineering
 University of Moratuwa, Sri Lanka

 On 5 May 2017 at 10:25, Ishara Karunarathna  wrote:

>
>
> On Fri, May 5, 2017 at 10:21 AM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi Ishara,
>>
>> Thank you.
>>
>> Tomorrow in the sense do you mean Saturday(6.4.2017)?
>>
> Its today 5/5/2017 if you available we can have a meeting in the
> evening.
>
> -Ishara
>
>>
>>
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 5 May 2017 at 00:51, Ishara Karunarathna  wrote:
>>
>>> Hi,
>>>
>>> Congratz Abilashini,
>>>
>>> On Thu, May 4, 2017 at 11:42 PM, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:
>>>
 Hi all,

 Thank you so much for accepting my proposal and selecting me to
 work on the project "*OAuth 2.0 Dynamic Client Registration
 Management Protocol support for WSO2 Identity Server*" in GSOC
 2017. I am so happy to work on a WSO2 project after the internship.

 I would like to clarify the plan through out the program. Shall we
 stick to my project plan in my proposal?

>>> We may have to do some slight modification. Shall we arrange a
>>> meeting and discuss tomorrow. ?
>>>
>>> Thanks,
>>> Ishara
>>>

 Looking forward to have a fabulous project experience with WSO2 for
 next 4 months of period.

 Thankyou and best regards,
 Abilashini

 *Thiyagarajah Abilashini*
 Student
 Department of Computer Science and Engineering
 University of Moratuwa, Sri Lanka

 On 3 April 2017 at 20:15, Abilashini Thiyagarajah <
 abilashini...@cse.mrt.ac.lk> wrote:

> Hi Maduranga,
>
> I have already submitted the final proposal. I would like to thank
> you for your guidance throughout the process of understanding the 
> project
> and preparing the proposal. Looking forward to work on the project.
>
> Best Regards,
> Abilashini
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 3 April 2017 at 19:54, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Abishalani,
>>
>> I will not have time to go through your proposal now. As the
>> deadline is getting closer, please go ahead and submit the proposal.
>>
>> Thanks,
>>
>> On Sun, Apr 2, 2017 at 10:12 PM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have included the initial design in the proposal. I kindly
>>> request your feedback on it.
>>>
>>> Thank you,
>>> Abilashini
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 27 March 2017 at 21:14, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:

[Dev] Security using IS 5.3.0

[Melodias]

Hi
I would like add extra security using IS 5.3.0.

My first scenario is:
I'm in London and I'm login to my webApp using SSO IS 5.3.0. After 30
minutes someone login to my account from Beijing. It is not possible that it
was me, because 30 minutes before I was in London. Can IS send me an email,
that someone login to my account from Beijing?

My second scenario is:
to have trusted device. In first login I add my pc to trusted device. To add
device, IS will send on my mobile phone message with code i have to write,
to add trusted device. When I login to my account from other device, then IS
send me an email with message that someone loggin to my account from unknown
device, and to login I must have new code to add new device.

It is possible to do this scenarios using IS?

my regards



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Security-using-IS-5-3-0-tp149117.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Error codes in issuing access token

[Pushpalanka Jayawardhana]

Hi Nilasini,

Yes, your understanding is correct. We are not doing scope validations in
IS as of now.
There is a separate scope validator that get engaged in the scenarios
relevant with APIM as of [1], which does scope validation.

[1] - https://github.com/wso2-extensions/identity-inbound-
auth-oauth/blob/master/components/org.wso2.carbon.
identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/validators/
JDBCScopeValidator.java

Thanks,

On Mon, May 22, 2017 at 3:28 PM, Nilasini Thirunavukkarasu <
nilas...@wso2.com> wrote:

>
>
> On Mon, May 22, 2017 at 2:55 PM, Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi,
>> According to the specification[1] invalid_scope error code must be shown
>> when we give invalid scope, unknown scope and etc. As we need to support
>> custom scope as well, so we can't have a predefined list of scopes. From
>> the current implementation it doesn't prompt the error code.
>>
>> As shown in [2], the scope is always set to true. So as far as I can
>> understand it's not validating the scope in a correct manner. Any insight
>> on this will be highly appreciated.
>>
>> [1] https://tools.ietf.org/html/rfc6749#section-5.2
>> [2]https://github.com/wso2-extensions/identity-inbound-auth-
>> oauth/blob/master/components/org.wso2.carbon.identity.oauth/
>> src/main/java/org/wso2/carbon/identity/oauth/callback/
>> DefaultCallbackHandler.java#L37
>>
>> Thank you,
>> Nila.
>>
>> --
>> Nilasini Thirunavukkarasu
>> Software Engineer - WSO2
>>
>> Email : nilas...@wso2.com
>> Mobile : +94775241823 <+94%2077%20524%201823>
>> Web : http://wso2.com/
>>
>>
>> 
>>
>
>
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823 <077%20524%201823>
> Web : http://wso2.com/
>
>
> 
>



-- 
Pushpalanka.
-- 
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/
pushpalanka/ | Twitter: @pushpalanka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [DAS] Error while passing the data through publishEvent mediator

[Gayan Yalpathwala]

Hi team,

I am getting an error similar to above, when PublishEvent mediator in the
target sequence of an Iterate mediator. ESB version is 5.0.0.
[2017-05-22 15:36:24,135] ERROR - PublishEventMediator Cannot mediate
message. Failed to load event sink 'TestEventSink'. Error: Event sink
"TestEventSink" not found.

I can see the following jira too: https://wso2.org/jira/browse/ESBJAVA-4899.
Is there a possible solution or a workaround for this?

Thanks,



On Thu, Sep 10, 2015 at 5:03 PM, Nadeeshaan Gunasinghe 
wrote:

> Hi Chanuka,
> It seems you haven't defined the event sink. Make sure you have defined
> one with the name eventSink14.
> Regards
>
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_86378577479624110_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>
> On Thu, Sep 10, 2015 at 8:55 AM, Chanuka Dissanayake 
> wrote:
>
>> Hi,
>>
>> I'm retrieving data set from Salesforce through ESB by using the
>> Salesforce connector [1]. My intention is here to pass the data set to
>> DAS as a payload. Therefore I used 'iterate' mediator [2] to iterate the
>> data and inside that I used publishEvent mediator to pass the data to DAS
>> as wso2events. But I'm getting this error [3] during the operation. First I
>> created a Sample static data and pass it successfully to the DAS without
>> getting the error and using the same 'EventSink' (which is 'eventSink14').
>> Proxy source [4]. What can be the possible error here?
>>
>> Additionally: Also when I update the PublishEvent stream Pay load
>> attributes and trying to add a receiver from DAS, It is not identifying
>> the newly added Pay Load attribute(s) (which may be a bug). Because of that
>> it'll categorize as a inactive receiver [5]. Need to change the Stream name
>> or the version of the Stream as a workaround.
>>
>> [1] https://docs.wso2.com/display/ESBCONNECTORS/Salesforce+Connector
>> [2] https://docs.wso2.com/display/ESB480/Iterate+Mediator
>> [3]
>>
>> 2015-09-09 17:09:53,741] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>> "eventSink14" not found
>>
>> [2015-09-09 17:09:53,741]  INFO - LogMediator To:
>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>> , MessageID: urn:uuid:0877c7fb-3e22-41d3-83ab-629edc9b59e9, Direction:
>> request, message = aa, Envelope: > encoding='utf-8'?>http://schemas.xmlsoap
>> .org/soap/envelope/">> ="urn:partner.soap.sforce.com">http://www.w3.org/2001/
>> XMLSchema-instance" xsi:type="QueryResult">true> xsi:nil="true"/>9> soapenv:Envelope>
>>
>> [2015-09-09 17:09:53,742] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>> "eventSink14" not found
>>
>> [2015-09-09 17:09:53,743] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>> "eventSink14" not found
>>
>> [2015-09-09 17:09:53,743]  INFO - LogMediator To:
>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>> , MessageID: urn:uuid:e16bc0a2-586c-4aa7-9d34-f03773b09efb, Direction:
>> request, message = aa, Envelope: > encoding='utf-8'?>http://schemas.xmlsoap
>> .org/soap/envelope/">> ="urn:partner.soap.sforce.com">http://www.w3.org/2001/
>> XMLSchema-instance" xsi:type="QueryResult">true> xsi:nil="true"/>9> soapenv:Envelope>
>>
>> [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>> "eventSink14" not found
>>
>> [2015-09-09 17:09:53,744] ERROR - PublishEventMediator Cannot mediate
>> message. Failed to load event sink 'eventSink14'. Error: Event sink
>> "eventSink14" not found
>>
>> [2015-09-09 17:09:53,746]  INFO - LogMediator To:
>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>> , MessageID: urn:uuid:08a723ab-9232-43db-ab66-be3feeac6fc1, Direction:
>> request, message = aa, Envelope: > encoding='utf-8'?>http://schemas.xmlsoap
>> .org/soap/envelope/">> ="urn:partner.soap.sforce.com">http://www.w3.org/2001/
>> XMLSchema-instance" xsi:type="QueryResult">true> xsi:nil="true"/>9> soapenv:Envelope>
>>
>> [4]
>>
>> 
>> http://ws.apache.org/ns/synapse;
>>name="esbtoBamProxyEvent"
>>transports="https,http"
>>statistics="disable"
>>trace="disable"
>>startOnLoad="true">
>>
>>   

[Dev] [Carbon][APIM] Unserialisable http session fails session replication

[Chamara Philips]

Hi all,

As explained in the thread "[CARBON][APIM] Replicating sessions in a API
manager cluster", we did a testing with sharing sessions in a cluster using
CarbonTomcatSessionReplicationValve [1]. For publisher and store worked as
expected.

But for the keymanager node, it didn't work as expected. The root cause for
blocking the approaches described in the above thread and http-session
replication is that the http-session we have in carbon is not serializable.
The session has three objects which are not serializable.

1. org.wso2.carbon.ui.DefaultCarbonAuthenticator
2. org.wso2.carbon.ui.MenuAdminClient
3. org.wso2.carbon.registry.core.session.UserRegistry

I serialized DefaultCarbonAuthenticator, MenuAdminClient with a patch.
But the object tree in the UserRegistry instance under the key "
WSO2RegistryRoot" in the http-session is simply hard to manage by patching.
I tried to do that but it ends up patching 5 components.

1. org.wso2.carbon.ndatasource.rdbms
2. org.wso2.carbon.registry.core
3. org.wso2.carbon.registry.search
4. org.wso2.carbon.ui
5. org.wso2.carbon.user.core

AFAIK, it is a bad practice to keep unserializable objects in the session.
We could use something like Redis session sharing

[2]
if the session was serializable. This could also solve the problem in
depending on the stickiness of load balancers in a clustering environment.
( Additionally, performance issues in using the
CarbonTomcatSessionReplicationValve in stores and publishers could have
been easily solved using the same kind of approach)

Shouldn't we design the session in a serializable manner? What are the
limitations doing so?

[1] https://docs.wso2.com/display/CLUSTER420/Enabling+
HTTP+Session+Replication
[2]
https://discuss.pivotal.io/hc/en-us/articles/206085337-How-to-setup-Redis-Session-Manager-on-tcServer-Tomcat

Thanks & Regards

-- 
-- 
Hareendra Chamara (BSc.Eng(Hons))
Sysco acceleration,
SyscoLabs(Pvt) Ltd
Mobile : +94 (0) 767 184161 <94767184161> | +65 (9) 425 2874 <6594252874>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Error codes in issuing access token

[Nilasini Thirunavukkarasu]

On Mon, May 22, 2017 at 2:55 PM, Nilasini Thirunavukkarasu <
nilas...@wso2.com> wrote:

> Hi,
> According to the specification[1] invalid_scope error code must be shown
> when we give invalid scope, unknown scope and etc. As we need to support
> custom scope as well, so we can't have a predefined list of scopes. From
> the current implementation it doesn't prompt the error code.
>
> As shown in [2], the scope is always set to true. So as far as I can
> understand it's not validating the scope in a correct manner. Any insight
> on this will be highly appreciated.
>
> [1] https://tools.ietf.org/html/rfc6749#section-5.2
> [2]https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/master/components/org.wso2.carbon.
> identity.oauth/src/main/java/org/wso2/carbon/identity/oauth/callback/
> DefaultCallbackHandler.java#L37
>
> Thank you,
> Nila.
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823 <+94%2077%20524%201823>
> Web : http://wso2.com/
>
>
> 
>



-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



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

[Dev] Adding Transacted Samplers for performance testing in MB 4 using Jmeter

[Sudharma Subasinghe]

Hi,

The purpose was to enabling performance testing for local transactions and
distributed transactions in MB 4 using Jmeter.

As latest Jmeter version does not provide that feature, I have created
sender and receiver samplers for queues as Jmeter java request samplers
[1]. This has used same queueSession with each thread in threadGruop.
(regardless loopcount for each thread in Jmeter).

[1]  https://github.com/wso2/carbon-business-messaging/pull/453/

Thanks
Sudharma

-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC : OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Pushpalanka Jayawardhana]

Hi Abilashini,

Appreciate if you can give an update on the current progress of the project.
Were you able to work on DCRM specification and other DCR stabilization
issues.

This is just to know the information for planning activities.

Thanks,

On Fri, May 5, 2017 at 11:01 AM, Abilashini Thiyagarajah <
abilashini...@cse.mrt.ac.lk> wrote:

> Yeah sure.
>
> Thank you
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 5 May 2017 at 10:59, Ishara Karunarathna  wrote:
>
>>
>>
>> On Fri, May 5, 2017 at 10:53 AM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Yeah we can have.
>>>
>> Then lets arrange a hangout from 2-3 pm
>>
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 5 May 2017 at 10:25, Ishara Karunarathna  wrote:
>>>


 On Fri, May 5, 2017 at 10:21 AM, Abilashini Thiyagarajah <
 abilashini...@cse.mrt.ac.lk> wrote:

> Hi Ishara,
>
> Thank you.
>
> Tomorrow in the sense do you mean Saturday(6.4.2017)?
>
 Its today 5/5/2017 if you available we can have a meeting in the
 evening.

 -Ishara

>
>
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>
> On 5 May 2017 at 00:51, Ishara Karunarathna  wrote:
>
>> Hi,
>>
>> Congratz Abilashini,
>>
>> On Thu, May 4, 2017 at 11:42 PM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Hi all,
>>>
>>> Thank you so much for accepting my proposal and selecting me to work
>>> on the project "*OAuth 2.0 Dynamic Client Registration Management
>>> Protocol support for WSO2 Identity Server*" in GSOC 2017. I am so
>>> happy to work on a WSO2 project after the internship.
>>>
>>> I would like to clarify the plan through out the program. Shall we
>>> stick to my project plan in my proposal?
>>>
>> We may have to do some slight modification. Shall we arrange a
>> meeting and discuss tomorrow. ?
>>
>> Thanks,
>> Ishara
>>
>>>
>>> Looking forward to have a fabulous project experience with WSO2 for
>>> next 4 months of period.
>>>
>>> Thankyou and best regards,
>>> Abilashini
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 3 April 2017 at 20:15, Abilashini Thiyagarajah <
>>> abilashini...@cse.mrt.ac.lk> wrote:
>>>
 Hi Maduranga,

 I have already submitted the final proposal. I would like to thank
 you for your guidance throughout the process of understanding the 
 project
 and preparing the proposal. Looking forward to work on the project.

 Best Regards,
 Abilashini

 *Thiyagarajah Abilashini*
 Student
 Department of Computer Science and Engineering
 University of Moratuwa, Sri Lanka

 On 3 April 2017 at 19:54, Maduranga Siriwardena  wrote:

> Hi Abishalani,
>
> I will not have time to go through your proposal now. As the
> deadline is getting closer, please go ahead and submit the proposal.
>
> Thanks,
>
> On Sun, Apr 2, 2017 at 10:12 PM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi Maduranga,
>>
>> I have included the initial design in the proposal. I kindly
>> request your feedback on it.
>>
>> Thank you,
>> Abilashini
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>> On 27 March 2017 at 21:14, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Hi Maduranga,
>>>
>>> Sorry for the inconvenience occurred with the wrong link.
>>>
>>> Thank you for your comments and I am updating the proposal
>>> respectively. Also I have replied to some of the comments for
>>> clarification. It would be so helpful if I get your comment on 
>>> those.
>>>
>>> I will include the initial design and the the fixed jira issues
>>> as soon as possible.
>>>
>>> Thanks,
>>> Abilashini
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>> On 27 March 2017 at 20:07, 

[Dev] [IS] Error codes in issuing access token

[Nilasini Thirunavukkarasu]

Hi,
According to the specification[1] invalid_scope error code must be shown
when we give invalid scope, unknown scope and etc. As we need to support
custom scope as well, so we can't have a predefined list of scopes. From
the current implementation it doesn't prompt the error code.

As shown in [2], the scope is always set to true. So as far as I can
understand it's not validating the scope in a correct manner. Any insight
on this will be highly appreciated.

[1] https://tools.ietf.org/html/rfc6749#section-5.2
[2]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth/callback/DefaultCallbackHandler.java#L37

Thank you,
Nila.

-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



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

Re: [Dev] [Carbon] Clarifications about keystores in WSO2 Products

[Niranjan Karunanandham]

Hi Dilan,

On Fri, May 5, 2017 at 7:15 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Folks,
>
> Following conceptions are still there regarding keystores used in WSO2
> products.
>
>1. Primary KeyStore must contain only one private key. There can not
>be two private keys. (This is due to some issue in WSO2 products which may
>be fixed in future).
>2. Primary KeyStore must contain *same* password as KeyStore password
>and private key password. (This is due to some issue in WSO2 products which
>may be fixed in future)
>
> Are these conceptions still valid or have these issues been already fixed ?
>

In WSO2 Carbon there are multiple keystores. I believe the above keystore
that you have mentioned is only the Keystore [1] in carbon.xml. In 4.4.x,
this keystore is only used for secure vault only. As you have mentioned, in
4.4.x, if secure vault is enabled, then at the server startup, it will ask
for a single password which it uses for both the Keystore and private key
password. IMO since this is only for secure vault, we can have the same
password. In-addition AFAIK we can have multiple private key here. In
4.4.x, the JKS for ssl has been moved to catalina-server.xml. Therefore a
separate keystore can be maintained for this. These two configuration are
mentioned in [2].



> Thanks.
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
[1] -



${carbon.home}/repository/resources/security/wso2carbon.jks

JKS

wso2carbon

wso2carbon

wso2carbon


[2] -
https://docs.wso2.com/display/ADMIN44x/Configuring+Keystores+in+WSO2+Products

Regards,
Nira

-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [carbon-jndi] Name not bound to Context exception for rmi in NamingContext

[Asma Jabir]

Hi,

When trying to bind rmi for JMXConnectorServer with carbon-jndi a
*javax.naming.NameNotFoundException:
Name [rmi://127.0.0.1:/jmxrmi ] is not
bound in this Context. Unable to find [rmi:]* throws.

This is thrown by the org.wso2.carbon.jndi.internal.impl.NamingContext  from
the method
 protected void bind(Name name, Object obj, boolean rebind) throws
NamingException {}

after execution of line

NamingEntry entry = (NamingEntry)this.bindings.get(name.get(0));

This is because the if(name.size() > 1) is true and subsequently  if(entry
== null) also becomes true since the binding aren't put to the bindings map
yet [1].

Ideally, shouldn't it be that if the entry is null, the object is wrapped
with a new NamingEntry [2] ?

[1]
 
https://github.com/wso2/carbon-jndi/blob/v1.0.2/components/org.wso2.carbon.jndi/src/main/java/org/wso2/carbon/jndi/internal/impl/NamingContext.java#L818

[2]
https://github.com/wso2/carbon-jndi/blob/v1.0.2/components/org.wso2.carbon.jndi/src/main/java/org/wso2/carbon/jndi/internal/impl/NamingContext.java#L833


Thank you

Regards,
Asma

-- 
Asma Zinneera Jabir
Software Engineer
WSO2 Inc: http://wso2.com/
Contact No: +94 77 332 4752
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [WSO2-IoTS] What is correct tag or branch of cdmf-agent-android for use with v3.0.0

[Lakshman Udayakantha]

Hi Clovis,

According to the compatibility doc [1], IOT 3.0.0 should work with agent
2.0.0 version. Could you check the tag and build and see? Anyway, can you
see any error in log (server log or logcat)?

[1]
https://docs.wso2.com/display/IoTS300/WSO2+IoT+Server+and+Agent+Compatibility

Thanks,
Lakshman.

On Sun, May 21, 2017 at 7:41 PM, Clovis Wichoski 
wrote:

>
> Hi,
>
> I'm try to configure and test with Sansung Tablet SM-T560 that uses
> Android Kitkat 4.4.4, when I try the application on emulator with same
> version all works fine, but when use with physical device dont get
> enrollment, I'm compiling the sources from git on branch release-2.0.0 (as
> I see that some changes in APIs dont worked with new branches) that work
> with version 3.0.0 of WSO2 IoTS.
>
> Can be any specific issue with physical devices that differ from emulator?
> Any clue? Maybe using another branch or tag?
>
> Best regards
>
> Clóvis
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Vulnerabilities detected through Dependency Check

[Lakshman Udayakantha]

Hi Hanen,

You can go through the security advisory docs[1] and apply the patches
given. These fixes may be already available in these patches.

[1] https://docs.wso2.com/display/Security/Security+Advisories

Thanks,
Lakshman

On Mon, May 22, 2017 at 1:28 PM, Hanen Ben Rhouma 
wrote:

> Hello guys,
>
> I scanned WSO2 IS with Dependency Check 1.4.5 and the report shows many
> vulnerabilities, I raised a Jira
>  for this concern, could you
> please let me know if there is any upcoming actions like dependencies
> version upgrade or libraries stack change. It's important to validate the
> security level for IS in order to fully adopt the solution and sign a
> support contract.
>
>
> Regards,
> Hanen
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] Vulnerabilities detected through Dependency Check

[Hanen Ben Rhouma]

Hello guys,

I scanned WSO2 IS with Dependency Check 1.4.5 and the report shows many
vulnerabilities, I raised a Jira
 for this concern, could you
please let me know if there is any upcoming actions like dependencies
version upgrade or libraries stack change. It's important to validate the
security level for IS in order to fully adopt the solution and sign a
support contract.


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

[Dev] BPS 3.5.0. signals

[Illia Alifanov]

Dear dev team, we have a problem with wso2 BPS 3.5.0.
We have bps-process with signal boundary events.
We try to activate request and when send request from rest api, this signal 
events didn't activate.
We send next request:

[cid:image001.png@01D2CFE8.722F7200]

Response:
[cid:image002.jpg@01D2CFE8.722F7200]
P.S In version 3.6.0 of WSO2 BPS, that works well.

Best regards,
Illia.




This e-mail may contain privileged and confidential information. If you are not 
the intended recipient, be aware that any use, disclosure, copying or 
distribution of this e-mail or any attachments is prohibited. If you have 
received this e-mail in error, please notify us immediately by returning it to 
the sender and delete this copy from your system. Thank you.



This e-mail may contain privileged and confidential information. If you are not 
the intended recipient, be aware that any use, disclosure, copying or 
distribution of this e-mail or any attachments is prohibited. If you have 
received this e-mail in error, please notify us immediately by returning it to 
the sender and delete this copy from your system. Thank you.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC][CEP][DEV] Python API for Siddhi CEP

[Grainier Perera]

Hi Madhawa,

I went through your impl and it works great. Try to improve the test cases
and documentation (README.md on git) when you get a time.

Furthermore, I have added Event simulator REST API endpoints to the doc
that you shared earlier. After getting debugger to work, try to wrap event
simulator endpoints as well. You can refer to [1] for the documentation on
them.

[1] https://docs.wso2.com/display/DAS400/Simulating+Events

Regards,
Grainier.

On Sun, May 21, 2017 at 6:00 PM, Madhawa Vidanapathirana <
madhawavidanapathir...@gmail.com> wrote:

> Hi,
>
> I started working on the native wrapper. So far, have the very basic
> functionality working for Siddhi 3.1 and Siddhi 4.0.
> I am maintaining my code at the repo [1].
>
> Next step is getting the Siddhi debugger working. I will let you know when
> it is done.
>
> [1] - https://github.com/madhawav/SiddhiCEPPythonAPI
>
> Thanks,
> Madhawa
>
>
> On Fri, May 19, 2017 at 12:47 PM, Sriskandarajah Suhothayan  > wrote:
>
>> Sure we'll look into that.
>>
>> As the immediate next step can you make finish the work on native Siddhi
>> working with python.
>> Make sure Siddhi debugger also works.
>>
>> Regards
>> Suho
>>
>> On Fri, May 19, 2017 at 11:45 AM, Madhawa Vidanapathirana <
>> madhawavidanapathir...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have updated the shared doc [1] by adding "List of Admin Services to
>>> be used for DAS 3.1". Feel free to add-in your suggestions as well.
>>>
>>> Also, are their any documentation available on specific Admin Services
>>> APIs I have mentioned in doc? Such as a Reference Guide describing the
>>> methods and parameters of individual Admin Services APIs. I am already
>>> aware of the general documentation on Admin Services available at [2]
>>>
>>> [1] - https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt
>>> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing
>>> [2] - https://docs.wso2.com/display/DAS310/Calling+Admin+Services+
>>> from+Apps
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Tue, May 9, 2017 at 11:11 AM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>
 +1 for the approach.
 We will add the classes

 On Tue, May 9, 2017 at 12:05 AM Madhawa Vidanapathirana <
 madhawavidanapathir...@gmail.com> wrote:

> Hi,
>
> I will look into REST side also then. Already found good APIs to work
> with Native Calls and SOAP.
>
> I am also trying to come up with a list of classes of Siddhi Java
> Library that should be exposed via Python API.  I don't think its required
> to wrap the internal classes since their functionality is not directly 
> used
> by Siddhi Java Library users.
>
> I will update the list of classes to be wrapped at link below. Feel
> free to add in your suggestions as well.
> https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt
> 2JHh9RJya2VdHlHOTl4/edit?usp=sharing
>
> Thanks and Regards,
> Madhawa
>
>
> On Sun, May 7, 2017 at 11:26 PM, Sriskandarajah Suhothayan <
> s...@wso2.com> wrote:
>
>> Siddhi 3.x is compatible with DAS 3.1, and Siddhi 4.x is
>> compatible with DAS 4.0 which we are still working on.
>>
>> Siddhi APIs does not drastically change from 3.x to 4.x,
>> DAS 3.1 uses SOAP and DAS 4.0 uses HTTP/REST APIs
>>
>> So apart from native APIs, if you have figured out a way to use REST
>> and SOAP we are good enough.
>>
>> Regards
>> Suho
>>
>> On Sun, May 7, 2017 at 12:00 PM, Madhawa Vidanapathirana <
>> madhawavidanapathir...@gmail.com> wrote:
>>
>>> Hi,
>>> Need bit more clarity on what versions of products we should build
>>> on.
>>>
>>> Are we developing on DAS 3.1 (as mentioned in beginning of mail
>>> thread) or 4.0 (mentioned in previous mail) ?
>>> Also, what version of WSO2 CEP?
>>>
>>> According to my understanding so far, we are developing on Siddhi
>>> Java Library 4.0.
>>>
>>> Thanks and Regards,
>>> Madhawa
>>>
>>> On Sat, May 6, 2017 at 1:27 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>


 On Sat, May 6, 2017 at 9:06 AM, Sriskandarajah Suhothayan <
 s...@wso2.com> wrote:

> @Mohan on DAS 4.0 do we have similar services like admin services
> at the worker?
>
> Shall we come up with the exact list of apis that we need to have
> ? So he can also incorporate them.
>

 Yes, I have already listed some apis in [1].. Will get the
 finalized list soon and share with Madhawa..

 [1] https://docs.google.com/spreadsheets/d/1m0sh4DLABCFzCBmj
 EXtVTrRGM0Mc6lvyYQP6rI99zhQ/edit#gid=0

 Thanks,
 Mohan


>
> Regards
> Suho
>
> On Fri, May 5, 2017 at 9:16 PM Mohanadarshan Vivekanandalingam <
>