[Dev] [Announce] [Architecture] WSO2 Enterprise Integrator 6.1.1-update19 Released !

[Milan Perera]

Hi All,

The WSO2 Integration team is pleased to announce the release of Enterprise
Integrator 6.1.1-update19.

It is available for download from here


*Tasks/Bug Fixes and Improvements*

   - https://github.com/wso2/product-ei/milestone/27?closed=1
   - https://wso2.org/jira/browse/ESBJAVA-5290?filter=14515


*​​List of Open Issues*

   - https://wso2.org/jira/browse/ESBJAVA-5283?filter=13994
   - https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue


*Documentation*

   - https://docs.wso2.com/display/EI611/WSO2+Enterprise+Integrat
   or+Documentation


*How To Contribute*

Your feedback is most welcome!

*Reporting Issues​*

We encourage you to report issues, improvements and feature requests
regarding WSO2 Integrator through WSO2 EI GIT Issues
.

*Mailing Lists*

Join our mailing lists and correspond with the developers directly.

Developer List : dev@wso2.org | Subscribe | Mail Archive

WSO2 Architecture List: architect...@wso2.org

User Forum : StackOverflow 


~ The WSO2 Integration Team ~


-- 
*Milan Perera *| Senior Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com


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

[Dev] Error when provisioning users with the SCIM API.

[Menaka Jayawardena]

Hi devs,

I configured outbound provisioning for Salesforce and invoked the SCIM API
as in the documentation[1].

Here is the curl command that I invoked.

curl -v -k --header "Content-Type:application/json" --user ad...@wso2.com:admin
--data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
","password":"test25","name":{"familyName":"Menaka12"},"emails":["
q...@wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
https://localhost:9443/wso2/scim/Users

But it gives me an exception. (See the attached file).

I also tried the scim2 api as well.

curl -v -k --header "Content-Type:application/json" --user ad...@wso2.com:admin
--data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
","password":"test25","name":{"familyName":"Menaka12"},"emails":["
q...@wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
https://localhost:9443/scim2/Users

But this also gives an error.

{"schemas":"urn:ietf:params:scim:api:messages:2.0:Error","scimType":"invalidSyntax","detail":"Unknown
JSON representation for the MultiValued attribute emails which has data
type as COMPLEX","status":"400"}%

There is no mentioning about the SCIM2 API in the documentation.

Highly appreciate any solution for this.

[1]
https://docs.wso2.com/display/IS540/Outbound+Provisioning+with+Salesforce


Thanks and Regards,
Menaka
-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
*
*Blog: https://menakamadushanka.wordpress.com/
*
[2018-02-02 10:37:44,937] ERROR {org.apache.catalina.core.StandardWrapperValve} 
-  Servlet.service() for servlet [SCIMServlet] in context with path [/wso2] 
threw exception
java.lang.RuntimeException: org.apache.cxf.interceptor.Fault: 
org/wso2/carbon/identity/provisioning/IdentityProvisioningException
at 
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:116)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:336)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.webapp.mgt.filter.AuthorizationHeaderFilter.doFilter(AuthorizationHeaderFilter.java:128)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:615)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at 
org.ap

[Dev] JSON Path in a property

[Thomas LEGRAND]

Hello,

I have the following JSON:

{
"resourceType": "Bundle",
"entry": [{
"resource": {
"resourceType": "Patient",
"identifier": [{
"use": "usual",
"system": "MySystem",
"value": "12346"
},
{
"use": "secondary",
"system": "Yo",
"value": "654321"
}]
}
}]
}

I would like to extract the value of the identifier with the use "usual".
To do so, I wanted to use JSON Path as described in [1]. So, here is my
property with the right expression:


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


However, in my log, I just see an empty array...:

TID: [-1234] [] [2018-02-02 11:35:21,524]  INFO
{org.apache.synapse.mediators.builtin.LogMediator} -  To: /YoTest/,
MessageID: urn:uuid:b341e57e-f1cf-4b76-b79d-4185fbcb26a1, Direction: r
equest, MyValue = [],

The problem is I am sure my expression works because it works nicely on
[2]. So, is there a bug in the ESB?


[1] https://docs.wso2.com/display/ESB480/JSON+Support
[2] https://jsonpath.curiousconcept.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 2.1.0-update9 Released !

[Chamila Adhikarinayake]

The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update9 of API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

   -

   API Provider: Define new APIs and manage them
   -

   API Store: Browse published APIs and subscribe to them
   -

   API Gateway: The underlying API runtime based on WSO2 ESB
   -

   API Key Manager: Performs Key Generation and Key Validation
   functionalities
   -

   API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also, take a look at the online
product documentation
.

Distributions

WSO2 APIM 2.1.0-update9.zip


WSO2 APIM Analytics 2.1.0-update5.zip

How to Run

   1.

   Extract the downloaded zip
   2.

   Go to the bin directory in the extracted folder
   3.

   Run the wso2server.sh or wso2server.bat as appropriate
   4.

   Launch a web browser and navigate to https://localhost:9443/publisher to
   access the API publisher web app
   5.

   Navigate to https://localhost:9443/store to access the API store
   6.

   Navigate to https://localhost:9443/admin to access Admin Portal
   7.

   Use "admin", "admin" as the username and password to log in as an admin

Bug Fixes And Improvements in 2.1.0-update9

Please refer following locations for WSO2 API Manager 2.1.0-update9 Bug
fixes and Improvements


   1.

   JIRA 
   2.

   GitHub (carbon-apimgt)
   

   3.

   GitHub (product-apim)
   


Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   1.

   JIRA 
   2.

   GitHub (carbon-apimgt)
   
   3.

   GitHub (product-apim)
   

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List: dev@wso2.org | Subscribe | Mail Archive
   
   -

   User List: u...@wso2.org | Subscribe | Mail Archive
   
   -

   User Forum: Stack Overflow
   

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 API Manager through the WSO2 API Manager Git issues


-- WSO2 API Manager Team --

-- 
Regards,
Chamila Adhikarinayake
Senior Software Engineer
WSO2, Inc.
Mobile - +94712346437 <+94%2071%20234%206437>
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Add info on docs how to create and deploy custom extensions/UDFs to WSO2 SP

[Sriskandarajah Suhothayan]

When we do all the given steps, it will create a skeleton source code which
the user can then fill in extension logic.
They have to then build that source code using maven and copy the built
extension jar to the /lib directory.

Can you add this info to the product wiki and also to the siddhi doc site.


On Fri, Feb 2, 2018 at 12:38 PM, Rukshani Weerasinha 
wrote:

> Hello Suho,
>
> Now I have added this information in [1]
>
> Is there anything that the extension implementer needs to do afterwards if
> he presses *N* to indicate that the property values are not correct (step
> 3 in each procedure)?
>
> [1] https://docs.wso2.com/display/SP400/Writing+Custom+Siddhi+Extensions
>
> Best Regards,
> Rukshani.
>
> On Thu, Feb 1, 2018 at 12:50 PM, Rukshani Weerasinha 
> wrote:
>
>> Hi Suho,
>>
>> I will work on this and update this thread once it is done.
>>
>> Best Regards,
>> Rukshani.
>>
>> On Thu, Feb 1, 2018 at 12:18 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> @Rukshani
>>>
>>> Can you do $Subject? Refer Siddhi site for info[1]. We have to also say
>>> how/where to deploy those jars too.
>>> After the ongoing build, the info in [1] will be available in [2]
>>>
>>> [1]https://github.com/wso2/siddhi/blob/master/docs/documenta
>>> tion/siddhi-4.0.md#writing-custom-extensions
>>> [2] https://wso2.github.io/siddhi/documentation/siddhi-4.0/#
>>> writing-custom-extensions
>>>
>>> Regards
>>> Suho
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Director
>>> *WSO2 Inc. *
>>> http://wso2.com  
>>>
>>>
>>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>>> http://suhothayan.blogspot.com/ twitter:
>>> http://twitter.com/suhothayan  | linked-in:
>>> http://lk.linkedin.com/in/suhothayan *
>>>
>>
>>
>>
>> --
>> Rukshani Weerasinha
>>
>> WSO2 Inc.
>> Web:http://wso2.com
>> Mobile: 0777 683 738 <077%20768%203738>
>>
>>
>
>
> --
> Rukshani Weerasinha
>
> WSO2 Inc.
> Web:http://wso2.com
> Mobile: 0777 683 738 <077%20768%203738>
>
>


-- 

*S. Suhothayan*
Director
*WSO2 Inc. *
http://wso2.com  


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB plain/text

[Melodias]

Hi
Using ESB I got response with text/plain without soap envelope, it's just
simple text. How I can convert this to soap envelope? When I try change
message type to text/xml I got error.



--
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

Re: [Dev] Need of importing the CA certificate to JVM trust store in mutual SSL with X509 authenticator

[Indunil Upeksha Rathnayake]

Hi,

I have tested and verified that, it's not needed to add the trusted
certificates in JVM trust store for X509 authenticator, if we have properly
configured the trust store in catalina-server.xml. It's not correct to add
those certificates in JVM trust store, since it'll be affected globally for
all the wso2 and non wso2 products as well. We should update the wso2
documentation correctly, created a doc Jira in [1].

[1] https://wso2.org/jira/browse/DOCUMENTATION-7697

Thanks and Regards

On Wed, Jan 24, 2018 at 9:33 AM, Shakila Sasikaran  wrote:

> Hi,
>
> As I understand, If we want to make SSL connection and the certificate
> issued by the CA is not listed in the Java trust store, the connection will
> fail even if the root certificate is recognised by the browser. Because
> when the SSL connection is made, the runtime validates the server’s
> identity against the CA certificate which is included in the local database.
>
> Therefore, IMO we have to add it to the JVM.
>
> Thanks
>
> On Wed, Jan 24, 2018 at 8:46 AM, Samisa Abeysinghe 
> wrote:
>
>> My message got blocked due to customer name and got that removed.
>>
>> You have copied internal groups with the dev mails. (dev@org with
>> iam-group) This is asking for trouble. Either keep it public or private.
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Chief Engineering and Delivery Officer
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Wed, Jan 24, 2018 at 8:34 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi Samisa,
>>>
>>> This mail has been sent to dev@wso2.org, before the support ticket was
>>> raised. Please note that the rajas is the person who worked with X509
>>> authenticator, so added his personal email, since this is a discussion in
>>> dev.
>>>
>>> Thanks and Regards
>>>
>>> On Wed, Jan 24, 2018 at 8:21 AM, Samisa Abeysinghe 
>>> wrote:
>>>
 Who is hmrajas1...@gmail.com and why have we copied that email address
 in a private company discussion that is security related???

 Also, is this related to support.wso2.com/jira/browse/NGTDEV-5?

 If yes, we need to get back to support ticket and respond within today!

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Chief Engineering and Delivery Officer

 WSO2 Inc.
 http://wso2.com


 On Fri, Jan 19, 2018 at 10:02 AM, Indunil Upeksha Rathnayake <
 indu...@wso2.com> wrote:

> Adding rajas and connector team members
>
> On Thu, Jan 18, 2018 at 5:58 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> As per the documentation in [1], the certificate of CA, which issued
>> the client certificate, should be added into the JVM trust store. Please
>> find the following concerns regarding this.
>>
>>- We should add the CA certificate which issued the client
>>certificate, as a certificate authority in the browser. So that will 
>> be
>>added to the root certificate store in browser.
>>
>> The CA certificates in root certificate store, will determine which
>> endpoints we will be allowed to communicate with, in this case it will
>> allow the client to connect to whichever server presents a certificate
>> which was signed by one of the certificate authorities.
>>
>>- During the mutual SSL with X509 authenticator, there is no need
>>to consider JVM trust store in client side, since this is a direct 
>> call
>>from browser to the server.
>>
>>
>>- During the mutual SSL with X509 authenticator, there is no need
>>to consider JVM trust store in server side, since in server side, we 
>> have a
>>configured trust store. JVM trsust store is needed, if only the server
>>configured trust store is not loaded into the SSLContext.
>>
>>
>> So that, AFAIU, it is not needed to add CA certificate into JVM trust
>> store either in client or server side. WDYT?
>>
>> Appreciate your ideas on this.
>>
>> [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+X509C
>> ertificate+Authenticator#ConfiguringX509CertificateAuthentic
>> ator-Workingwithcertificates
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>> Mobile   0772182255 <077%20218%202255>
>>
>
>
>
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255 <077%20218%202255>
>


>>>
>>>
>>> --
>>> Indunil Upeksha Rathnayake
>>> Software Engineer | WSO2 Inc
>>> Emailindu...@wso2.com
>>> Mobile   0772182255 <077%20218%202255>
>>>
>>
>>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848 <+94%2077%20526%206848>
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.c

Re: [Dev] JSON Path in a property

[Thomas LEGRAND]

Actually, I think this is the site which is buggy because I found another
tester in [1].

And here is the expression which works:
$.entry[0].resource.identifier[?(@.use=='usual')].value

http://jsonpath.herokuapp.com/

Maybe the tester could be put in the documentation? :P

[1] http://jsonpath.herokuapp.com/

2018-02-02 11:40 GMT+01:00 Thomas LEGRAND :

> Hello,
>
> I have the following JSON:
>
> {
> "resourceType": "Bundle",
> "entry": [{
> "resource": {
> "resourceType": "Patient",
> "identifier": [{
> "use": "usual",
> "system": "MySystem",
> "value": "12346"
> },
> {
> "use": "secondary",
> "system": "Yo",
> "value": "654321"
> }]
> }
> }]
> }
>
> I would like to extract the value of the identifier with the use "usual".
> To do so, I wanted to use JSON Path as described in [1]. So, here is my
> property with the right expression:
>
> 
>  expression="json-eval($.entry[0].resource.identifier[?(@.
> use='usual')].value)"
> name="MyValue" xmlns:ns="http://org.apache.synapse/xsd"/>
> 
>
> However, in my log, I just see an empty array...:
>
> TID: [-1234] [] [2018-02-02 11:35:21,524]  INFO
> {org.apache.synapse.mediators.builtin.LogMediator} -  To: /YoTest/,
> MessageID: urn:uuid:b341e57e-f1cf-4b76-b79d-4185fbcb26a1, Direction: r
> equest, MyValue = [],
>
> The problem is I am sure my expression works because it works nicely on
> [2]. So, is there a bug in the ESB?
>
>
> [1] https://docs.wso2.com/display/ESB480/JSON+Support
> [2] https://jsonpath.curiousconcept.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev