[Dev] WSO2 IoT Server 3.1.0-UPDATE3 Released!

WSO2 IoT Server 3.1.0-UPDATE3 We are pleased to announce the latest update to WSO2 IoT Server 3.1.0 WSO2 IoT Server is one of the most adaptive Apache licensed open source IoT platforms available today. It provides best of breed

Re: [Dev] HTTP POST multipart/form-data via ESB

Hi Vivek, If your problem is regarding not adding boundary, try the fix in[1] relevant version, build and apply that jar as a patch. (Assuming you are using APIM210) [1] https://github.com/wso2/pro duct-ei/issues/780 Thanks Sudharma On Fri, Sep 22, 2017 at 2:12 PM, vivekkumar

Re: [Dev] HTTP POST multipart/form-data via ESB

Hi!, I think your problem is related to this: https://stackoverflow.com/questions/45617964/wso2-missing-boundary-in-multipart-form-data-post Problem being the Content-type line does not set the

Re: [Dev] HTTP POST multipart/form-data via ESB

I tried the option recommend in previous mail. Still have same issue. Following is my mediator with new changes and log captured in TcpMon --- mediator - http://ws.apache.org/ns/synapse;> $1

Re: [Dev] HTTP POST multipart/form-data via ESB

Hi I believe boundary issue has been fixed in July. In my case problem is that its not copying the content of file from Input to Backend service. I might be using the wrong syntax for copying the content. I just used the configuration mentioned in the original email. Cheers Vivek --

Re: [Dev] What is the correct behavior when user store selected from Inbound Provisioning Configuration

IMO, returning the username with userstore domain in the response may be seen as an unwanted sensitive information leak in this setup. Ideally in these kind of scenarios expectation is service provider doesn't need to know the user store domain name where his users are created. Therefore they can

Re: [Dev] [IS] [SCIM] Why Can't We Enable Both SCIM1 and SCIM2 at the Same Time?

On Fri, Sep 1, 2017 at 10:36 PM, Johann Nallathamby wrote: > In that case can we set a threadlocal variable in order to identify the > SCIM version? Based on that the correct listener will execute and the other > will not. Since SCIM1.1 listener will check for it's related

Re: [Dev] Remove outdated feature "Usage plan for the tenant"

IINM this comes from carbon-multitenancy. Not a identity feature. So if we are removing it needs to be removed from all the products. +1 to remove obsolete features if possible to avoid confusion. WSO2 Cloud uses a completely different model I suppose. On Sun, Sep 17, 2017 at 2:34 PM, Nilasini

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

See if this idea would work? We currently set a threadlocal variable inside the SCIM endpoint component, to identify the SCIM service provider inside some of our implementations. Can we improve this variable value to also identify the SCIM version? This way the relevant listeners will check for

[Dev] WSO2 Enterprise Integrator 6.1.1-update5 Released!

WSO2 Integration Team is pleased to announce the release of Enterprise Integrator 6.1.1-update5. This is the immediate release following 6.2.0-m4 release. Source and binary distribution files of WSO2 Enterprise Integrator 6.1.1-update5 are available for download from here

[Dev] WSO2 Identity Server 5.4.0 Alpha3 Released!

The WSO2 Identity and Access Management team is pleased to announce the release of WSO2 Identity Server 5.4.0 Alpha3. This distribution can be downloaded from the following location. https://github.com/wso2/product-is/releases/tag/v5.4.0-alpha3 The following list contains all the features,

[Dev] Too Many Slots submitted to delete - WSO2 MB

Hi, I am seeing a lot of this message in my MB Broker Logs: *TID: [] [] [2017-09-22 09:45:29,606] WARN {org.wso2.andes.kernel.slot.SlotDeletingTask} - Too many slots submitted to delete. Consider increasing and parameters. Current submit value = 5755 safe zone value = 5586695713193984* I

Re: [Dev] MB Cluster node issue

Hi Jason, Thanks for the tip. I am going to check that. Thanks, 2017-09-21 23:06 GMT-03:00 Jason De Silva : > Hi Junior, > > Can you verify whether time is synced across all MB nodes in the cluster > because in order for MB cluster to function properly the nodes needs to be >