Re: [Dev] Implementing UI for Multilevel Categorization for G-Reg Store

[Mushthaq Rumy]

Hi Dakshika,

Thanks for the suggestion. I will go through it.

Thanks & Regards,

On Thu, Mar 17, 2016 at 9:48 AM, Dakshika Jayathilaka 
wrote:

> Hi Mushthaq,
>
> IMO we can use simple dropdown for this. You can use same markup that we
> implemented previously. [1]  [2]
>
> [1]
> https://htmlpreview.github.io/?https://raw.githubusercontent.com/wso2-dev-ux/product-es/master/markup/wso2-leftmenu/home-categories-new.html
> [2]
> https://github.com/wso2-dev-ux/product-es/blob/master/markup/wso2-leftmenu/home-categories-new.html
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Sat, Mar 12, 2016 at 10:45 PM, Mushthaq Rumy  wrote:
>
>> Hi all,
>>
>> I'm currently working on Multilevel Categorization for G-Reg Store. I'm
>> planning to have a dropdown menu for the categorization as documented in
>> [1]. I have done a bit of searching to decide on library to use for this. I
>> think the dropdown menu shown in [2] would be ideal for this.
>>
>> Any suggestions can be really appreciated.
>>
>> [1] -
>> https://docs.google.com/document/d/1gU0KCCb595kJ0-B9ERMYmIbducZO3-4OCAGf0coZCs4/view#heading=h.dyjymrt5o8bq
>> [2] -
>> http://www.cssscript.com/demo/create-a-multi-level-drop-down-menu-with-pure-css/
>>
>> Thanks & Regards,
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Process Center] Permission API in Registry

[Mushthaq Rumy]

Hi,


There is a class called PermissionUtil in org.wso2.carbon.registry.resource.
services.utils package in the Registry. You can use the getPermissions
method in the above class to get the permission level.

Thanks & Regards,

On Wed, Apr 20, 2016 at 1:44 PM, Yasima Dewmini  wrote:

> Hi,
>
> I'm from PC team and I'm implementing process level permission support for
> PC. I need to get the permission level given resource, action and the user.
> Can I know the permission API used for this in Registry?
>
>
> Thanks and Regards,
> Yasima.
>
> --
> Yasima Dewmini
> Software Engineer, WSO2, Inc.
> Mobile: 0713117081
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] Help to build product-as

[Mushthaq Rumy]

Hi,

Have you set the  MAVEN_OPTS="-Xmx128m -XX:MaxPermSize=128m"? If not set it
and try to build it.

Thanks & Regards,

On Thu, Apr 21, 2016 at 7:18 PM, Megala Uthayakumar  wrote:

>
> Hi All,
>
> I am trying to build the product-as from the source. When tried to build
> v5.3.0, I got the following error and build failed.
>
> *[INFO] WSO2 AppServer Distribution having apache ldap server feature
> installed FAILURE [  3.839 s]*
>
> *Exception in thread "main" *
> *Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "main"*
>
> After that I tried to build from the master branch, but got following
> error,
> *[INFO] WSO2 Application Server - Module - Utils ... FAILURE [
>  1.542 s]*
>
> *[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> (default-compile) on project appserver-utils: Fatal error compiling:
> invalid target release: 1.8 -> [Help 1]*
>
> I am using oracle JDK 1.7.0_80 and my maven version is 3.3.9
>
> Could someone point out what is the cause for these errors?
>
> Thank you.
>
> Regards,
> Megala
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting an Error in the Stub created using Axis2

[Mushthaq Rumy]

Hi,

I created my stub using axis2 and when I run my client I get the following
error in the stub.

"Unexpected subelement {http://schemas.xmlsoap.org/soap/envelope/}Body";

I checked the request and responses using TcpMon.



*Requests*
1. This request is to add the order (This works fine as it is a void method)


http://schemas.xmlsoap.org/soap/envelope/";>

http://service.axis2.wso2.com";>
112
Kasun
WSO2
900.0





2. This request is to delete the order


http://schemas.xmlsoap.org/soap/envelope/";>

http://service.axis2.wso2.com";>
112






*Response*
1. This is the response for the 2nd request.


http://schemas.xmlsoap.org/soap/envelope/";>

http://service.axis2.wso2.com";>
true





I think the response is fine. But I'm unable to find the reason for the
above error in the stub.

Please guide me on this.

Thanks in advance.


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting an Error in the Stub created using Axis2

[Mushthaq Rumy]

Hi,

The stack trace is a follows,

org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement {http://schemas.xmlsoap.org/soap/envelope/}Body
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
com.wso2.axis2.client.OrderProcessingServiceStub.fromOM(OrderProcessingServiceStub.java:5402)
at
com.wso2.axis2.client.OrderProcessingServiceStub.deleteOrder(OrderProcessingServiceStub.java:591)
at
com.wso2.axis2.client.MyOrderProcessingClient.deleteOrder(MyOrderProcessingClient.java:100)
at
com.wso2.axis2.client.MyOrderProcessingClient.main(MyOrderProcessingClient.java:22)
Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException:
Unexpected subelement {http://schemas.xmlsoap.org/soap/envelope/}Body
at
com.wso2.axis2.client.OrderProcessingServiceStub$DeleteOrderResponse$Factory.parse(OrderProcessingServiceStub.java:3517)
at
com.wso2.axis2.client.OrderProcessingServiceStub.fromOM(OrderProcessingServiceStub.java:5382)
... 3 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement
{http://schemas.xmlsoap.org/soap/envelope/}Body
at
com.wso2.axis2.client.OrderProcessingServiceStub$DeleteOrderResponse$Factory.parse(OrderProcessingServiceStub.java:3511)
... 4 more

Thanks,


On Wed, Aug 26, 2015 at 6:32 PM, Harsha Thirimanna  wrote:

>
> On Wed, Aug 26, 2015 at 6:02 PM, Mushthaq Rumy  wrote:
>
>> /
>
>
> It is better if you can attach full stack trace .
>
>
>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * <http://www.apache.org/>*
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
> *harshathirimannlinked-in: **http:
> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>
> *Lean . Enterprise . Middleware*
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting an Error in the Stub created using Axis2

[Mushthaq Rumy]

Thanks Dinusha,

I'll check and see.

Thanks,

On Wed, Aug 26, 2015 at 6:59 PM, Dinusha Boteju  wrote:

> Hi Mushthaq,
>
> From the little info you have given, I did a bit of a research. One
> possible reason for this could be incompatible response type. Have a look
> at [1].
>
> [1] -
> http://mail-archives.apache.org/mod_mbox/axis-java-user/200807.mbox/%3c60708f4b0807090748t289f5971wf44e1057b89d7...@mail.gmail.com%3E
>
> -Dinusha
>
>
> On Wed, Aug 26, 2015 at 6:49 PM, Harsha Thirimanna 
> wrote:
>
>>
>> On Wed, Aug 26, 2015 at 6:37 PM, Mushthaq Rumy  wrote:
>>
>>> org.apache.axis2.databinding.ADBException: Unexpected subelement {
>>> http://schemas.xmlsoap.org/soap/envelope/}Body
>>>
>>
>> ​Can you try out this with building stub that is pointing jaxbri ?​
>>
>>
>>
>> *Harsha Thirimanna*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> * <http://www.apache.org/>*
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>> *harshathirimannlinked-in: **http:
>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Dinusha Boteju*
> *Associate Tech Lead,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting an Error in the Stub created using Axis2

[Mushthaq Rumy]

Hi Hasunie,

I think the error says the body is the Unexpected element. So I think there
is something wrong with the SOAP body element. But when I checked the
response in TcpMon it was fine.

Thanks,

On Thu, Aug 27, 2015 at 11:16 AM, Hasunie Adikari  wrote:

> Hi Mushthaq,
>
> In general, "Unexpected subelement" means that the message being processed
> doesn't conform to the WSDL that was used to generate the ADB code.you are
> getting this exception on the client side, it means that the response from
> the server is invalid.
> check if your mandatory elements are filled within the server.
>
> On Thu, Aug 27, 2015 at 10:23 AM, Kasun Bandara  wrote:
>
>> Hi Mushthaq,
>>
>> According to [1] , aforementioned error mostly occur in Axis2 in ADB
>> databinding type, when the sequence of tags coming in SOAP response is not
>> same as that of attributes in java class formed from wsdl. You can resolved
>> this by changing the sequence of tags in wsdl.
>>
>> [1]
>> http://stackoverflow.com/questions/10113395/apache-unexpected-subelement-exception-while-generating-a-webservice-client
>>
>> Thanks.
>>
>>
>>
>>
>> On Wed, Aug 26, 2015 at 7:14 PM, Mushthaq Rumy  wrote:
>>
>>> Thanks Dinusha,
>>>
>>> I'll check and see.
>>>
>>> Thanks,
>>>
>>> On Wed, Aug 26, 2015 at 6:59 PM, Dinusha Boteju 
>>> wrote:
>>>
>>>> Hi Mushthaq,
>>>>
>>>> From the little info you have given, I did a bit of a research. One
>>>> possible reason for this could be incompatible response type. Have a look
>>>> at [1].
>>>>
>>>> [1] -
>>>> http://mail-archives.apache.org/mod_mbox/axis-java-user/200807.mbox/%3c60708f4b0807090748t289f5971wf44e1057b89d7...@mail.gmail.com%3E
>>>>
>>>> -Dinusha
>>>>
>>>>
>>>> On Wed, Aug 26, 2015 at 6:49 PM, Harsha Thirimanna 
>>>> wrote:
>>>>
>>>>>
>>>>> On Wed, Aug 26, 2015 at 6:37 PM, Mushthaq Rumy 
>>>>> wrote:
>>>>>
>>>>>> org.apache.axis2.databinding.ADBException: Unexpected subelement {
>>>>>> http://schemas.xmlsoap.org/soap/envelope/}Body
>>>>>>
>>>>>
>>>>> ​Can you try out this with building stub that is pointing jaxbri ?​
>>>>>
>>>>>
>>>>>
>>>>> *Harsha Thirimanna*
>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>>> * <http://www.apache.org/>*
>>>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>>>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>>>>> *harshathirimannlinked-in: **http:
>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>>
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Dinusha Boteju*
>>>> *Associate Tech Lead,*
>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>>> *lean.enterprise.middleware.*
>>>>
>>>> email: dinus...@wso2.com 
>>>> phone:(+94) 776640275 <%28%2B94%29%2039736>
>>>>
>>>
>>>
>>>
>>> --
>>> Mushthaq Rumy
>>> *Software Engineer*
>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>> Email : musht...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kasun Bandara
>> *Software Engineer*
>> Mobile : +94 (0) 718 338 360
>> <%2B94%20%280%29%20773%20451194>
>> kas...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Hasunie Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> blog http://hasuniea.blogspot.com
> Mobile:+94715139495
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Mushthaq Rumy]

Hi Rajeenthani,

I think you need to create an object instance of AutomationContext within
your java class and proceed with it. The below link[1] might be useful for
you.

[1]
http://malinthas.blogspot.com/2014/02/how-to-obtain-configuration-details.html
.



On Mon, Sep 28, 2015 at 1:44 PM, Rajeenthini Satkunam 
wrote:

> Hi all,
>
> I am currently working on writing UI integration tests for product UES
> using selenium.I have to make maximum waiting time for search element by()
> as default value.As per discussion it can be configured through
> automation.xml file. I have added 30 maximumWaitingTime> at automation.xml file.So I need to get the value of
> it for test java classes.Can anyone please give any suggestion on how to
> get that value?
>
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823>   *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

Thanks & Regards,
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.1.0 RC 1

[Mushthaq Rumy]

Hi All,

I have tested the pack with the samples.

[+] Stable - go ahead and release.

Thanks & Regards,

On Sat, Oct 31, 2015 at 3:54 PM, Denuwanthi De Silva 
wrote:

> Hi,
>
>
> I have tested the pack with following scenarios:
>
> 1 - Notification/Subscription support in Publisher and Store.
> 2 - Notification/Subscription support in management console
> 3 - E-mail notification/subscription support in publisher and management
> console
> 4 - Notification/Subscription support for a tenant user.
> 5 - Notification/Subscription support on a mounted setup.
> 6 - Notification/Subscription support on collections.
> 7 - Tested one time email verification for Publisher and management
> console.
>
> [+] Stable - go ahead and release.
>
> Thanks,
>
> On Sat, Oct 31, 2015 at 3:51 PM, Rajith Roshan  wrote:
>
>> Hi All,
>>
>> I tested following scenarios.
>>
>>
>>- Add new RXT types and RXT hot deployment.
>>- Check rxt elements.
>>- Check permissions for asset types in publisher for users,  and
>>tenants.
>>- Check categorization and tags.
>>- Check regex validation.
>>- Sample data populator.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks!
>> Rajith
>>
>> On Fri, Oct 30, 2015 at 11:40 PM, Danesh Kuruppu  wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Governance Registry 5.1.0 RC1 Release Vote.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12499
>>> <https://wso2.org/jira/issues/?filter=12422>
>>> Please download, test and vote. Please refer the release verification
>>> guide for detailed information on verifying this release.
>>>
>>> Source & binary distribution files:
>>> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.1.0/RC1/
>>>
>>> Maven staging repo:
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-096/
>>> <http://www.google.com/url?q=http%3A%2F%2Fmaven.wso2.org%2Fnexus%2Fcontent%2Frepositories%2Forgwso2greg-096%2F&sa=D&sntz=1&usg=AFQjCNHn187zs7NcAgrhAiIk2xQJX2WUKQ>
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-greg/tree/v5.1.0-RC1
>>>
>>>
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards
>>> G-Reg team
>>>
>>> --
>>>
>>> Danesh Kuruppu
>>> Software Engineer
>>> WSO2 Inc,
>>> Mobile: +94 (77) 1690552
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Roshan
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Denuwanthi De Silva
> Software Engineer;
> WSO2 Inc.; http://wso2.com,
> Email: denuwan...@wso2.com
> Blog: https://denuwanthi.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Grainier Perera

[Mushthaq Rumy]

Congratulations Grainier :)

Thanks & Regards

On Wed, Feb 3, 2016 at 5:25 PM, Tishan Dahanayakage  wrote:

> Congratulations Grainier!!
>
> On Wed, Feb 3, 2016 at 4:47 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Grainier Perera as a WSO2 Committer.
>> Grainier has been a valuable contributor for WSO2 CEP & Metrics
>> Components and did a commendable worked on Virtual Hackathon & Forrester
>> Demo, and in recognition of his contribution to WSO2, he has been voted
>> as a WSO2 Committer.
>>
>> Grainier, congratulations and keep up the good work!
>>
>> Thanks & Regards.
>> Suho
>>
>> --
>>
>> *S. Suhothayan*
>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>> *WSO2 Inc. *http://wso2.com
>> * <http://wso2.com/>*
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Implementing UI for Multilevel Categorization for G-Reg Store

[Mushthaq Rumy]

Hi all,

I'm currently working on Multilevel Categorization for G-Reg Store. I'm
planning to have a dropdown menu for the categorization as documented in
[1]. I have done a bit of searching to decide on library to use for this. I
think the dropdown menu shown in [2] would be ideal for this.

Any suggestions can be really appreciated.

[1] -
https://docs.google.com/document/d/1gU0KCCb595kJ0-B9ERMYmIbducZO3-4OCAGf0coZCs4/view#heading=h.dyjymrt5o8bq
[2] -
http://www.cssscript.com/demo/create-a-multi-level-drop-down-menu-with-pure-css/

Thanks & Regards,
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Natasha Wijesekara

[Mushthaq Rumy]

Congratz Natasha...!

Thanks & Regards,
Mushthaq

On Wed, Jun 29, 2016 at 11:44 AM, Fazlan Nazeem  wrote:

> congrats Natasha!
>
> On Wed, Jun 29, 2016 at 10:23 AM, Nandika Jayawardana 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Natasha Wijesekara as a WSO2 Committer.
>> Natasha has been a great contributor to BPS and PC products and in
>> recognition of her contributions, she's been voted as a WSO2 Committer.
>>
>> Congratulations Natasha and keep up the good work!
>>
>> Regards
>> Nandika
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC] Published processes are not visible in the store before login

[Mushthaq Rumy]

Hi Yasima,

In order to view a particular process in the store side before login, that
particular process needs to have permission to Anonymous role. Please check
if that particular process has the permission for Anonymous role.

Thanks & Regards,
Mushthaq

On Fri, Aug 12, 2016 at 9:49 AM, Yasima Dewmini  wrote:

> Hi,
>
> In PC, we have a new lifecycle suit to the process management. Once a
> process is published using this lifecycle, that process is not visible in
> the store before login. It is visible when a user logged into the store.
> Is there any configuration to be set or am i missing anything?
>
> Appreciate any help regarding this issue.
>
> Regards,
> Yasima.
>
> --
> http://wso2.com/signatureYasima Dewmini
> Software Engineer, WSO2, Inc.
> Email: yas...@wso2.com
> Mobile: +94713117081
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Mushthaq Rumy

[Mushthaq Rumy]

Thanks everyone :)

Thanks & Regards,
Mushthaq

On Fri, Sep 2, 2016 at 9:02 PM, Rasika Perera  wrote:

> Congratulations Rumy 
>
> On Fri, Sep 2, 2016 at 11:50 AM, Chandana Napagoda 
> wrote:
>
>> Hi all,
>>
>> It is my pleasure to welcome Mushthaq Rumy as a WSO2 Committer. Rumy has
>> made some great contributions to WSO2 Governance Registry and WSO2
>> Enterprise Store products during the last few months and in recognition of
>> his commitment and contributions, he has been voted as a Committer for WSO2.
>>
>> Rumy, welcome aboard and keep up the good work.
>>
>> Best Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
>> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> [image: wso2-signature-general.png] <https://wso2.com/signature>
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

[Mushthaq Rumy]

Congratulation Lahiru...!!! :)

Thanks & Regards,
Mushthaq

On Tue, Sep 6, 2016 at 11:00 AM, Chandana Napagoda 
wrote:

> Hi All,
>
> It is my pleasure to welcome Lahiru J Ekanayake as a WSO2 Committer.
> Lahiru has made some great contributions to WSO2 Governance Registry and
> WSO2 Enterprise Store products during the last few months, specially to
> implement the taxonomy feature. In recognition of his commitment and
> contributions, Lahiru has been voted as a Committer for WSO2.
>
> Lahiru, welcome aboard and keep up the good work.
>
> Best Regards,
> Chandana
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Ashen Weerathunga

[Mushthaq Rumy]

Congrats Ashen!

Thanks & Regards,
Mushthaq

On Tue, Oct 4, 2016 at 2:39 PM, Sameera Ramasinghe 
wrote:

> Congratz Ashen!!
>
> On Tue, Oct 4, 2016 at 1:56 PM, Grainier Perera  wrote:
>
>> Congratulations Ashen.!
>>
>> On Tue, Oct 4, 2016 at 11:03 AM, Nirmal Fernando  wrote:
>>
>>> Hi all,
>>>
>>> It is my pleasure to welcome Ashen Weerathunga as a WSO2 Committer. In
>>> recognition of Ashen's contributions to ML, Siddhi and IoT analytics, he
>>> has been voted as a Committer.
>>>
>>> Ashen, welcome aboard and keep up the good work.
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Grainier Perera
>> Software Engineer
>> Mobile : +94716122384
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sameera Ramasinghe*
> Software Engineer, WSO2 Inc.; http://wso2.com
> mobile: *+94 714489682*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Madawa Soysa

[Mushthaq Rumy]

>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Sabra Ossen*
>>>>>>>> *Software Engineer*
>>>>>>>> Email: sa...@wso2.com
>>>>>>>> Mobile: +94 767 837356
>>>>>>>>
>>>>>>>> <http://wso2.com/signature>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Prakhash Sivakumar
>>>>>>> Software Engineer | WSO2 Inc
>>>>>>> Platform Security Team
>>>>>>> Mobile : +94771510080
>>>>>>> Blog : https://medium.com/@PrakhashS
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Chanaka Cooray
>>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>>> Email: chana...@wso2.com
>>>>>> Mobile: +94713149860
>>>>>> <https://wso2.com/signature>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Fathima Dilhasha
>>>>> *Software Engineer*
>>>>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>>>>> <%2B94%20%280%29%20773%20451194>
>>>>> dilha...@wso2.com 
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Malintha Fernando
>>>> Software Engineer
>>>> WSO2 Inc. | http://wso2.com
>>>> Mobile : +94 718874922
>>>> Blog : http://blog.malintha.org
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Eranda Rajapakshe*
>>> Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94784822608
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *Lahiru J Ekanayake**Software Engineer*
>> Mobile : +9471 8812629 / +94778509547
>> Email : lahi...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Gunarathne
> Software Engineer, WSO2 Inc. http://wso2.com
> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com&h=gAQEswASa>
> Email: samee...@wso2.com
> Mobile: +94714155561
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Kasun Thennakoon

[Mushthaq Rumy]

Congratz Kasun :)

Thanks & Regards,
Mushthaq

On Fri, Oct 21, 2016 at 9:58 AM, Lahiru J Ekanayake 
wrote:

> Congratz Kasun :) !!!
>
> On Fri, Oct 21, 2016 at 9:39 AM, Samitha Chathuranga 
> wrote:
>
>> Congratz Kasun :)
>>
>> On Fri, Oct 21, 2016 at 9:36 AM, Malintha Amarasinghe > > wrote:
>>
>>> Congratulations Kasun!! :)
>>>
>>>
>>> On Fri, Oct 21, 2016 at 9:30 AM, Maneesha Wijesekara 
>>> wrote:
>>>
>>>> Congratulations Kasun.
>>>>
>>>> On Fri, Oct 21, 2016 at 9:13 AM, Chandana Napagoda 
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> It is my pleasure to welcome Kasun Thennakoon as a WSO2 Committer.
>>>>> Kasun has made some great contributions to WSO2 Enterprise Store and WSO2
>>>>> Governance Registry products during the last few months and in recognition
>>>>> of his commitment and contributions, he has been voted as a Committer for
>>>>> WSO2.
>>>>>
>>>>> @Kasun, welcome aboard and keep up the good work.
>>>>>
>>>>> Best Regards,
>>>>> Chandana
>>>>>
>>>>> --
>>>>> *Chandana Napagoda*
>>>>> Associate Technical Lead
>>>>> WSO2 Inc. - http://wso2.org
>>>>>
>>>>> *Email  :  chand...@wso2.com **Mobile :
>>>>> +94718169299 <%2B94718169299>*
>>>>>
>>>>> *Blog  :http://cnapagoda.blogspot.com
>>>>> <http://cnapagoda.blogspot.com> | http://chandana.napagoda.com
>>>>> <http://chandana.napagoda.com>*
>>>>>
>>>>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>>>>> <http://www.linkedin.com/in/chandananapagoda>*
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Maneesha Wijesekara
>>>> Software Engineer - QA Team
>>>> WSO2 Inc.
>>>>
>>>> Email: manee...@wso2.com
>>>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>>>> Mobile: +94712443119
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Samitha Chathuranga
>> Software Engineer, WSO2 Inc.
>> lean.enterprise.middleware
>> Mobile: +94715123761
>>
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +9471 8812629 / +94778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Error while installing Account Recovery and Credential Management Feature in wso2am-2.0.1-SNAPSHOT

[Mushthaq Rumy]

Hi Abimaran,

I downloaded the P2 locally and checked. It still gives the same error. Any
help on this is highly appreciated.

Thanks & Regards,
Mushthaq

On Mon, Oct 31, 2016 at 2:27 PM, Abimaran Kugathasan 
wrote:

> Hi Mushthaq,
>
> This issue mostly occurs when the JARs are corrupted while installing over
> the network. You can download the entire P2 locally and check.
>
> On Mon, Oct 31, 2016 at 12:22 PM, Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> I am getting an error in the console while trying to install Account
>> Recovery and Credential Management Feature in wso2am-2.0.1-SNAPSHOT through
>> management console. I have attached the error log file herewith.
>>
>> Has anyone has come across this? Any input on this is highly appreciated.
>>
>>
>>
>> *Error*TID: [-1234] [] [2016-10-31 11:07:10,686] ERROR
>> {org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService} -
>> Error occurred while performing provisioning action
>> {org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService}
>> org.wso2.carbon.feature.mgt.core.ProvisioningException: NLS missing
>> message: Phase_Install_Error in: org.eclipse.equinox.internal.p
>> 2.engine.messages
>>   NLS missing message: session_context in: org.eclipse.equinox.internal.p
>> 2.engine.messages
>>   NLS missing message: artifact_file_not_found in:
>> org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.messages
>> at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.perf
>> ormProvisioningAction(ProvisioningUtils.java:76)
>> at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.perf
>> ormProvisioningAction(ProvisioningUtils.java:85)
>> at org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminS
>> ervice.performProvisioningAction(ProvisioningAdminService.java:313)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
>> RPCUtil.java:212)
>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>> nessLogic(RPCMessageReceiver.java:117)
>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>> bstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:169)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:82)
>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>> (LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:430)
>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:225)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.wso2.carbon.feature.mgt.stub.ProvisioningAdminServiceStu
>> b.performProvisioningAction(ProvisioningAdminServiceStub.java:1085)
>> at org.wso2.carbon.feature.mgt.ui.ProvisioningAdminClient.perfo
>> rmInstallation(ProvisioningAdminClient.java:138)
>> at org.apache.jsp.feature_002dmgt.perform_005finstallation_002d
>> ajaxprocessor_jsp._jspService(perform_005finstallation_002da
>> jaxprocessor_jsp.java:134)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.

[Dev] Error when invoking Salesforce login method using jaggery

[Mushthaq Rumy]

Hi All,

I'm getting an error while invoking the Salesforce login operation using
jaggery. I tried the same payload through SOAP UI and it is working fine.
The following is the jaggery code block.

var payload =  '' +
  '' +
salesforce_username + '' +
  '' +
salesforce_password + salesforce_security_token + '' +
   '';
var options = new Array();
options.useSOAP = 1.1;
options.CONNECTION_TIMEOUT = 12;
salesforce.open(options, salesforce_url, false);
*salesforce.send(payload);*

The following is the error logged and the full error log is attached
herewith.

ERROR {org.jaggeryjs.modules.ws.WSRequestHostObject} -  Error occured while
invoking the service {org.jaggeryjs.modules.ws.WSRequestHostObject}
java.lang.NullPointerException

Any thoughts or help on this is highly appreciated.

Thanks & Regards,
Mushthaq
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

<http://wso2.com/signature>


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

[Dev] Adding a secondary user store role to a secondary user store user

[Mushthaq Rumy]

Hi All,

I was trying to add a user to a secondary user store in IS 5.3.0 Management
Console. In the user creation flow, adding a same secondary user store role
to the created user, does not seem to work. It gives the successfully added
message but the role is not added to that specific user.

But, listing the created user and adding the same role works fine.

Steps to reproduce :-

1. Create a custom secondary user store.
2. Login to Management Console.
3. Add a new role to the created secondary user store.
4. Add a new user to the created secondary user store with previously
created role.
5. Gives a success message but when you lists role for the user, it will
not be available.

Any thoughts on this is highly appreciated.

-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Adding a secondary user store role to a secondary user store user

[Mushthaq Rumy]

Found the cause. Seems like there is a problem with the custom user store
manager class.

Thanks & Regards,
Mushthaq

On Mon, Oct 16, 2017 at 4:27 PM, Godwin Shrimal  wrote:

> What is the type of the secondary user store you created? Ex. JDBC,
> ReadOnlyLDAP etc.
>
>
> Thanks
> Godwin
>
>
> On Mon, Oct 16, 2017 at 1:57 PM, Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> I was trying to add a user to a secondary user store in IS 5.3.0
>> Management Console. In the user creation flow, adding a same secondary user
>> store role to the created user, does not seem to work. It gives the
>> successfully added message but the role is not added to that specific user.
>>
>> But, listing the created user and adding the same role works fine.
>>
>> Steps to reproduce :-
>>
>> 1. Create a custom secondary user store.
>> 2. Login to Management Console.
>> 3. Add a new role to the created secondary user store.
>> 4. Add a new user to the created secondary user store with previously
>> created role.
>> 5. Gives a success message but when you lists role for the user, it will
>> not be available.
>>
>> Any thoughts on this is highly appreciated.
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
> twitter: https://twitter.com/godwinamila
> <http://wso2.com/signature>
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Unit Test for AS400 PCML Connector

[Mushthaq Rumy]

on+in+AS400
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762 <+94%2077%20768%208882>
>>
>> On Wed, Oct 11, 2017 at 11:42 AM, Janani Thangavel 
>> wrote:
>>
>>> Adding Hemika.
>>>
>>> Janani Thangavel
>>> Associate Software Engineer
>>> WSO2 Inc : http://wso2.org
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>>> Mobile   : +94771856427 <+94%2077%20185%206427>
>>>
>>> On Wed, Oct 11, 2017 at 11:40 AM, Janani Thangavel 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Currently I'm working on the unit testing [1] for AS400 pcml connector. 
>>>> Inside
>>>> the pcml connector we are creating a instance for ProgramCallDocument
>>>> [2]. It calls actual back end Server. So, I'm trying to mock
>>>> that ProgramCallDocument as follow [3]. Even if I mock, It calls the actual
>>>> back end service and get the error as [4]. Am I doing anything wrong?
>>>> Please help me on this.
>>>>
>>>>
>>>> [1]https://github.com/wso2-extensions/esb-connector-pcml/pull/9
>>>> [2]https://github.com/jananithangavel/esb-connector-pcml/blo
>>>> b/master/src/main/java/org/wso2/carbon/connector/pcml/AS400C
>>>> allProgram.java#L91
>>>> [3]https://github.com/jananithangavel/esb-connector-pcml/blo
>>>> b/2f3f9585225750c6f009a039ef716a520ca2bdf3/src/test/java/org
>>>> /wso2/carbon/connector/pcml/test/unit/AS400CallProgramUnitTest.java#L79
>>>> [4]org.apache.synapse.SynapseException: Unable to connect to AS400
>>>> server: A parse error occurred.
>>>>
>>>> Thanks.
>>>>
>>>> Regards,
>>>> Janani Thangavel
>>>> Associate Software Engineer
>>>> WSO2 Inc : http://wso2.org
>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>>>> Mobile   : +94771856427 <+94%2077%20185%206427>
>>>>
>>>
>>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] requirePasswordChange is a required attribute but optional in the RemoteUserStoreManagerService wsdl

[Mushthaq Rumy]

Hi All,

requirePasswordChange attribute in addUser operation in the
RemoteUserStoreManagerService is a required attribute but it is made
optional in the RemoteUserStoreManagerService wsdl. When I invoke the
addUser operation without requirePasswordChange attribute, it gives the
following exception.

http://schemas.xmlsoap.org/soap/envelope/";>

  
 soapenv:Server
 Exception occurred while trying to invoke
service method addRole
 
  
   



I tried this in SOAPUI.

Seems like this needs to be fixed. I have created a JIRA [1].

[1] - https://wso2.org/jira/browse/IDENTITY-6803

Thanks & Regards,
Mushthaq
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Endpoint Address

[Mushthaq Rumy]

Hi Melodias,

You can also try with messageContext.getTo() [1] as well.

[1] -
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/core/axis2/Axis2MessageContext.java#L384

Thanks & Regards,
Mushthaq

On Tue, Oct 24, 2017 at 6:28 PM, Himasha Guruge  wrote:

> Hi ,
>
> Could you try with  context.getEndpoint(endpointKey).getName();
>
> [1] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
> e/src/main/java/org/apache/synapse/core/axis2/Axis2MessageCo
> ntext.java#L235
>
> Thanks,
> Himasha
>
> On Tue, Oct 24, 2017 at 6:05 PM, Melodias 
> wrote:
>
>> Hi dev,
>> It is possible to get backend endpoint address from
>> org.apache.axis2.context.MessageContext?
>>
>>
>>
>> --
>> 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
>>
>
>
>
> --
> Himasha Guruge
> Senior Software Engineer
> WS*O2* *Inc.*
> Mobile: +94 777459299 <+94%2077%20745%209299>
> himas...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] UserAccountAssociationService having “/permission/admin/login” permissions in some operations

[Mushthaq Rumy]

Hi All,

Is there a specific reason to have "/permission/admin/login" in some of the
operations in UserAccountAssociationService?

This permission will allow the users to login to the Management Console and
In case, if someone wants to use these operations of
UserAccountAssociationService in a separate client application and he/she
does not want to the users of this application to login to the Management
Console, what would be the work around and how can we solve this?

Your thoughts on this is highly appreciated.

Thanks & Regards,
Mushthaq
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] UserAccountAssociationService having “/permission/admin/login” permissions in some operations

[Mushthaq Rumy]

Hi Thanuja,

Thanks for the clarification. One more thing. Is there a way that we can
avoid specific users to login to the Management Console who has "
permission/admin/login" permission?

Thanks & Regards,
Mushthaq

On Thu, Oct 26, 2017 at 7:28 PM, Thanuja Jayasinghe 
wrote:

> Hi Mushthaq,
>
> UserAccountAssociationService.switchLoggedInUser() service method is only
> useful for users who has logged in session. Because this feature provides
> support for switch between associated user accounts in that logged in
> session. In order to create a session we need to call A
> uthenticationAdmin.login() and in this service method, we do check
> whether the user has permission/admin/login permission[1]. So it is a
> must to have permission/admin/login permission for any user who is using
> switchLoggedInUser method.
>
> I think this gives the rationality for other methods which have the same
> permission level.
>
> [1] - https://github.com/wso2/carbon-kernel/blob/4.4.x/core/
> org.wso2.carbon.core.services/src/main/java/org/wso2/carbon/
> core/services/authentication/AuthenticationAdmin.java#L110
>
> Thanks,
> Thanuja
>
> On Thu, Oct 26, 2017 at 6:18 PM, Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> Is there a specific reason to have "/permission/admin/login" in some of
>> the operations in UserAccountAssociationService?
>>
>> This permission will allow the users to login to the Management Console
>> and In case, if someone wants to use these operations of
>> UserAccountAssociationService in a separate client application and he/she
>> does not want to the users of this application to login to the Management
>> Console, what would be the work around and how can we solve this?
>>
>> Your thoughts on this is highly appreciated.
>>
>> Thanks & Regards,
>> Mushthaq
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> *Thanuja Lakmal*
> Associate Technical Lead
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] UserAccountAssociationService having “/permission/admin/login” permissions in some operations

[Mushthaq Rumy]

@Farasath - These users will have roles assigned to them.

Thanks & Regards,
Mushthaq

On Sun, Oct 29, 2017 at 1:01 AM, Farasath Ahamed  wrote:

>
>
> On Friday, October 27, 2017, Mushthaq Rumy  wrote:
>
>> Hi Thanuja,
>>
>> Thanks for the clarification. One more thing. Is there a way that we can
>> avoid specific users to login to the Management Console who has "
>> permission/admin/login" permission?
>>
>
> Can we identify these users based on their role or some other attribute?
>
>
>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Thu, Oct 26, 2017 at 7:28 PM, Thanuja Jayasinghe 
>> wrote:
>>
>>> Hi Mushthaq,
>>>
>>> UserAccountAssociationService.switchLoggedInUser() service method is
>>> only useful for users who has logged in session. Because this feature
>>> provides support for switch between associated user accounts in that logged
>>> in session. In order to create a session we need to call A
>>> uthenticationAdmin.login() and in this service method, we do check
>>> whether the user has permission/admin/login permission[1]. So it is a
>>> must to have permission/admin/login permission for any user who is
>>> using switchLoggedInUser method.
>>>
>>> I think this gives the rationality for other methods which have the same
>>> permission level.
>>>
>>> [1] - https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.ws
>>> o2.carbon.core.services/src/main/java/org/wso2/carbon/core/
>>> services/authentication/AuthenticationAdmin.java#L110
>>>
>>> Thanks,
>>> Thanuja
>>>
>>> On Thu, Oct 26, 2017 at 6:18 PM, Mushthaq Rumy 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Is there a specific reason to have "/permission/admin/login" in some of
>>>> the operations in UserAccountAssociationService?
>>>>
>>>> This permission will allow the users to login to the Management Console
>>>> and In case, if someone wants to use these operations of
>>>> UserAccountAssociationService in a separate client application and he/she
>>>> does not want to the users of this application to login to the Management
>>>> Console, what would be the work around and how can we solve this?
>>>>
>>>> Your thoughts on this is highly appreciated.
>>>>
>>>> Thanks & Regards,
>>>> Mushthaq
>>>> --
>>>> Mushthaq Rumy
>>>> *Software Engineer*
>>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>>> Email : musht...@wso2.com
>>>> WSO2, Inc.; http://wso2.com/
>>>> lean . enterprise . middleware.
>>>>
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> *Thanuja Lakmal*
>>> Associate Technical Lead
>>> WSO2 Inc. http://wso2.com/
>>> *lean.enterprise.middleware*
>>> Mobile: +94715979891
>>>
>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
> --
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] UserAccountAssociationService having “/permission/admin/login” permissions in some operations

[Mushthaq Rumy]

Thanks Farasath. I'll check on this.

Thanks & Regards,
Mushthaq

On Mon, Oct 30, 2017 at 1:23 PM, Farasath Ahamed  wrote:

> Hi Rumy,
>
> If we can identify the users we want to restrict access by a particular
> role, Let's say 'X'. We can achieve your requirement as follows,
>
> 1. Add management console as a service provider in IS ( Ref:
> https://medium.com/@PrakhashS/enabling-multi-factor-
> authentication-for-wso2-identity-server-management-console-c4e247cd553f)
>
> 2. Engage Authorization for the service provider representing the
> management console. (Ref: https://medium.com/@pulasthi7/
> application-authorization-using-wso2-identity-server-1-
> introduction-3f2e0898b43e)
>
> 3. We can engage an XACML policy which restricts login to users with role
> 'X'
>
>
> Thanks,
> Farasath
>
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 <https://twitter.com/farazath619>
> <http://wso2.com/signature>
>
>
>
> On Sun, Oct 29, 2017 at 10:53 PM, Mushthaq Rumy  wrote:
>
>> @Farasath - These users will have roles assigned to them.
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Sun, Oct 29, 2017 at 1:01 AM, Farasath Ahamed 
>> wrote:
>>
>>>
>>>
>>> On Friday, October 27, 2017, Mushthaq Rumy  wrote:
>>>
>>>> Hi Thanuja,
>>>>
>>>> Thanks for the clarification. One more thing. Is there a way that we
>>>> can avoid specific users to login to the Management Console who has "
>>>> permission/admin/login" permission?
>>>>
>>>
>>> Can we identify these users based on their role or some other attribute?
>>>
>>>
>>>
>>>> Thanks & Regards,
>>>> Mushthaq
>>>>
>>>> On Thu, Oct 26, 2017 at 7:28 PM, Thanuja Jayasinghe 
>>>> wrote:
>>>>
>>>>> Hi Mushthaq,
>>>>>
>>>>> UserAccountAssociationService.switchLoggedInUser() service method is
>>>>> only useful for users who has logged in session. Because this feature
>>>>> provides support for switch between associated user accounts in that 
>>>>> logged
>>>>> in session. In order to create a session we need to call A
>>>>> uthenticationAdmin.login() and in this service method, we do check
>>>>> whether the user has permission/admin/login permission[1]. So it is a
>>>>> must to have permission/admin/login permission for any user who is
>>>>> using switchLoggedInUser method.
>>>>>
>>>>> I think this gives the rationality for other methods which have the
>>>>> same permission level.
>>>>>
>>>>> [1] - https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.ws
>>>>> o2.carbon.core.services/src/main/java/org/wso2/carbon/core/s
>>>>> ervices/authentication/AuthenticationAdmin.java#L110
>>>>>
>>>>> Thanks,
>>>>> Thanuja
>>>>>
>>>>> On Thu, Oct 26, 2017 at 6:18 PM, Mushthaq Rumy 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Is there a specific reason to have "/permission/admin/login" in some
>>>>>> of the operations in UserAccountAssociationService?
>>>>>>
>>>>>> This permission will allow the users to login to the Management
>>>>>> Console and In case, if someone wants to use these operations of
>>>>>> UserAccountAssociationService in a separate client application and he/she
>>>>>> does not want to the users of this application to login to the Management
>>>>>> Console, what would be the work around and how can we solve this?
>>>>>>
>>>>>> Your thoughts on this is highly appreciated.
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> Mushthaq
>>>>>> --
>>>>>> Mushthaq Rumy
>>>>>> *Software Engineer*
>>>>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>>>>> Email : musht...@wso2.com
>>>>>> WSO2, Inc.; http://wso2.com/
>>>>>> lean . enterprise . middleware.
>>>>>>
>>>>>> <http://wso2.com/signature>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Thanuja Lakmal*
>>>>> Associate Technical Lead
>>>>> WSO2 Inc. http://wso2.com/
>>>>> *lean.enterprise.middleware*
>>>>> Mobile: +94715979891
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mushthaq Rumy
>>>> *Software Engineer*
>>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>>> Email : musht...@wso2.com
>>>> WSO2, Inc.; http://wso2.com/
>>>> lean . enterprise . middleware.
>>>>
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>> --
>>> Farasath Ahamed
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>> Mobile: +94777603866
>>> Blog: blog.farazath.com
>>> Twitter: @farazath619 <https://twitter.com/farazath619>
>>> <http://wso2.com/signature>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Implement a thirdparty web application using the sample in the doc

[Mushthaq Rumy]

Hi Ushani,

AFAIK you can pass null values to initiate a configurationContext as shown
in [1]. Something like below would do.

configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);

And alternatively you can also try this way.

String endPoint = SERVER_URL + "RemoteUserStoreManagerService";
RemoteUserStoreManagerServiceStub remoteUserStoreManagerServiceStub = new
RemoteUserStoreManagerServiceStub(endPoint);
AuthenticateStub.authenticateStub(userName, password,
remoteUserStoreManagerServiceStub);

remoteUserStoreManagerServiceStub.addRole(roleName, null, null);

I hope this helps.

[1] -
http://shazninazeer.blogspot.com/2014/10/creating-roles-and-assigning.html

Thanks & Regards,
Mushthaq

On Fri, Nov 3, 2017 at 4:33 PM, Ushani Balasooriya  wrote:

> Hi,
>
> I am going to implement a third party web application for Users and roles
> creation.
>
> Below are the steps I carried out.
>
> 1. I have taken the same travelocity web app and customizing it adding a
> form submission in the home which which loads after the login.
> 2. I have my jsp form with the correct servlet mapping.
> 3. In My method, I am trying to add a user role by referring the example
> given in this doc [1]
>
> [1] https://docs.wso2.com/display/IS520/Managing+Users+and+Roles+with+APIs
>
> My Question is,
>
> Without using the below approach to create a *ConfigurationContextFactory*
> and authenticating the logged in user, what is the correct way to proceed
> with my implementation? Since this is looking for the given
> client.axis2.xml.
>
>  try {
>configContext = ConfigurationContextFactory.
> createConfigurationContextFromFileSystem(
>  "repo", "repo/conf/client.axis2.xml");
>authstub = new AuthenticationAdminStub(configContext, SERVER_URL
>  + "AuthenticationAdmin");
>
>// Authenticates as a user having rights to add users.
>if (authstub.login("admin", "admin", null)) {
> cookie = (String) authstub._getServiceClient().getServiceContext().
> getProperty(
>   HTTPConstants.COOKIE_STRING);
>
>
> In order to call the addRole method in UserStoreManager class, I need to
> set correct value to the *realm*. Please correct me if my understanding
> is wrong since I am not much familiar with this. Appreciate your advice.
>
> *UserRealm realm = WSRealmBuilder.createWSRealm(SERVER_URL, cookie,
> configContext); *
> *UserStoreManager storeManager = realm.getUserStoreManager(); *
>
> Thanks,
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Exception when Publishing API in API Manager 2.1.0

[Mushthaq Rumy]

Hi Piriya,

Was there any error logged in the console. If so could you please attach
the error log?

Thanks & Regards,
Mushthaq

On Fri, Nov 10, 2017 at 5:27 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am working on a task where I have followed the below steps:
>
>
>- There is a SOAP backend which is hosted on Application Server and
>secured UT over Transport.
>- I have created a proxy service in ESB 5.0.0 having the SOAP backend
>as the endpoint of the proxy.
>- Then I followed this [1] blog to create an API in API Manager 2.1.0
>having the created ESB as the endpoint of the API.
>- According to the blog when I create the API, I couldn't publish this
>API. I could notice some exception in the Publisher UI.
>
> I am attaching a screenshot of the Publisher when it gives the exception.
> Could you please suggest me the reason for this exception and whether I
> have done something wrong here and how can I solve this issue?
>
> [1] https://medium.com/@shenavi21/exposing-a-soap-
> service-as-a-managed-rest-api-288676e06418
>
> Highly appreciate your suggestion on this.
>
> Thanks.
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

[Mushthaq Rumy]

Hi Pririya,

Seems like the operation you use is an incorrect operation. Was this
working fine in SOAPUI? Could you please check if *"readNinewells" *is the
correct operation?

Thanks & Regards,
Mushthaq

On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am creating an API in ESB 5.0.0 for GET Resource, where I have a secured
> SOAP backend service. Below is my synapse configuration of the API. I find
> some error logged in the console.
>
> 
> http://ws.apache.org/ns/synapse";
>  name="PatientAPI"
>  context="/patientapi">
>
>   
>scope="transport"
>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/"
>  xmlns:ser="http://service.
> sample.ninewells.com">
>   
>   
>  
> 
>  
>   
>
> 
> 
>
> 
>  
>  
>   scope="transport"/>
>  value="application/soap+xml"
>scope="axis2"
>type="STRING"/>
>  
> 
>https://.xx.xx.xx:xxx3/services/
> NinewellsPatientService"
> format="soap11"/>
> 
>  
>   
>   
>  value="application/json"
>scope="axis2"
>type="STRING"/>
>  
>   
>
> 
>
> There is a 500 Internal Server Error logged in the console.
>
> Below is the exception found.
> {"faultstring":"The endpoint reference (EPR) for the Operation not found
> is /services/DurdansPatientService and the WSA Action = null. If this EPR
> was previously reachable, please contact the server administrator."}
>
> Highly appreciate your advice on this.
>
> Thanks.
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

[Mushthaq Rumy]

Hi Piriya,

Can you attach the proxy WSDL file?

Thanks & Regards,
Mushthaq

On Sun, Nov 12, 2017 at 10:53 AM, Piriya Sivalingam  wrote:

> Hi Mushthaq,
>
> I tried the same operation in SOAPUI and it works fine. "readNinewells" is
> a correct operation.
>
> Thanks.
>
> On Sun, Nov 12, 2017 at 12:55 AM, Mushthaq Rumy  wrote:
>
>> Hi Pririya,
>>
>> Seems like the operation you use is an incorrect operation. Was this
>> working fine in SOAPUI? Could you please check if *"readNinewells" *is
>> the correct operation?
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam 
>> wrote:
>>
>>> Hi,
>>>
>>> I am creating an API in ESB 5.0.0 for GET Resource, where I have a
>>> secured SOAP backend service. Below is my synapse configuration of the API.
>>> I find some error logged in the console.
>>>
>>> 
>>> http://ws.apache.org/ns/synapse";
>>>  name="PatientAPI"
>>>  context="/patientapi">
>>>
>>>   
>>>  >>  scope="transport"
>>>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>>>  
>>> 
>>>http://schemas.
>>> xmlsoap.org/soap/envelope/"
>>>  xmlns:ser="http://service.sam
>>> ple.ninewells.com">
>>>   
>>>   
>>>  
>>> 
>>>  
>>>   
>>>
>>> 
>>> 
>>>
>>> 
>>>  
>>>  
>>>  >> scope="transport"/>
>>>  >>value="application/soap+xml"
>>>scope="axis2"
>>>type="STRING"/>
>>>  
>>> 
>>>https://.xx.xx.xx:xxx
>>> 3/services/NinewellsPatientService"
>>> format="soap11"/>
>>> 
>>>  
>>>   
>>>   
>>>  >>value="application/json"
>>>scope="axis2"
>>>type="STRING"/>
>>>  
>>>   
>>>
>>> 
>>>
>>> There is a 500 Internal Server Error logged in the console.
>>>
>>> Below is the exception found.
>>> {"faultstring":"The endpoint reference (EPR) for the Operation not found
>>> is /services/DurdansPatientService and the WSA Action = null. If this
>>> EPR was previously reachable, please contact the server administrator."}
>>>
>>> Highly appreciate your advice on this.
>>>
>>> Thanks.
>>>
>>> --
>>> Regards,
>>>
>>> *Piriya Sivalingam*
>>>
>>> *Software Engineer - Support Team*
>>>
>>> *WSO2*
>>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>>
>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Observing Missing Timestamp exception when doing creation via rest client

[Mushthaq Rumy]

Hi Thivya,

As Irham have suggested better to enable wire logs and check. Furthermore,
seems like it is checking for a time stamp in the header tag.

Thanks & Regards,
Mushthaq

On Wed, Nov 15, 2017 at 5:21 AM, Irham Iqbal  wrote:

> Hi Thuvya,
>
> You can enable the wire log and check the response headers and status code
> to narrow down this. follow the blog[1] to know about wire logs.
>
> [1] http://mytecheye.blogspot.com/2013/09/wso2-esb-all-
> about-wire-logs.html
>
> Thanks,
> Iqbal
>
> On Tue, Nov 14, 2017 at 8:10 PM, Thivya Mahenthirarasa 
> wrote:
>
>> Hi Dev,
>>
>> When I invoke POST method to create resource in a legacy(SOAP) backend.
>> (Backe end is secured)in my API of a WUM updated ESB500 pack from a rest
>> client, I'm observing exception as follows from the Backend soap service.
>> The Other Methods (DELETE/GET) are working fine.
>>
>>
>> wsse:InvalidSecurity
>>  Missing Timestamp
>>
>>
>> The resource of the API
>>
>> 
>>   
>>  > type="STRING"/>
>>  > type="STRING"/>
>>  > value="urn:postCMedi"/>
>>  
>> 
>>http://schemas.
>> xmlsoap.org/soap/envelope/">
>>   
>>  
>>   
>>   
>>  http://service.samp
>> le.central.com">
>> 
>>http://dto.service.
>> sample.central.com/xsd">
>>   ?
>>   ?
>>   ?
>>
>>http://dto.service.
>> sample.central.com/xsd">
>>   ?
>>   ?
>>
>>http://dto.service.sample.central.com/xsd";>
>>   ?
>>   ?
>>   ?
>>
>>http://dto.service.sample.central.com/xsd";>
>>   ?
>>   ?
>>   ?
>>
>>http://dto.service.sample.central.com/xsd";>?
>>http://dto.service.
>> sample.central.com/xsd">105665
>>http://dto.service.
>> sample.central.com/xsd">
>>   ?
>>   ?
>>   ?
>>
>> 
>>  
>>   
>>
>> 
>> 
>>  
>>  
>>  
>>  
>> 
>>https://192.168.55.160:94
>> 43/services/CentralPatientService" format="soap11"/>
>> 
>>  
>>   
>>   
>>  
>>  > scope="axis2" type="STRING"/>
>>  
>>   
>>
>>
>> WSDL location
>>
>> h*ttp://192.168.55.160:9763/services/CentralPatientService?wsdl*
>> <http://192.168.55.160:9763/services/CentralPatientService?wsdl>
>>
>> Could you please help to resolve this?
>>
>>
>>
>> --
>>
>> *Thivya Mahenthirarasa*
>>
>> *Software Engineer -Support Team | WSO2*
>>
>>
>> *Email: thi...@wso2.com *
>>
>> *Mobile: +94766461966 <+94%2076%20646%201966> <http://wso2.com/signature>*
>> *Web: http://wso2.com <http://wso2.com>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] (no subject)

[Mushthaq Rumy]

Hi Dilusha,

AFAIK, since this is scope based permission for resources, this should work
for both POST and DELETE resources even with the same user with the
Administrator role.

For example, if you create a scope with Administrator role and add this
scope to all 3 resources, you should be able to generate an access token
with the curl command.

Have you given the correct scope while generating the access token? If so
could please you provide the response of the access token generation curl?

Thanks & Regards,
Mushthaq

On Wed, Nov 15, 2017 at 4:54 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> The Administrator(role) has resource permission for DELETE and POST.
>
> First  I have assigned the same user to both resources. so that
> doesn't work for POST. But works for DELETE.
>
> After that, I created a new user (Admin_user) and assigned the same role
> (Administrator). I used that username and password to get the access token.
> I tested the POST resource with that access token. Now POST resource is
> working fine.
> Is this correct method?
>
> Thanks
> Dilusha.
>
>
>
> On Wed, Nov 15, 2017 at 3:51 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Dilusha,
>>
>> Please make sure you have the correct scope in the response of the token
>> generation.
>>
>> Thank you!
>>
>> On Wed, Nov 15, 2017 at 5:52 PM, Dilusha Alphonso 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am trying to add SCOPE to API manager 2.1.0. I have the user role. We
>>> have to give the resource permission for the particular role.I follow this
>>> link [1]
>>>
>>> 1. I created a new user in APIM management console using super tenant. (
>>> user is User_Administrator) I didn't give any permission to that user.
>>> 2. I assigned the roles to that user. ( user role is administrator).
>>> 3. After I added the scope of the resource  API in the publisher for
>>> roles.
>>> 4.I used the curl command to get the access token for that particular
>>> user.
>>> 5.After I got access token I used it in the curl command to access the
>>> resource.  The GET and DELETE are working fine. but POST is giving the
>>> following error response.
>>>
>>> {"fault":{"code":900910,"message":"The access token does not allow you
>>> to access the requested resource","description":"Access failure for
>>> API: /test/1.0.0, version: 1.0.0 status: (900910) - The access token does
>>> not allow you to access the requested resource"}}
>>>
>>> It will be great if any of you can suggest a solution for this.
>>>
>>>
>>> [1].https://wso2.com/library/articles/2017/01/article-an-ove
>>> rview-of-scope-management-with-wso2-api-manager/
>>>
>>>
>>> Thanks
>>> Dilusha
>>> --
>>>
>>>
>>> *Best Regards,Dilusha Alphonso*
>>>
>>> *Software Engineer - Support Team*
>>>
>>>
>>> *WSO2*
>>> *Mobile : *
>>>
>>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>>> <http://wso2.com/signature>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> <http://wso2.com/signature>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] Use of Thread.sleep in in between creation of two APIs

[Mushthaq Rumy]

Hi All,

While optimizing the APIM product build, I found a Thread.sleep() at [1].
Any particular reason for adding this. IMO we would not be needing this
since this does not wait for any response rather it just waits before
creating the next API. If there is no such specific reason, shall we remove
this? WDYT?

[1] -
https://github.com/mushthaq33/product-apim/blob/468ab801a4112d40c3a7bbddfcb7db21eae5a998/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/other/APIM710AllSubscriptionsByApplicationTestCase.java#L165

-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Use of Thread.sleep in in between creation of two APIs

[Mushthaq Rumy]

@Harsha - Thanks for the input. I have one more doubt. Why would a high
frequency of API creation cause errors? Since APIM should be able to handle
multiple create requests in parallel, it should not be a problem right?
Please correct me if I'm wrong.
However, I ran only that particular test case after removing that line and
it seems to be working fine. I will run the whole test integration module
and verify.

Thanks & Regards,
Mushthaq

On Sat, Nov 18, 2017 at 7:11 PM, Harsha Kumara  wrote:

>
>
> On Sat, Nov 18, 2017 at 6:50 PM, Prasanna Dangalla 
> wrote:
>
>> HI Rumy,
>>
>> In this code, it creates the API and then does a getAPI call as well.
>> Then changing the lifecycle state as well. After changing the lifecycle
>> state is does a verification as well. After all these only this
>> Thread.sleep is done. Hence IMO we can remove this Thread.sleep.
>>
> Yes we should be able to remove it. I believe this isn't going with a path
> which uses indexed API to retrived. But sometimes we noticed calling the
> API creation APIs in high frequency can cause errors. So it's better to do
> a few test rounds after you remove it and confirm. My doubt is, there might
> be a reason for those delays. It mostly the calling frequency. Anyway let's
> check and verify.
>
>>
>> Thanks
>> Prasanna
>>
>> *Prasanna Dangalla*
>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>>
>> *cell: +94 718 11 27 51*
>> *twitter: @prasa77*
>>
>> On Sat, Nov 18, 2017 at 1:36 PM, Mushthaq Rumy  wrote:
>>
>>> Hi All,
>>>
>>> While optimizing the APIM product build, I found a Thread.sleep() at
>>> [1]. Any particular reason for adding this. IMO we would not be needing
>>> this since this does not wait for any response rather it just waits before
>>> creating the next API. If there is no such specific reason, shall we remove
>>> this? WDYT?
>>>
>>> [1] - https://github.com/mushthaq33/product-apim/blob/468ab801a411
>>> 2d40c3a7bbddfcb7db21eae5a998/modules/integration/tests-integ
>>> ration/tests-backend/src/test/java/org/wso2/am/integration/
>>> tests/other/APIM710AllSubscriptionsByApplicationTestCase.java#L165
>>>
>>> --
>>> Mushthaq Rumy
>>> *Software Engineer*
>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>> Email : musht...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>> <http://wso2.com/signature>
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Use of Thread.sleep in in between creation of two APIs

[Mushthaq Rumy]

Got it. Thanks Harsha for the clarification

Thanks & Regards,
Mushthaq

On Sat, Nov 18, 2017 at 9:50 PM, Harsha Kumara  wrote:

>
>
> On Sat, Nov 18, 2017 at 9:32 PM, Mushthaq Rumy  wrote:
>
>> @Harsha - Thanks for the input. I have one more doubt. Why would a high
>> frequency of API creation cause errors? Since APIM should be able to handle
>> multiple create requests in parallel, it should not be a problem right?
>> Please correct me if I'm wrong.
>>
> "We ourselves have observed the registry deadlocks when testing the
> product for API creation/publishing under high concurrency and high
> speed. An API creation causes registry writes and APIM DB writes as well.
> Which together causes a number of SQL inserts into the DBs. And on top of
> this we use registry transactions as well. So basically an API 
> creation/publishing
> is a heavy operation in terms of DB writes. So we cannot expect high
> response times for this anyway." Extracted by NuwanD's reply.
>
>> However, I ran only that particular test case after removing that line
>> and it seems to be working fine. I will run the whole test integration
>> module and verify.
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Sat, Nov 18, 2017 at 7:11 PM, Harsha Kumara  wrote:
>>
>>>
>>>
>>> On Sat, Nov 18, 2017 at 6:50 PM, Prasanna Dangalla 
>>> wrote:
>>>
>>>> HI Rumy,
>>>>
>>>> In this code, it creates the API and then does a getAPI call as well.
>>>> Then changing the lifecycle state as well. After changing the lifecycle
>>>> state is does a verification as well. After all these only this
>>>> Thread.sleep is done. Hence IMO we can remove this Thread.sleep.
>>>>
>>> Yes we should be able to remove it. I believe this isn't going with a
>>> path which uses indexed API to retrived. But sometimes we noticed calling
>>> the API creation APIs in high frequency can cause errors. So it's better to
>>> do a few test rounds after you remove it and confirm. My doubt is, there
>>> might be a reason for those delays. It mostly the calling frequency. Anyway
>>> let's check and verify.
>>>
>>>>
>>>> Thanks
>>>> Prasanna
>>>>
>>>> *Prasanna Dangalla*
>>>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>>>> lean.enterprise.middleware
>>>>
>>>>
>>>> *cell: +94 718 11 27 51*
>>>> *twitter: @prasa77*
>>>>
>>>> On Sat, Nov 18, 2017 at 1:36 PM, Mushthaq Rumy 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> While optimizing the APIM product build, I found a Thread.sleep() at
>>>>> [1]. Any particular reason for adding this. IMO we would not be needing
>>>>> this since this does not wait for any response rather it just waits before
>>>>> creating the next API. If there is no such specific reason, shall we 
>>>>> remove
>>>>> this? WDYT?
>>>>>
>>>>> [1] - https://github.com/mushthaq33/product-apim/blob/468ab801a411
>>>>> 2d40c3a7bbddfcb7db21eae5a998/modules/integration/tests-integ
>>>>> ration/tests-backend/src/test/java/org/wso2/am/integration/t
>>>>> ests/other/APIM710AllSubscriptionsByApplicationTestCase.java#L165
>>>>>
>>>>> --
>>>>> Mushthaq Rumy
>>>>> *Software Engineer*
>>>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>>>> Email : musht...@wso2.com
>>>>> WSO2, Inc.; http://wso2.com/
>>>>> lean . enterprise . middleware.
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Harsha Kumara
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94775505618 <+94%2077%20550%205618>
>>> Blog:harshcreationz.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Cannot see the response when invoking the service

[Mushthaq Rumy]

Hi Buddhimala,

By looking at the ESB wire-log, it seems like the data is converted to
JSON. Were there any errors logged in the APIM console or in the ESB
console?

Thanks & Regards,
Mushthaq

On Tue, Nov 21, 2017 at 10:07 AM, Buddhimala Ranasinghe  wrote:

> Hi All,
>
> I'm trying to implement the scenario as shown in the following diagram.
> [image: Inline image 1]
>
> The WSDL for my BE can be found in the following location.
> http://192.168.55.160:9763/services/NawalokaPatientService?wsdl
>
> I created an API with CRUD operations inside API Manager. For GET method
> I'm sending the request to the "read" method in my legacy BE. The sample
> response from my BE for the request will be as follows.
>
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
> 1.0.xsd">
>  http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd">
> 2017-11-20T10:30:41.878Z
> 2017-11-20T10:35:41.878Z
>  
>   
>
>
>   http://service.sample.nawaloka.com";>
>  http://dto.
> service.sample.nawaloka.com/xsd" xmlns:ax25="http://service.
> sample.nawaloka.com/xsd" xmlns:xsi="http://www.w3.org/
> 2001/XMLSchema-instance">
> 
>?
>?
>?
> 
> 
> 
>?
>?
>?
> 
> 
>?
>?
>?
> 
> abc
> a...@abc.com
> 
>M.Rajan
>?
>?
> 
>  
>   
>
> 
>
> But my response should be in JSON format so that I tried to convert the
> response into JSON using " value="application/json"/>"
>
> But my problem is, in my response to the client, it should only contain 
> *insurer
> details, parentGuardian, patientContact, patientFullName and patientId*.
> Therefore, I tried of defining a custom payload as follows.
>
> 
>
>   
> {
> "patient":{
> "insurer": "$1",
> "parentGuardian": "$2",
> "patientContact": "$3",
> "patientFullName": "$4",
> "patientId": "$5"
>
>
> }
> }
> 
>   
>  
>  
>  
>  
>  
>   
>
>
>
> But, when I invoke the service, I cannot see any response at client side.
> I'm attaching the wirelogs for my ESB and APIM.
>
> Can you please help me to solve this problem?Where am I doing wrong?
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <+94%2077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] <https://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Handler in ESB proxy service

[Mushthaq Rumy]

Hi Piriya,

Have you included the JAR or the OSGI bundle in your ESB pack? If not could
you please add it. Can you try adding the handler to your proxy through
management console?

Thanks & Regards,
Mushthaq

On Tue, Nov 21, 2017 at 4:55 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I have a scenario where I have to decode the JWT token at the ESB layer
> and fetch the user role from that token and validate at the ESB. I have a
> handler to decode the generated JWT token and extract the role. I have
> tried different ways in order to call that handler in my ESB proxy service.
>
> 1. Added the below code inside the synapse configuration of my proxy
> service located at /repository/deployment/server/synapse-
> configs/default/proxy-services.
>
> 
>   
>
>
> 2. Added the above code into the axis2.xml file located at
> /repository/conf/axis2/axis2.xml.
>
> I start the server in debug mode and noticed that handler does not get
> executed.
>
> And according to the first method, whenever I make any changes to the
> proxy, that (handler) gets removed. If I am not wrong, this is the expected
> behavior.
>
>
> Could you please suggest how can I call the handler inside my ESB proxy
> service?
>
> The ESB version is ESB 5.0.0.
>
> Thanks,
> Piriya
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [APIM]Cannot login to APIM Management console with admin credentials

[Mushthaq Rumy]

Hi Isuru,

Seems like the java version is causing this issue. This issue is there with
java JDK 8u151. Please refer [1] for more details.

[1] - [Important][Critical] None of WSO2 products are working with
latest JDK [Was: GZIP decoding issue in APIM/EI when deployed in MC]

Thanks & Regards,
Mushthaq

On Wed, Nov 22, 2017 at 3:35 PM, Irham Iqbal  wrote:

> Hi Isuru,
>
> The reason might the java version you're using.
>
> You can update the Owasp.CsrfGuard.Carbon.properties file, which is in
> $APIM_HOME/repository/conf/security folder with the bellowing entry to
> ignore this error, IMO it's better if you use the proper java version.
> org.owasp.csrfguard.unprotected.mgtconsolelogin=%
> servletContext%/carbon/admin/*
>
> Thanks,
> Iqbal
>
> On Wed, Nov 22, 2017 at 3:08 PM, Isuru Uyanage  wrote:
>
>> Hi All,
>>
>> I'm using wum updated pack (wso2am-2.1.0.1511201090302) for API Manager.
>> After APIM server is started with the fresh pack, I can navigate to
>> Management Console. But once I'm trying to log in with admin credentials, I
>> cannot log in. The error is as below.
>>
>> Error: 403 Forbidden
>> JavaLogger potential cross-site request forgery (CSRF) attack thwarted
>> (user:, ip:10.100.5.136, method:POST,
>> uri:/carbon/admin/login_action.jsp, error:required token is missing from
>> the request)
>>
>> Affected Product Version:
>> wum updated pack: wso2am-2.1.0.1511201090302.zip
>>
>> Environment details and versions:
>>
>> macOS High Sierra
>> Version 10.13.1
>> Google Chrome: Version 62.0.3202.94 (Official Build) (64-bit)
>> Firefox: 57.0
>>
>> Any thoughts about this are highly appreciated.
>>
>>
>> *Thanks and Best Regards,*
>>
>> *Isuru Uyanage*
>> *Software Engineer - QA | WSO2*
>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>> <https://www.linkedin.com/in/isuru-uyanage/>*
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Error occurs with Response caching enabled.

[Mushthaq Rumy]

> ndMediator.java:118)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:97)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:338)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> TRequestHandler.java:90)
>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>> stHandler.java:56)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>> Message(Axis2SynapseEnvironment.java:304)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
>> Message(SynapseCallbackReceiver.java:554)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
>> e(SynapseCallbackReceiver.java:188)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
>> tWorker.java:262)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> Caused by: org.apache.axis2.AxisFault: Payload could not be written as
>> JSON.
>> at org.apache.synapse.commons.json.JsonUtil.writeAsJson(JsonUti
>> l.java:276)
>> at org.apache.synapse.commons.json.JsonFormatter.writeTo(JsonFo
>> rmatter.java:62)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> submitResponse(PassThroughHttpSender.java:573)
>> at org.apache.synapse.transport.passthru.PassThroughHttpSender.
>> invoke(PassThroughHttpSender.java:264)
>>
>> Can you please help me to solve this problem?
>>
>> Thanks
>>
>> --
>>
>>
>> *Buddhimala Ranasinghe*
>> Software Engineer-Support Team | WSO2
>> Emil: buddhim...@wso2.com
>> Mobile:+94771563138 <+94%2077%20156%203138>
>> Web:http://wso2.com
>> [image: https://wso2.com/signature] <https://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Krishan Wijesena*
> Software Engineer | WSO2
>
> Email : krish...@wso2.com
> Mobile : +94776219923 <+94%2077%20621%209923>
> WSO2 Inc : http://wso2.com
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [WUM] wum diff copying file to the current relative path except for .wum-wso2 directory

[Mushthaq Rumy]

Hi Malith,

+1 for creating the diff archive, summery and all the wum related files in
the .wum-wso2 directory as this will make the user experience better.

Thanks & Regards,
Mushthaq

On Wed, Nov 29, 2017 at 9:34 AM, Malith Munasinghe  wrote:

> Hi All,
>
> While using WUM diff command to compare two updates it was noted that both
> the Diff archive and Diff summary is getting created in the current working
> directory.
>
> IMO it would be better if we created those diff files in ~/.wum-wso2/ as
> well since this will increase the user experience by limiting wum related
> activities within the wum home directory.
>
> WDYT ?
>
> Regards,
> Malith
>
> --
> Malith Munasinghe | Senior Software Engineer
> M: +94 (71) 9401122 <+94%2071%20940%201122>
> E: mali...@wso2.com
> W: http://wso2.com
> <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] How to implement a Notification mechanism for informing subscribers about API changes using WSO2 APIM 2.1.0

[Mushthaq Rumy]

Hi Shanika,

How did you create user as API subscriber? If you have created the
subscriber in the Management Console, you need to add the subscriber's
email in the subscriber user profile in Management Console. You can find
the user profile when you list the users in the management console as below.

[image: Inline image 1]

You need to click user profile of the particular subscriber, go to the
default profile and then give the email address.

Thanks & Regards,
Mushthaq

On Wed, Nov 29, 2017 at 2:46 PM, Shanika Wickramasinghe 
wrote:

> Kind reminder on this
>
> Thankyou,
> Shanika.
>
> On Fri, Nov 24, 2017 at 3:08 PM, Shanika Wickramasinghe  > wrote:
>
>>
>> Hi All,
>>
>> I am trying to implement a scenario with the WSO2 APIM 2.1.0 to cover API
>> life cycle Management. There I want to implement a Notification mechanism
>> for informing subscribers about API changes.
>>
>> Steps that I followed are as below.  (If I have used a wrong process
>> please correct and provide feedback)
>>
>> 1. Created a user as a API publisher
>> 2. Created a user as a API subscriber
>> 3. Login to the API publisher as the publisher and create and publish a
>> API with version 1.0
>> 4. Login to the API store as a subscriber and subscribe to that API
>> 5. Login to the API publisher as publisher and create a new version for
>> the previous API as version 2.0
>> 6. Subscriber who is subscribed to the API version 1.0 need to get a
>> email notification to mentioning about the new API version change
>>
>> After completing up to step 5 to implement this notification part I
>> followed [1]. But I could not find enough information to find the the
>> correct flow on where we need to configure the subscribers email and how to
>> do this. Appreciate your feedback on how to do this.
>>
>> Also what is referred as API provider email in [1]
>>
>> [1]. https://docs.wso2.com/display/AM210/Enabling+Notifications
>>
>>
>> Thankyou,
>> Shanika.
>> --
>> *Shanika Wickramasinghe*
>> Software Engineer - QA Team
>>
>> Email: shani...@wso2.com
>> Mobile  : +94713503563 <+94%2071%20350%203563>
>> Web : http://wso2.com
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> *Shanika Wickramasinghe*
> Software Engineer - QA Team
>
> Email: shani...@wso2.com
> Mobile  : +94713503563 <+94%2071%20350%203563>
> Web : http://wso2.com
>
> <http://wso2.com/signature>
>



-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [APIM] [2.1.0] Read tenant registry config from jaggery

[Mushthaq Rumy]

Hi Viduranga,

You can achieve this by adding a new method in a file in the store/modules
directory to get the particular value from the registry path.
Then you can call this function from the
store/site/blocks/api/api-info/block.jag file as follows,

Assuming that your function name is getAuthorization(domain)

jagg.module().getAuthorization(domain);

The assign it as follows,
{
"title": i18n.localize("API
Console"),
"body": [
{
"name": "api/swagger",
"inputs": {
"api": api,
"subscriptions":
subscriptions,
   * "authorization": *
}
}
]
}


Then you can simply access this value from the template.jag as
outputs.authorization .

Hope this helps.

Thanks & Regards,
Mushthaq

On Thu, Dec 7, 2017 at 10:48 AM, Viduranga Gunarathne 
wrote:

> Hi,
>
> I'm working on APIM 2.1.0 and I need to read a configuration in the tenant
> registry that is specific to each tenant, from the jaggery layer so that it
> can be displayed in the Store UI.
>
> Any tips on how to do this?
>
> Also, The media type of the "tenant-conf" is json and can that be accessed
> as a json object or is it returned as a resource and we have to convert it
> to a json object at the jaggery level ?
>
> Thanks in advance!
> Viduranga.
> --
> Regards,
>
> *Viduranga Gunarathne*
>
> *Software Engineer Intern*
>
>
> *WSO2*
> Email : vidura...@wso2.com
> Mobile : +94712437484 <+94%2071%20243%207484>
> Web : http://wso2.com
> [image: https://wso2.com/signature] <https://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] API Manager with Identity Server as Key Manager - IS secondary user store to connect to APIM Store

[Mushthaq Rumy]

Hi Thomas,

Do you have special characters in your password? If so could you please try
encoding the url characters in your password and execute the curl command
again?

Thanks & Regards,
Mushthaq

On Wed, Jan 17, 2018 at 7:11 PM, Thomas LEGRAND <
thomas.legr...@versusmind.eu> wrote:

> Hello,
>
> I configured the Identity Server (IS) to be the Key Manager of the API
> Manager (APIM). In the IS, I configured a secondary user store where I will
> have my users of my applications. But, I think I missed something because
> when I want to generate a OAuth token for a user stored in this secondary
> user store, I have an error:
>
> My request:
>
> curl -k -d "grant_type=password&username=&password="
> -H "Authorization: Basic "
> https://apim:8243/token
>
> The response:
>
> {"error_description":"Authentication failed for @carbon.super","
> error":"invalid_grant"}.
>
> In the application in the store of the APIM, "Password" is ticked so the
> grant_type is right.
> And I tried with the following pattern for the :
> - 
> - /
> - \
>
> Can you help me? How can I ensure that the APIM uses all of the user
> stores from the IS.
>
> Regards,
>
> Thomas
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Setting up primary and secondary logins

[Mushthaq Rumy]

This is getting reproduced to me as well. Even appending the tenant domain
does not work. Seems like we will have to fix this.

Thanks,  & Regards,
Mushthaq

On Tue, Jan 23, 2018 at 7:26 PM, Isuru Uyanage  wrote:

> Hi Chamin,
>
> I provided the below details in self-signup to the API Store[1]. When I
> provide the username and password as usual I could log in.
>
> As per doc, by above configuration enabled, user should be able to
> login to the API Store by providing email address as well as the username.
> Therefore I provided the email address as the username used in self-sign up
> process in order to login to the API Store. Please correct me if I have
> done anything wrong.
>
> [1] - signup.png
>
>
> Thanks,
> Isuru
>
>
>
>
> *Thanks and Best Regards,*
>
> *Isuru Uyanage*
> *Software Engineer - QA | WSO2*
> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
> <https://www.linkedin.com/in/isuru-uyanage/>*
>
>
>
>
> On Tue, Jan 23, 2018 at 6:56 PM, Chamin Dias  wrote:
>
>> Did you provide the tenant domain in the user name? Normally this might
>> happen when we do not specify the tenant domain.
>>
>> On Tue, Jan 23, 2018 at 6:46 PM, Isuru Uyanage  wrote:
>>
>>> Hi All,
>>>
>>> I'm configuring the setup for primary and secondary logins to the API
>>> Store as in [1]. As per the doc, it says users can use either username or
>>> email address in order to login to the API Store. I followed the below
>>> steps.
>>>
>>> 1. Self-signed up to the API Store.
>>> 2. As in the doc, enabled login config property in
>>> /repository/conf/api-manager.xml file.
>>>
>>> 
>>> 
>>>  
>>> 
>>> 
>>>  http://wso2.org/claims/emailaddress
>>> 
>>>  
>>>
>>> 3. Restarted the APIM server.
>>> 4. Tried to login to API Store with the email address provided.
>>>
>>> I get the following error.
>>>
>>> ERROR - APIStoreHostObject Invalid tenant domain.
>>>
>>> Any feedback would be appreciated if I've missed anything.
>>>
>>> [1] - https://docs.wso2.com/display/AM2xx/Maintaining+Logins+and
>>> +Passwords
>>> Section: Setting up primary and secondary logins
>>> Product: apim-2.1.0-update 6
>>>
>>>
>>> *Thanks and Best Regards,*
>>>
>>> *Isuru Uyanage*
>>> *Software Engineer - QA | WSO2*
>>> *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
>>> *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
>>> <https://www.linkedin.com/in/isuru-uyanage/>*
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Chamin Dias
>> Mobile : 0716097455
>> Email : cham...@wso2.com
>> LinkedIn : https://www.linkedin.com/in/chamindias
>>
>>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] WSO2 API Manager 2.1.0-update13 Released !

[Mushthaq Rumy]

*The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update13 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 RequestsFor more information on WSO2 API
Manager please visit http://wso2.com/products/api-manager
<http://wso2.com/products/api-manager>. Also, take a look at the online
product documentation
<https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>.*

* Distributionswso2am-2.1.0-update13.zip
<https://github.com/wso2/product-apim/releases/download/v2.1.0-update13/wso2am-2.1.0-update13.zip>wso2am-analytics-2.1.0-update8.zip
<https://github.com/wso2/analytics-apim/releases/download/v2.1.0-update8/wso2am-analytics-2.1.0-update8.zip>*

*How to Run*

   *1. Extract the downloaded zip2. Go to the bin directory in the
   extracted folder3. Run the wso2server.sh or wso2server.bat as appropriate4.
   Launch a web browser and navigate to https://localhost:9443/publisher
   <https://localhost:9443/publisher> to access the API publisher webapp5.
   Navigate to https://localhost:9443/store <https://localhost:9443/store> to
   access the API store6. Navigate to https://localhost:9443/admin
   <https://localhost:9443/admin> to access Admin Portal7. Use "admin",
   "admin" as the username and password to login as an admin*

*Bug Fixes And Improvements in 2.1.0-update13*

   *- JIRA <https://wso2.org/jira/issues/?filter=14526>- GitHub
   (Product-apim
   <https://github.com/wso2/product-apim/milestone/27?closed=1>),
   (Carbon-apimgt
   <https://github.com/wso2/carbon-apimgt/milestone/15?closed=1>),
   (analytics-apim
   <https://github.com/wso2/analytics-apim/milestone/2?closed=1>)*






* Known IssuesAll the open issues pertaining to WSO2 API Manager are
reported at the following location: - JIRA
<https://wso2.org/jira/issues/?filter=14454>- GitHub (Product-apim
<https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue+label%3A2.2.0>),
(Carbon-apimgt
<https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>),
(analytics-apim
<https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) How
You Can ContributeMailing ListsJoin our mailing list and correspond with
the developers directly. - Developer List: dev@wso2.org  |
Subscribe | Mail Archive- User List: u...@wso2.org  |
Subscribe | Mail ArchiveReporting IssuesWe encourage you to report issues,
documentation faults, and feature requests regarding WSO2 API Manager
through the public API Manager Git Repo
<https://github.com/wso2/product-apim/issues>. -- The WSO2 API Manager Team
--*


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Committers += Dinusha Dissanayake

[Mushthaq Rumy]

Congratulations Dinusha :)

Thanks & Regards,
Mushthaq

On Thu, Mar 8, 2018 at 3:48 PM, Bhathiya Jayasekara 
wrote:

> Hi all,
>
> Its my pleasure to announce Dinusha Dissanayake as a WSO2 Committer. He
> has been a valuable contributor to WSO2 API Manager.
>
> Congratulations Dinusha and keep up the good work!!.
>
> Thanks,
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] WSO2 API Manager 2.1.0-update14 Released !

[Mushthaq Rumy]

*The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update14 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 RequestsFor more information on WSO2 API
Manager please visit http://wso2.com/products/api-manager
<http://wso2.com/products/api-manager>. Also, take a look at the online
product documentation
<https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>.*

* Distributionswso2am-2.1.0-update14.zip
<https://github.com/wso2/product-apim/releases/download/v2.1.0-update14/wso2am-2.1.0-update14.zip>wso2am-analytics-2.1.0-update9.zip
<https://github.com/wso2/analytics-apim/releases/download/v2.1.0-update9/wso2am-analytics-2.1.0-update9.zip>*

*How to Run*

   *1. Extract the downloaded zip2. Go to the bin directory in the
   extracted folder3. Run the wso2server.sh or wso2server.bat as appropriate4.
   Launch a web browser and navigate to https://localhost:9443/publisher
   <https://localhost:9443/publisher> to access the API publisher webapp5.
   Navigate to https://localhost:9443/store <https://localhost:9443/store> to
   access the API store6. Navigate to https://localhost:9443/admin
   <https://localhost:9443/admin> to access Admin Portal7. Use "admin",
   "admin" as the username and password to login as an admin*

*Bug Fixes And Improvements in 2.1.0-update14*

   *- JIRA <https://wso2.org/jira/issues/?filter=14528>- GitHub
   (Product-apim
   <https://github.com/wso2/product-apim/milestone/30?closed=1>),
   (Carbon-apimgt
   <https://github.com/wso2/carbon-apimgt/milestone/16?closed=1>),
   (analytics-apim
   <https://github.com/wso2/analytics-apim/milestone/3?closed=1>)*






* Known IssuesAll the open issues pertaining to WSO2 API Manager are
reported at the following location: - JIRA
<https://wso2.org/jira/issues/?filter=14454>- GitHub (Product-apim
<https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue+label%3A2.2.0>),
(Carbon-apimgt
<https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>),
(analytics-apim
<https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) How
You Can ContributeMailing ListsJoin our mailing list and correspond with
the developers directly. - Developer List: dev@wso2.org  |
Subscribe | Mail Archive- User List: u...@wso2.org  |
Subscribe | Mail ArchiveReporting IssuesWe encourage you to report issues,
documentation faults, and feature requests regarding WSO2 API Manager
through the public API Manager Git Repo
<https://github.com/wso2/product-apim/issues>. -- The WSO2 API Manager Team
--*

-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Review and merge PR for logs required for message roundtrip analysis

[Mushthaq Rumy]

Hi Dushani,

Added some comments to the carbon-apimgt PR. Please fix those.

Thanks & Regards,
Mushthaq

On Fri, Mar 9, 2018 at 6:57 PM, Dushani Wellappili 
wrote:

> Hi APIM team and IS team,
>
> Highly appreciate if you can review the two PRs [1] and [2] which include
> the newly added logs which are used to identify the message hops and their
> latencies in each node during an API invocation in WSO2 APIM. Please refer
> [3] for documentation and mail thread [4] for more information.
>
> [1] - carbon-apimgt  - https://github.com/wso2/carbon-apimgt/pull/5184
> [2] - identity-inbound-auth-oauth - https://github.com/wso2-
> extensions/identity-inbound-auth-oauth/pull/849
> [3] - Documentation - https://docs.google.com/docu
> ment/d/10-p1B9bORXHMG71XQfELxFQc0uHUOxlfD6TsvZBhuPs/edit?usp=sharing
> [4] - Mail Thread - "Message roundtrip analysis of distributed deployment
> of WSO2 APIM"
>
> Thanks,
> Regards,
>
>
> *Dushani Wellappili*
> Software Engineer - WSO2
>
> Email : dusha...@wso2.com
> Mobile : +94779367571 <+94%2077%20936%207571>
> Web : https://wso2.com/
>
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] WSO2 API Manager 2.2.0 Released!

[Mushthaq Rumy]

The WSO2 API Management team is pleased to announce the release of version
2.2.0 of the open source WSO2 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
<https://docs.wso2.com/display/AM220/WSO2+API+Manager+Documentation>.
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 provider webapp
   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 login as an admin


New Features

WSO2 API Manager version 2.2 is part of WSO2’s Spring 2018 Release
<https://wso2.com/about/news/wso2-delivers-platform-wide-support-for-gdpr-with-new-product-developments/>
which includes new features and updates across all products, solutions, and
services, that together empower organizations to rapidly comply with GDPR.
For more information on new features please visit
https://docs.wso2.com/display/AM220/About+this+Release
Bug Fixes And Improvements

   -

   JIRA <https://wso2.org/jira/issues/?filter=14532>
   -

   GitHub (product-apim
   
<https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A%3E2017-02-06+-label%3A3.0.0+>),
   (carbon-apimgt
   
<https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A%3E2017-02-06+-label%3A3.0.0+>),
   (analytics-apim
   
<https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A%3E2017-02-06+-label%3A3.0.0+>
   )

Known Issues

   -

   JIRA <https://wso2.org/jira/issues/?filter=14533>
   -

   GitHub (product-apim
   
<https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue+label%3A2.2.0>),
   (carbon-apimgt
   
<https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>),
   (analytics-apim
   <https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>)

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List : dev@wso2.org | Subscribe | Mail Archive
   <http://wso2.org/mailarchive/dev/>
   -

   User List : u...@wso2.org | Subscribe | Mail Archive
   <http://wso2.org/mailarchive/user/>

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo
<https://github.com/wso2/product-apim/issues>.

-- The WSO2 API Manager Team --


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Microgateway doesnt sync APIs as expected

[Mushthaq Rumy]

ycle.java:482)
> at
> org.wso2.carbon.governance.registry.eventing.handlers.GovernanceEventingHandler.invokeAspect(GovernanceEventingHandler.java:344)
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.invokeAspect(HandlerManager.java:2792)
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.invokeAspect(HandlerLifecycleManager.java:518)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.invokeAspect(EmbeddedRegistry.java:2607)
> at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.invokeAspect(CacheBackedRegistry.java:510)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.invokeAspect(UserRegistry.java:1952)
> at
> org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:829)
> at
> org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:808)
> at
> org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:4097)
> at
> org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:281)
> at
> org.wso2.carbon.apimgt.micro.gateway.api.synchronizer.util.APIMappingUtil.apisUpdate(APIMappingUtil.java:97)
> at
> org.wso2.carbon.apimgt.micro.gateway.api.synchronizer.APISynchronizer.synchronizeApis(APISynchronizer.java:183)
> at
> org.wso2.carbon.apimgt.micro.gateway.api.synchronizer.APISynchronizer.completedInitialization(APISynchronizer.java:102)
> at
> org.wso2.carbon.apimgt.micro.gateway.common.GatewayListenerNotifier.notifyListeners(GatewayListenerNotifier.java:44)
> at
> org.wso2.carbon.apimgt.micro.gateway.tenant.initializer.listener.ServerStartupListener$ScheduledThreadPoolExecutorImpl.run(ServerStartupListener.java:120)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
>
> Thank you,
>
> --
> Nadeesha Gamage
> Lead Solutions Engineer
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] WSO2 Publish & Subscribe

[Mushthaq Rumy]

Hi Shib,

Could you please try entering the request URL in a new tab and add a
security exception for your request URL? This seems to be a security
certificate issue.

Thanks & Regards,
Mushthaq

On Wed, Jun 6, 2018 at 11:01 PM shibsankar  wrote:

> when I  do a *Try Now *testing in API Console of WSO2 Store, I do not
> receive a valid response.  Please see the *Try Now *screenshot attached.
>
>
> Regarding Log:  I was looking at the *wso2carbon.log*  at the same time
> when I was trying out API invocation in WSO2 store.
>
> There is no log printed in *wso2carbon.log*  for this activity.
>
> Why there is no valid response?
>
> Regards
> Shib
>
>
>
> On Wed, Jun 6, 2018 at 6:07 PM, Dinusha Dissanayake 
> wrote:
>
>> Hi Shib,
>>
>> When you are creating the API you are using the actual backend URL of the
>> service as the production endpoint of the API.
>> But when you are using API Manager, you actual backend is getting proxy
>> and the service is exposed via APIM gateway with  security and throttling
>> facilities for the API.
>> Hence now the service is exposed via the APIM gateway.
>> That is why you see two different URLs in publisher and store production
>> endpoints.
>>
>> (http://{host}:8280 and https://{host}:8243 are gateway urls.)
>>
>> Since you are unable to obtain a response, there seems to be an issue.
>> Could you please send us the error log in the server when invoking the
>> API. That would help us to narrow down the issue.
>>
>> Thanks,
>> DinushaD.
>>
>>
>> On Wed, Jun 6, 2018 at 5:43 PM, shibsankar  wrote:
>>
>>> Hi,
>>>
>>> *My Objective: *
>>>
>>> I  have published a service in WSO2 Publish.  Now I  am trying to test
>>> this service from WSO2 Store API console.
>>>
>>> *Issue : * API console in WSO2 Store not returning result when invoking
>>> service.
>>>
>>>
>>> *Troubleshooting :*
>>>
>>> To my surprise, when I view the published service from WSO2 store, I
>>> see different production URL of the service than what is in Publishing.
>>> What has gone wrong ?
>>>
>>>
>>> For your convenience,  I'm attaching a screenshot of Publish and Store.
>>> Could you please help to fix this issue.
>>>
>>>
>>> Regards
>>> Shib
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dissanayake
>> Software Engineer
>> WSO2 Inc
>> Mobile: +94712939439
>> <https://wso2.com/signature>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Mushthaq Rumy]

Hi All,

I have tested the following scenarios.

- Basic API creation flow with the creator role.
- Publishing an API with publisher role.
- User sign-up.
- Password recovery with super tenant and other tenants.

No blockers found. Hence [+] Stable - go ahead and release.

Thanks & Regards,
Mushthaq

On Mon, Sep 17, 2018 at 1:43 PM Bhathiya Jayasekara 
wrote:

> Hi,
>
> I tested the following areas and no blockers were found.
>
> - Semi manual client registration
> - Grant types
> - Scopes
> - GDPR
>
> Hence, +1 for the release.
>
> Thanks,
> Bhathiya
>
>
>
>
> On Mon, Sep 17, 2018 at 12:42 PM Praminda Jayawardana 
> wrote:
>
>> Hi,
>>
>> Tested below scenarios,
>>
>> 1. Basic API creation and publishing with roles.
>> 2. Micro gateway with labels
>> 3. Micro gateway stat publishing
>> 4. Micro gateway throttling with both oauth and jwt tokens
>> 5. Dynamic SSL certificates
>>
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Praminda
>>
>> On Mon, Sep 17, 2018 at 11:50 AM Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> Tested the following scenarios.
>>>
>>> - JWT generation in API Manager
>>> - API Micorgateway generation using a Swagger Imported API
>>> - API Microgateway API invocation with a JWT and without a subscription
>>> (JWT validation only)
>>> - API Microgateway run on VM/Docker
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thank you!
>>>
>>> On Mon, Sep 17, 2018 at 11:26 AM Ishara Cooray  wrote:
>>>
>>>> Tested the following.
>>>>
>>>> Store REST API
>>>> External Stores
>>>> Store tag listing and tagwiseMode
>>>>
>>>> [+] Stable - go ahead and release
>>>>
>>>>
>>>> Thanks & Regards,
>>>> Ishara Cooray
>>>> Senior Software Engineer
>>>> Mobile : +9477 262 9512
>>>> WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>>>
>>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>>
>> *Praminda Jayawardana*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> Mobile : +94 (0) 716 590918
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Technical Lead,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Could not retrieve records based on tenant_Id

[Mushthaq Rumy]

Hi Ambujaa,

As Dushani has mentioned you can find the tenant ID from the AM_SUBSCRIBER
table. You could do this by joining the AM_APPLICATION and AM_SUBSCRIBER
table and get the tenant ID.

Thanks & Regards,
Mushthaq

On Mon, Oct 1, 2018 at 1:43 PM Dushani Wellappili  wrote:

> Hi Ambujaa,
>
> If I understood correctly, your requirement is to find the tenant id of
> each application owner for the applications in AM_APPLICATION table. You
> could be able to use the SUBSCRIBER_ID in AM_APPLICATION table, it is the
> subscriber id of the application owner. Here the SUBSCRIBER_ID is the
> primary key of AM_SUBSCRIBER table. From AM_SUBSCRIBER table you could find
> the TENANT_ID of that application owner.
>
> Thanks
>
> *Dushani Wellappili*
> Software Engineer - WSO2
>
> Email : dusha...@wso2.com
> Mobile : +94779367571
> Web : https://wso2.com/
>
>
>
>
> On Mon, Oct 1, 2018 at 11:55 AM Ambujaa Satchithananthan 
> wrote:
>
>> @WSO2 Engineering Group 
>>
>> On Mon, Oct 1, 2018 at 10:55 AM Ambujaa Satchithananthan <
>> ambu...@wso2.com> wrote:
>>
>>>
>>> Hi,
>>>
>>> Currently, I am working on creating an admin UI for changing ownership
>>> of an application for APIM. For that, I have to create two jaggery APIs one
>>> to change the owner of an application by the user and the other to retrieve
>>> all the applications for each tenant domain. AM_APPLICATION table in
>>> WSO@AM_DB database does not have a separate field like tenant_Id to
>>> store the entries of tenant domains.
>>> It only has application_Id, name, subscriber_id, application_tier,
>>> callback_url, description, application_status, group_id, created_by,
>>> created_time, updated_by, updated_time, uuid and token_id. When a user
>>> login through a tenant domain the relevant applications for that particular
>>> domain should be only displayed. Here I couldn't retrieve application_ids
>>> by tenant_domain. When users login in an API store of a tenant, usernames
>>> with tenant domain get stored in created_by filed.
>>>
>>> Can you please suggest me a method to overcome this?
>>>
>>>
>>>
>>> +++---+--+--+-++--+---+-++-+--++
>>>
>>> | APPLICATION_ID | NAME   | SUBSCRIBER_ID |
>>> APPLICATION_TIER | CALLBACK_URL | DESCRIPTION | APPLICATION_STATUS |
>>> GROUP_ID | CREATED_BY| CREATED_TIME| UPDATED_BY |
>>> UPDATED_TIME| UUID | TOKEN_TYPE
>>> |
>>>
>>>
>>> +++---+--+--+-++--+---+-++-+--++
>>>
>>> |  4 | DefaultApplication | 4 | Unlimited
>>>   | NULL | NULL| APPROVED   |  |
>>> b...@trip.com | 2018-10-01 10:34:13 | NULL   | 2018-10-01 10:34:13
>>> | 89570a3c-f83d-409c-b48a-92ded8662811 | DEFAULT|
>>>
>>> |  5 | DefaultApplication | 5 | Unlimited
>>>   | NULL | NULL| APPROVED   |  |
>>> ma...@pay.com | 2018-10-01 10:34:52 | NULL   | 2018-10-01 10:34:52
>>> | 894d04bb-33c0-4f34-ad95-deea0e5ad76c | DEFAULT|
>>>
>>>
>>> +++---+--+--+-++--+---+-++-+--++
>>>
>>> 2 rows in set (0.00 sec)
>>>
>>> Thank you.
>>> --
>>> Ambujaa Satchithananthan
>>> Associate Software Engineer | WSO2
>>>
>>> Email: ambu...@wso2.com
>>> Mobile: +94768462473
>>> Web: http://Wso2.com
>>>
>>>
>>>
>>>
>>
>> --
>> Ambujaa Satchithananthan
>> Associate Software Engineer | WSO2
>>
>> Email: ambu...@wso2.com
>> Mobile: +94768462473
>> Web: http://Wso2.com
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Engineering Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to engineering-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

[Mushthaq Rumy]

Adding @dev-wso2 

On Thu, Oct 18, 2018 at 5:25 PM Nuwan Dias  wrote:

> Please discuss technical problems externally.
>
> On Thu, Oct 18, 2018 at 3:44 PM Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> While I was implementing the view page for API document (File) I came
>> across an issue where we get the file name as null when using the
>> micro-service to get the content of the the API document.
>> While analyzing, when adding a file as an API document, I found out that
>> first we save only the doc metadata  and then we save the file content
>> using a second call.
>>
>> After analyzing the DB scripts I figured out that the fileName is stored
>> in AM_API_DOC_META_DATA table and the content is stored in
>> AM_API_RESOURCES. So during the first call we do not have the file name and
>> it is saved as null. During the second call the fileName is passed to the
>> micro-service but it is not stored anywhere. Hence, the fileName is null
>> when we get the content of the file. So to solve this issue, I thought of
>> two solutions.
>>
>> 1. During the second call while adding a file document for API as we get
>> the FileName to the micro-service we can retrieve the document metadata
>> using the documentId and update the fileName apart from saving the content.
>> Hence, it will be available when retrieving the content.
>>
>> 2. We can change the fileName field from AM_API_DOC_META_DATA to
>> AM_API_RESOURCES as the content of the document is stored in this table.
>> And while saving the content we can save it with the fileName. Hence, it
>> will be available when retrieving the content.
>>
>> IMO as option 1 will have more DB calls, option 2 would be the preferred
>> solution.
>>
>> Appreciate your valuable inputs.
>>
>> Thanks & Regards,
>> Mushthaq
>> --
>> Mushthaq Rumy
>> *Senior Software Engineer*
>> Mobile : +94 (0) 779 492140
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>>
>
>
> --
> *Nuwan Dias* | Director | WSO2 Inc.
> (m) +94 777 775 729 | (e) nuw...@wso2.com
> [image: Signature.jpg]
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

[Mushthaq Rumy]

Hi All,

We had an internal discussion and decided to do some modifications in the
DB Schema related to API Docs (AM_API_RESOURCES and AM_API_DOC_META_DATA).
We will be removing the foreign key constraint added to the
AM_API_DOC_META_DATA table as it it has a primary key referred to the
primary key of AM_API_RESOURCES which is not a good practice.

And the following columns will be added to the respective tables.

*AM_API_DOC_META_DATA*
API_ID (This will be a foreign key referred to AM_API table)
RESOURCE_ID
DOC_CONTENT

*AM_API_RESOURCES*
RESOURCE_NAME

So the content of INLINE and URL of API documents will be saved in
*AM_API_DOC_META_DATA
(*DOC_CONTENT column*) *and content of FILE of API documents will be saved
in *AM_API_RESOURCES *which will have a reference in *AM_API_DOC_META_DATA
(*RESOURCE_ID column*)*.

Thanks & Regards,
Mushthaq


On Fri, Oct 19, 2018 at 9:23 PM Harsha Kumara  wrote:

>
>
> On Fri, Oct 19, 2018 at 10:30 AM Uvindra Dias Jayasinha 
> wrote:
>
>> Here is my take on this. When I originally designed the schema I wasn't
>> taking into consideration any of the practical implications associated with
>> API resources being saved and retrieved at DB level. But now that we are at
>> implementation stage some of these implications are much more clearer now.
>>
>> The AM_API_RESOURCES is a generic API resource table(For storing all file
>> based resources associated with APIs). It will be storing the Swagger file,
>> Ballerina file and documentation associated with the API.
>>
>> The AM_API_DOC_META_DATA table is specialized to store additional meta
>> data only associated with documentation.
>>
>> Practically we need to do two calls for document uploads and adding meta
>> data because we are dealing with two different content
>> types(application/json for meta data and multipart/form-data for the file).
>>
>> All files have a name associated with them so it makes sense to have the
>> file name in the AM_API_RESOURCES table. I don't think its a good idea to
>> have a NULL value in a column that we are going to update later, this could
>> lead to all kinds of complications that we will need to handle at code
>> level. So its better to have the file name in AM_API_RESOURCES where we can
>> ensure that we always have a valid name at the time of upload. It is also
>> very easy for us to enforce that a file name for a given type does not get
>> duplicated with a table level constraint if we go with this option.
>>
>> Joining between two tables like this in case we need to get the file name
>> is trivial so I don't think we should let that affect us coming up with the
>> best possible solution.
>>
> +1 it's a not good practice to add record which will update from null to
> some value cause of update going for another table.
>
>>
>> So Im +1 for option 2. WDYT?
>>
>> On Thu, 18 Oct 2018 at 17:31, Mushthaq Rumy  wrote:
>>
>>> Adding @dev-wso2 
>>>
>>> On Thu, Oct 18, 2018 at 5:25 PM Nuwan Dias  wrote:
>>>
>>>> Please discuss technical problems externally.
>>>>
>>>> On Thu, Oct 18, 2018 at 3:44 PM Mushthaq Rumy 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> While I was implementing the view page for API document (File) I came
>>>>> across an issue where we get the file name as null when using the
>>>>> micro-service to get the content of the the API document.
>>>>> While analyzing, when adding a file as an API document, I found out
>>>>> that first we save only the doc metadata  and then we save the file 
>>>>> content
>>>>> using a second call.
>>>>>
>>>>> After analyzing the DB scripts I figured out that the fileName is
>>>>> stored in AM_API_DOC_META_DATA table and the content is stored in
>>>>> AM_API_RESOURCES. So during the first call we do not have the file name 
>>>>> and
>>>>> it is saved as null. During the second call the fileName is passed to the
>>>>> micro-service but it is not stored anywhere. Hence, the fileName is null
>>>>> when we get the content of the file. So to solve this issue, I thought of
>>>>> two solutions.
>>>>>
>>>>> 1. During the second call while adding a file document for API as we
>>>>> get the FileName to the micro-service we can retrieve the document 
>>>>> metadata
>>>>> using the documentId and update the fileName apart from saving the 
>>>>> content.
>>

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

[Mushthaq Rumy]

Hi Uvindra,

Please find the data types below

*AM_API_DOC_META_DATA*
API_ID (This will be a foreign key referred to AM_API table) VARCHAR(255)
RESOURCE_ID VARCHAR(255)
DOC_CONTENT VARCHAR(1024)

*AM_API_RESOURCES*
RESOURCE_NAME VARCHAR(255)

And I think we can change it DOC_CONTENT to CONTENT .
WDYT?

Thanks & Regards,
Mushthaq

On Mon, Oct 22, 2018 at 2:35 PM Uvindra Dias Jayasinha 
wrote:

> HI Mushtaq,
>
> Can you provide the data types of the columns so that this is more clear?
> I believe that DOC_CONTENT should be a VARCHAR, in that case better to call
> it something like SHORT_CONTENT, since this communicates that it is meant
> to share relatively short text values such as URL and inline text. The name
> DOC_CONTENT is misleading and might suggest we can store larger documents
> in this column.
>
> On Mon, 22 Oct 2018 at 14:02, Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> We had an internal discussion and decided to do some modifications in the
>> DB Schema related to API Docs (AM_API_RESOURCES and AM_API_DOC_META_DATA).
>> We will be removing the foreign key constraint added to the
>> AM_API_DOC_META_DATA table as it it has a primary key referred to the
>> primary key of AM_API_RESOURCES which is not a good practice.
>>
>> And the following columns will be added to the respective tables.
>>
>> *AM_API_DOC_META_DATA*
>> API_ID (This will be a foreign key referred to AM_API table)
>> RESOURCE_ID
>> DOC_CONTENT
>>
>> *AM_API_RESOURCES*
>> RESOURCE_NAME
>>
>> So the content of INLINE and URL of API documents will be saved in 
>> *AM_API_DOC_META_DATA
>> (*DOC_CONTENT column*) *and content of FILE of API documents will be
>> saved in *AM_API_RESOURCES *which will have a reference in 
>> *AM_API_DOC_META_DATA
>> (*RESOURCE_ID column*)*.
>>
>> Thanks & Regards,
>> Mushthaq
>>
>>
>> On Fri, Oct 19, 2018 at 9:23 PM Harsha Kumara  wrote:
>>
>>>
>>>
>>> On Fri, Oct 19, 2018 at 10:30 AM Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
>>>> Here is my take on this. When I originally designed the schema I wasn't
>>>> taking into consideration any of the practical implications associated with
>>>> API resources being saved and retrieved at DB level. But now that we are at
>>>> implementation stage some of these implications are much more clearer now.
>>>>
>>>> The AM_API_RESOURCES is a generic API resource table(For storing all
>>>> file based resources associated with APIs). It will be storing the Swagger
>>>> file, Ballerina file and documentation associated with the API.
>>>>
>>>> The AM_API_DOC_META_DATA table is specialized to store additional meta
>>>> data only associated with documentation.
>>>>
>>>> Practically we need to do two calls for document uploads and adding
>>>> meta data because we are dealing with two different content
>>>> types(application/json for meta data and multipart/form-data for the file).
>>>>
>>>> All files have a name associated with them so it makes sense to have
>>>> the file name in the AM_API_RESOURCES table. I don't think its a good idea
>>>> to have a NULL value in a column that we are going to update later, this
>>>> could lead to all kinds of complications that we will need to handle at
>>>> code level. So its better to have the file name in AM_API_RESOURCES where
>>>> we can ensure that we always have a valid name at the time of upload. It is
>>>> also very easy for us to enforce that a file name for a given type does not
>>>> get duplicated with a table level constraint if we go with this option.
>>>>
>>>> Joining between two tables like this in case we need to get the file
>>>> name is trivial so I don't think we should let that affect us coming up
>>>> with the best possible solution.
>>>>
>>> +1 it's a not good practice to add record which will update from null to
>>> some value cause of update going for another table.
>>>
>>>>
>>>> So Im +1 for option 2. WDYT?
>>>>
>>>> On Thu, 18 Oct 2018 at 17:31, Mushthaq Rumy  wrote:
>>>>
>>>>> Adding @dev-wso2 
>>>>>
>>>>> On Thu, Oct 18, 2018 at 5:25 PM Nuwan Dias  wrote:
>>>>>
>>>>>> Please discuss technical problems externally.
>>>>>>
>>>>>> On Thu, Oct 18, 2018 at 3:44 PM Mushthaq Ru

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

[Mushthaq Rumy]

+1 for having all API doc related data in a single table and rename the
table as DOCS.

Thanks & Regards,
Mushthaq

On Tue, Oct 23, 2018 at 10:07 AM Uvindra Dias Jayasinha 
wrote:

> @Bhathiya Jayasekara 
> yes, this is also an option. In reality though very few customers upload
> lots of additional docs. We could just rename DOC_META_DATA table to DOCS
> and store the docs in that table itself. So at the very minimum we have a
> swagger and ballerina definition per an API stored in the RESOURCES table.
>
> Can we make a call on this soon? Implementation is getting delayed because
> of this.
>
> On Mon, 22 Oct 2018 at 21:08, Bhathiya Jayasekara 
> wrote:
>
>> This looks ok. Btw, I was wondering if it's a good idea to have all files
>> (swaggers, wsdls, docs etc.) in a single table. Won't that make the table
>> grow faster and make querying slower? How about keeping a separate table
>> for this? Then we can have a foreign key as well.
>>
>> Thanks,
>> Bhathiya
>>
>> On Mon, Oct 22, 2018 at 2:57 PM Uvindra Dias Jayasinha 
>> wrote:
>>
>>> +1, CONTENT  is fine
>>>
>>> On Mon, 22 Oct 2018 at 14:45, Mushthaq Rumy  wrote:
>>>
>>>> Hi Uvindra,
>>>>
>>>> Please find the data types below
>>>>
>>>> *AM_API_DOC_META_DATA*
>>>> API_ID (This will be a foreign key referred to AM_API table)
>>>> VARCHAR(255)
>>>> RESOURCE_ID VARCHAR(255)
>>>> DOC_CONTENT VARCHAR(1024)
>>>>
>>>> *AM_API_RESOURCES*
>>>> RESOURCE_NAME VARCHAR(255)
>>>>
>>>> And I think we can change it DOC_CONTENT to CONTENT .
>>>> WDYT?
>>>>
>>>> Thanks & Regards,
>>>> Mushthaq
>>>>
>>>> On Mon, Oct 22, 2018 at 2:35 PM Uvindra Dias Jayasinha <
>>>> uvin...@wso2.com> wrote:
>>>>
>>>>> HI Mushtaq,
>>>>>
>>>>> Can you provide the data types of the columns so that this is more
>>>>> clear? I believe that DOC_CONTENT should be a VARCHAR, in that case better
>>>>> to call it something like SHORT_CONTENT, since this communicates that it 
>>>>> is
>>>>> meant to share relatively short text values such as URL and inline text.
>>>>> The name DOC_CONTENT is misleading and might suggest we can store larger
>>>>> documents in this column.
>>>>>
>>>>> On Mon, 22 Oct 2018 at 14:02, Mushthaq Rumy  wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We had an internal discussion and decided to do some modifications in
>>>>>> the DB Schema related to API Docs (AM_API_RESOURCES and
>>>>>> AM_API_DOC_META_DATA). We will be removing the foreign key constraint 
>>>>>> added
>>>>>> to the  AM_API_DOC_META_DATA table as it it has a primary key referred to
>>>>>> the primary key of AM_API_RESOURCES which is not a good practice.
>>>>>>
>>>>>> And the following columns will be added to the respective tables.
>>>>>>
>>>>>> *AM_API_DOC_META_DATA*
>>>>>> API_ID (This will be a foreign key referred to AM_API table)
>>>>>> RESOURCE_ID
>>>>>> DOC_CONTENT
>>>>>>
>>>>>> *AM_API_RESOURCES*
>>>>>> RESOURCE_NAME
>>>>>>
>>>>>> So the content of INLINE and URL of API documents will be saved in 
>>>>>> *AM_API_DOC_META_DATA
>>>>>> (*DOC_CONTENT column*) *and content of FILE of API documents will be
>>>>>> saved in *AM_API_RESOURCES *which will have a reference in 
>>>>>> *AM_API_DOC_META_DATA
>>>>>> (*RESOURCE_ID column*)*.
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> Mushthaq
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 19, 2018 at 9:23 PM Harsha Kumara 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 19, 2018 at 10:30 AM Uvindra Dias Jayasinha <
>>>>>>> uvin...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Here is my take on this. When I originally designed the schema I
>>>>>>>> wasn't taking into consideration any of the practical implications
>>>>>>>> a

[Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC2

[Mushthaq Rumy]

Hi All,

We are pleased to announce the second release candidate of WSO2 API Manager
3.0.0.

This release fixes the following issues.

   - Fixes : carbon-apimgt
   
<https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23+>
   - Fixes : product-apim
   
<https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>
   - Fixes : analytics-apim
   
<https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>

Source and distribution,
Runtime : https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc2
Analytics :
https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc2
APIM Tooling :
https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc

Please download, test the product and vote.

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
WSO2 API Manager Team


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC2

[Mushthaq Rumy]

Hi All,

Tested the following scenarios.
- API Creation, Publishing and Subscription
- Tested Publisher Access Control
- Tested Store visibility
- Identity management features such as self sign up, password reset,
password policy, account locking.

No blockers found. Hence +1.

Thanks & Regards,
Mushthaq

On Thu, Oct 24, 2019 at 4:15 PM Prasanna Dangalla  wrote:

> Hi All,
>
> Tested API Creation, Publishing, Subscription JWT & OAuth Token generation
> and throttling.
>
> Hence +1 from me.
>
> Thanks
> *Prasanna Dangalla* | Associate Technical Lead | WSO2 Inc.
> (m) +94 718 112 751 | (e) prasa...@wso2.com
> [image: Signature.jpg]
>
>
>
>
>
>
>
> On Thu, Oct 24, 2019 at 8:51 AM Mushthaq Rumy  wrote:
>
>> Hi All,
>>
>> We are pleased to announce the second release candidate of WSO2 API
>> Manager 3.0.0.
>>
>> This release fixes the following issues.
>>
>>- Fixes : carbon-apimgt
>>
>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23+>
>>- Fixes : product-apim
>>
>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>
>>- Fixes : analytics-apim
>>
>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>
>>
>> Source and distribution,
>> Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc2
>> Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc2
>> APIM Tooling :
>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc
>>
>> Please download, test the product and vote.
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> WSO2 API Manager Team
>>
>>
>> --
>> Mushthaq Rumy
>> *Senior Software Engineer*
>> Mobile : +94 (0) 779 492140
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> <http://wso2.com/signature>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC3

[Mushthaq Rumy]

Hi All,

Hi All,

Tested the following scenarios in both super tenant and tenant.
- API Creation, Publishing, Subscribing and invocation of APIs
- Tested Publisher Access Control
- Tested Store Visibility
- Identity management features such as self sign up, password reset,
password policy, account locking.

No blockers found. Hence, [+] Stable - go ahead and release.

Thanks & Regards,
Mushthaq

On Fri, Oct 25, 2019 at 3:52 AM Samitha Chathuranga 
wrote:

> Hi All,
>
> We are pleased to announce the second release candidate of WSO2 API
> Manager 3.0.0.
>
> This release fixes the following issues.
>
>- Fixes : product-apim
>
> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24>
>- Fixes : carbon-apimgt
>
> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24+>
>- Fixes : analytics-apim
>
> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24>
>
> Source and distribution,
> Runtime : https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc3
> Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc3
> APIM Tooling :
> https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 API Manager Team
>
>
> --
> *Samitha Chathuranga*
> *Senior Software Engineer*, *WSO2 Inc.*
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [APIM] API Categories

[Mushthaq Rumy]

; <https://localhost:9443/api/am/admin/v0.15/categories>**\r\n**Authorization:
>>>>>>>>>  Bearer 0d63e133-7ad6-3aeb-9ca9-9299e0708122**\r\n**Content-Type: 
>>>>>>>>> application/json**\r\n\r\n* *-d  {**\r\n 
>>>>>>>>> \"**name**\"**:**\"**Finance**\"**,**\r\n 
>>>>>>>>> \"**description**\"**:**\"**Finance related APIS**\"\r\n* *}"*,
>>>>>>>>> *"x-wso2-response"*: *"HTTP/1.1 201 Created**\r\n**Content-Type: 
>>>>>>>>> application/json**\r\n\r\n**{**\r\n   \"**count**\"**:1,**\r\n   
>>>>>>>>> \"**list**\"**:[**\r\n*  *{**\r\n 
>>>>>>>>> \"**id**\"**:**\"**463e2c9f-5e99-43c3-a66e-de7e0f367373**\"**,**\r\n  
>>>>>>>>>\"**name**\"**:**\"**Finance**\"**,**\r\n 
>>>>>>>>> \"**description**\"**:**\"**Finance related APIS**\"\r\n*  
>>>>>>>>> *}**\r\n*   *]**\r\n**}"*,*"summary"*: *"Add a Category"*,
>>>>>>>>> *"description"*: *"Add a new API Category**\n**"*,*"parameters"*: 
>>>>>>>>> [  {*"in"*: *"body"*,*"name"*: *"body"*,
>>>>>>>>> *"description"*: *"Category object that should to be added**\n**"*,   
>>>>>>>>>  *"required"*: *true*,*"schema"*: {  *"$ref"*: 
>>>>>>>>> *"#/definitions/Category"*}  }],*"tags"*: [  
>>>>>>>>> *"Category"*],*"responses"*: {  *"201"*: {
>>>>>>>>> *"description"*: *"Created.**\n**Successful response with the newly 
>>>>>>>>> created object as entity in the body.**\n**"*,*"schema"*: {   
>>>>>>>>>*"$ref"*: *"#/definitions/Category"*}  },  
>>>>>>>>> *"400"*: {*"description"*: *"Bad Request.**\n**Invalid 
>>>>>>>>> request or validation error**\n**"*,*"schema"*: {  
>>>>>>>>> *"$ref"*: *"#/definitions/Error"*}  }}  }}
>>>>>>>>>
>>>>>>>>> And category and categoryList would be defined as below.
>>>>>>>>>
>>>>>>>>> *"Category"*: {*"title"*: *"Category"*,*"required"*: [  
>>>>>>>>> *"name"*],*"properties"*: {  *"id"*: {*"type"*: 
>>>>>>>>> *"string"*,*"example"*: 
>>>>>>>>> *"01234567-0123-0123-0123-012345678901"*  },  *"name"*: { 
>>>>>>>>>*"type"*: *"string"*,*"example"*: *"Finance"*  },  
>>>>>>>>> *"description"*: {*"type"*: *"string"*,*"example"*: 
>>>>>>>>> *"Finance related APIs"*  }}  },  *"CategoryList"*: {
>>>>>>>>> *"title"*: *"Category List"*,*"properties"*: {  *"count"*: {  
>>>>>>>>>   *"type"*: *"integer"*,*"description"*: *"Number of 
>>>>>>>>> categories returned.**\n**"*,*"example"*: 1  },  
>>>>>>>>> *"list"*: {*"type"*: *"array"*,*"items"*: {  
>>>>>>>>> *"$ref"*: *"#/definitions/Category"*}  }}  }}
>>>>>>>>>
>>>>>>>>> 2. Define a new AM_CATEGORIES table to hold category related
>>>>>>>>> details.
>>>>>>>>>
>>>>>>>>> *CREATE TABLE *IF *NOT EXISTS *AM_CATEGORIES (  CATEGORY_ID 
>>>>>>>>> *VARCHAR*(50),  NAME *VARCHAR*(255),  DESCRIPTION *VARCHAR*(1024),  
>>>>>>>>> TENANT_DOMAIN *VARCHAR*(255),  *UNIQUE *(NAME,TENANT_DOMAIN),  
>>>>>>>>> *PRIMARY KEY *(CATEGORY_ID));
>>>>>>>>>
>>>>>>>>> 3. Publisher UI overview tab(or a suitable place as it fits) will
>>>>>>>>> have a new UI element to select categories for the API. And selecting
>>>>>>>>> categories for an API would be optional.
>>>>>>>>>
>>>>>>>>> 4. API to category mapping will be stored in registry API artifact
>>>>>>>>> and for that following table field would have to be added to api.rxt. 
>>>>>>>>> (I
>>>>>>>>> assume we are going to support associating a single API with multiple
>>>>>>>>> categories)
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Category Name
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> categoryName
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>>
>>>>>>>>> 5. And from store viewing POV, I assume API categories are a
>>>>>>>>> substitution for existing tag-wise grouping feature and that both 
>>>>>>>>> tag-wise
>>>>>>>>> groups and categories won’t co-exist in the store. Please do correct 
>>>>>>>>> if my
>>>>>>>>> understanding is wrong.
>>>>>>>>> Once a developer visits the store, he will be presented with the
>>>>>>>>> list of API categories and upon selecting a category out of those,
>>>>>>>>> associated APIs will be listed.
>>>>>>>>> APIs that are not associated with any category will be listed
>>>>>>>>> under other APIs or a similar heading.
>>>>>>>>>
>>>>>>>>> Please feel free to add your suggestions.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sachini
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> *Sachini De Silva*
>>>>>>>>> Senior Software Engineer - WSO2
>>>>>>>>>
>>>>>>>>> Email : sachi...@wso2.com
>>>>>>>>> Mobile : +94714765495
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Bhathiya Jayasekara* | Technical Lead | WSO2 Inc.
>>>>>>>> (m) +94 71 547 8185  | (e) bhathiya-@t-wso2-d0t-com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Sachini De Silva*
>>>>>>> Senior Software Engineer - WSO2
>>>>>>>
>>>>>>> Email : sachi...@wso2.com
>>>>>>> Mobile : +94714765495
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Nuwan Dias* | Director | WSO2 Inc.
>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com
>>>>>> [image: Signature.jpg]
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Sachini De Silva*
>>>>> Senior Software Engineer - WSO2
>>>>>
>>>>> Email : sachi...@wso2.com
>>>>> Mobile : +94714765495
>>>>>
>>>>>
>>>>
>>>> --
>>>> *Sanjeewa Malalgoda*
>>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>>>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>>>> <https://medium.com/@sanjeewa190>
>>>>
>>>> GET INTEGRATION AGILE <https://wso2.com/signature>
>>>> Integration Agility for Digitally Driven Business
>>>>
>>>
>>>
>>> --
>>> *Bhathiya Jayasekara* | Technical Lead | WSO2 Inc.
>>> (m) +94 71 547 8185  | (e) bhathiya-@t-wso2-d0t-com
>>>
>>>
>>>
>>
>> --
>> Malintha Amarasinghe
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Thanks and Regards
> *,**Shani Ranasinghe* | Associate Lead - Technical Writer | WSO2 Inc
> <https://wso2.com/>
> (M) +94 772 273 555 | (E) sh...@wso2.com
>
> <http://wso2.com/signature>
>
> <https://mail.google.com/http://wso2.com/signature>
> :
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Senior Software Engineer*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [APIM] API Categories

[Mushthaq Rumy]

Maybe we can have two tables, that is one extra table to have the values
(multi valued attribute as shown below) related to the main category.

[image: Screen Shot 2019-11-20 at 11.42.41 AM.png]

Thanks & Regards,
Mushthaq

On Wed, Nov 20, 2019 at 10:40 AM Mushthaq Rumy  wrote:

> Hi,
>
> I too don't see much difference between the tags model and the current
> proposed model. As Sanjeewa mentioned the only difference seems to be that
> in this case admin will be adding the categories. IMO, if we are to have a
> value from this feature we will have to do something similar to the
> categorization feature done in WSO2 Governance Registry [1]. Here [1], we
> have used RXT to add the categories but it is not recommended to change
> RXTs as there will be migration issues. We will have to do something
> similar to that but with a different design approach.
>
> [1] -
> https://docs.wso2.com/display/Governance540/Refining+the+Search+Results
>
> Thanks & Regards,
> Mushthaq
>
> On Wed, Nov 13, 2019 at 4:10 PM Shani Ranasinghe  wrote:
>
>> Hi,
>> Is my understanding on our different grouping methods, as stated below,
>> correct?
>> 1) API Labels - used when want to group APIs and deploy them on a MGW
>> 2) API tags - to group APIs based on specific functionality if offers
>> (down to resource level), and to make search easier
>> 3) API Category Labels - to group APIs based on the main business
>> offering, and to make it more searchable on the dev portal
>>
>> I have a few suggestions to avoid confusions about the different grouping
>> terms we have in the product.
>>
>> 1) With API Labels, if we call it a way of grouping APIs, I think it
>> would confuse our customers. Because ideally, if someone searches for
>> grouping APIs, API categories should appear on the search result. To avoid
>> confusion, shall we describe it as "API deployment Package" /  "API
>> Package"  and have the content heading as "Deploying API Packages" under
>> MGW docs? But then again, we also have API Products, which is also a
>> packaging concept. Any other suggestions?
>>
>> 2) We have "API Monetization Category Labels" . Are we still considering
>> it as a label or, should we call it, "API monetization model" I feel it's
>> more than a label, and it defines actually a monetization model. WDYT?
>>
>> On Wed, Nov 13, 2019 at 12:35 PM Malintha Amarasinghe 
>> wrote:
>>
>>> Earlier we supported a thumbnail per group. Do we plan to support that
>>> too?
>>>
>>> Thanks!
>>>
>>> On Wed, Nov 13, 2019 at 12:32 PM Bhathiya Jayasekara 
>>> wrote:
>>>
>>>> We can replace tag-groups with categories, and keep tags as it is which
>>>> is helpful in searches.
>>>>
>>>> Thanks,
>>>> Bhathiya
>>>>
>>>> On Wed, Nov 13, 2019 at 12:30 PM Sanjeewa Malalgoda 
>>>> wrote:
>>>>
>>>>> If we have API categories then tag wise store view will not need
>>>>> anymore. As i remember tagwise store view working till last release.
>>>>> Only difference between categories and tags is categories created by
>>>>> admin while tags created by API creator. Do we have any other differences
>>>>> or specific use cases address by this?
>>>>>
>>>>> Thanks,
>>>>> sanjeewa.
>>>>>
>>>>> On Wed, Nov 13, 2019 at 12:22 PM Sachini De Silva 
>>>>> wrote:
>>>>>
>>>>>> @Harsha Kumara   will switch to tenant id.
>>>>>>
>>>>>> @Nuwan Dias   +1 will add a single scope
>>>>>> ‘apim:api_category’ to do all api categories related operations.
>>>>>>
>>>>>> In publisher, categories/ GET resource can be associated with
>>>>>> apim:api_view scope. In store we can avoid attaching a scope to 
>>>>>> categories/
>>>>>> GET resource and allow to access the resource without a token.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 13, 2019 at 11:50 AM Nuwan Dias  wrote:
>>>>>>
>>>>>>> For the admin API, I don't think we need separate scopes for the
>>>>>>> read and write of categories, isn't it?
>>>>>>>
>>>>>>> The publisher and store APIs would also need an API each to fetch
>>>>>>> the categories. These can be boun

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.1.0 RC3

[Mushthaq Rumy]

 - AWS Lambda functions
>>>>>>>>>>>>>>>- Working with Observability
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No blocking issues found.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1 - Stable - Go ahead and release
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Sanjula
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Mar 22, 2020 at 4:36 PM Tharindu Dharmarathna <
>>>>>>>>>>>>>>> tharin...@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have tested the following Databases.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. Oracle
>>>>>>>>>>>>>>>> 2. Mysql 5.7
>>>>>>>>>>>>>>>> 3. Mysql 8
>>>>>>>>>>>>>>>> 4. Postgresql
>>>>>>>>>>>>>>>> 5. Oracle
>>>>>>>>>>>>>>>> 6. MSSQL
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> No issues found.
>>>>>>>>>>>>>>>> +1 go ahead and Release
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Mar 21, 2020 at 12:56 AM Krishan Wijesena <
>>>>>>>>>>>>>>>> krish...@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We are pleased to announce the third release candidate of
>>>>>>>>>>>>>>>>> WSO2 API Manager 3.1.0.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This release fixes the following issues.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>- Fixes : product-apim
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2019-11-01..2020-03-20+label%3A3.1.0+>
>>>>>>>>>>>>>>>>>- Fixes : analytics-apim
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> <https://github.com/wso2/analytics-apim/milestone/20?closed=1>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Source and distribution,
>>>>>>>>>>>>>>>>> Runtime :
>>>>>>>>>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v3.1.0-rc3
>>>>>>>>>>>>>>>>> Analytics :
>>>>>>>>>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.1.0-rc3
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please download, test the product and vote.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [+] Stable - go ahead and release
>>>>>>>>>>>>>>>>> [-] Broken - do not release (explain why)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> WSO2 API Manager Team
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *Krishan Wijesena*
>>>>>>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Email : krish...@wso2.com
>>>>>>>>>>>>>>>>> Mobile : +94776219923
>>>>>>>>>>>>>>>>> WSO2 Inc : http://wso2.com
>>>>>>>>>>>>>>>>> [image: http://wso2.com/signature]
>>>>>>>>>>>>>>>>> <http://wso2.com/signature>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *Tharindu Dharmarathna*Technical Lead
>>>>>>>>>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> mobile: *+94779109091*
>>>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>>>> Dev mailing list
>>>>>>>>>>>>>>>> Dev@wso2.org
>>>>>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> *Sanjula Madurapperuma* | Software Engineering Intern |
>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>> (m) +94 768877766 | (e) sanj...@wso2.com
>>>>>>>>>>>>>>> <http://wso2.com/signature>
>>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>>>> architect...@wso2.org
>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> *Nuwan Dias* | Senior Director | WSO2 Inc.
>>>>>>>>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com
>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>> Dev mailing list
>>>>>>>>>>>>>> Dev@wso2.org
>>>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> *Krishan Wijesena*
>>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Email : krish...@wso2.com
>>>>>>>>>>>>> Mobile : +94776219923
>>>>>>>>>>>>> WSO2 Inc : http://wso2.com
>>>>>>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> *Krishan Wijesena*
>>>>>>>>>>>> Senior Software Engineer | WSO2
>>>>>>>>>>>>
>>>>>>>>>>>> Email : krish...@wso2.com
>>>>>>>>>>>> Mobile : +94776219923
>>>>>>>>>>>> WSO2 Inc : http://wso2.com
>>>>>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>>>>>>> ___
>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>> architect...@wso2.org
>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc.
>>>>>>>>>>> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com
>>>>>>>>>>> GET INTEGRATION AGILE
>>>>>>>>>>> Integration Agility for Digitally Driven Business
>>>>>>>>>>> ___
>>>>>>>>>>> Dev mailing list
>>>>>>>>>>> Dev@wso2.org
>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc.
>>>>>>>>>> +94 710 618 178
>>>>>>>>>> GET INTEGRATION AGILE
>>>>>>>>>> Integration Agility for Digitally Driven Business
>>>>>>>>>> ___
>>>>>>>>>> Dev mailing list
>>>>>>>>>> Dev@wso2.org
>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Dev mailing list
>>>>>>>>> Dev@wso2.org
>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Vithursa Mahendrarajah* | Senior Software Engineer | WSO2 Inc
>>>>>>>> (m) +94 766 695 643 | (e) vithu...@wso2.com
>>>>>>>>
>>>>>>>> * <http://wso2.com/signature>[image: https://wso2.com/signature]
>>>>>>>> <https://wso2.com/signature>*
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Kavishka Fernando*
>>>>>>> *Senior Software Engineer | WSO2*
>>>>>>> Email: kavis...@wso2.com
>>>>>>> Mobile:  +94773838069
>>>>>>> Web: http://wso2.com
>>>>>>> Blog: https://medium.com/@kavishkafernando
>>>>>>>
>>>>>>> <http://wso2.com/signature>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Sachini De Silva*
>>>>>> Senior Software Engineer - WSO2
>>>>>>
>>>>>> Email : sachi...@wso2.com
>>>>>> Mobile : +94714765495
>>>>>>
>>>>>> ___
>>>>>> Architecture mailing list
>>>>>> architect...@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards
>>>>> Dushan Silva
>>>>> Senior Software Engineer
>>>>>
>>>>> *WSO2, Inc. *
>>>>>
>>>>> lean . enterprise . middleware
>>>>> Mob: +94 774 979042
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>> <https://medium.com/@sanjeewa190>
>>
>> GET INTEGRATION AGILE <https://wso2.com/signature>
>> Integration Agility for Digitally Driven Business
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC2

[Mushthaq Rumy]

Tested the following flows for super tenant and tenant users.
- Basic flow of API creation, subscription and invocation
- Soap API with pass through
- Soap to Rest feature

No issues found. +1 to proceed with the release.

Thanks & Regards,
Mushthaq

On Sat, Aug 8, 2020 at 5:53 PM Amila De Silva  wrote:

> Tested Artifact Synchroniser for Super Tenant mode
> - for Basic flows
> - With multiple Labels assigned to APIs
> - Startup Delay configured
> - for failover scenarios (On a Setup with GWs without DB access and TMs in
> Failover mode)
> No issues found.
>
> +1 to proceed with the release.
>
> On Sat, Aug 8, 2020 at 12:25 PM Arshardh Ifthikar 
> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the second release candidate of WSO2 API
>> Manager 3.2.0.
>>
>> This release fixes the following issues.
>>
>>- Fixes : product-apim
>>
>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-08-06>
>>- Fixes : analytics-apim
>><https://github.com/wso2/analytics-apim/milestone/28?closed=1>
>>
>> Source and distribution,
>> Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc2
>> Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc2
>>
>> Documentation : https://apim.docs.wso2.com/en/3.2.0/
>> Migration docs :
>> https://apim.docs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/
>>
>> Please download, test the product and vote.
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> WSO2 API Manager Team
>>
>> --
>> *Arshardh Ifthikar*
>> Senior Software Engineer | WSO2 Inc.
>>
>> Email: arsha...@wso2.com
>> Mobile: +94777218551
>> Web: http://wso2.com
>>
>> <http://wso2.com/signature>
>>
>
>
> --
> *Amila De Silva*
> Software Architect | Associate Director, Engineering - WSO2 Inc.
> (m) +94 775119302 | (e) ami...@wso2.com
> <http://wso2.com/signature>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC3

[Mushthaq Rumy]

Hi All,

We are pleased to announce the third release candidate of WSO2 API Manager
3.2.0.

This release fixes the following issues.

   - Fixes : product-apim
   
<https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-08-11>
   - Fixes : analytics-apim
   <https://github.com/wso2/analytics-apim/milestone/28?closed=1>

Source and distribution,
Runtime : https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc3
Analytics :
https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc3

Documentation : https://apim.docs.wso2.com/en/3.2.0/
Migration docs :
https://apim.docs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/

Please download, test the product and vote.

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
WSO2 API Manager Team


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC5

[Mushthaq Rumy]

Hi All,

We are pleased to announce the fifth release candidate of WSO2 API Manager
3.2.0.

This release fixes the following issues.

   - Fixes : product-apim
   
<https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-08-15>
   - Fixes : analytics-apim
   <https://github.com/wso2/analytics-apim/milestone/28?closed=1>

Source and distribution,
Runtime : https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc5
Analytics :
https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc3

Documentation : https://apim.docs.wso2.com/en/3.2.0/
Migration docs :
https://apim.docs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/

Please download, test the product and vote.

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
WSO2 API Manager Team


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC6

[Mushthaq Rumy]

Hi All,

Tested the following flows for super tenant and tenant users.
- Basic flow of API creation, subscription and invocation
- Soap API with pass through
- Soap to Rest feature
- Scopes

No issues found.

*[+] Stable - Go ahead and release.*

Thanks & Regards,
Mushthaq

On Mon, Aug 24, 2020 at 3:32 PM Krishan Wijesena  wrote:

> Hi all,
>
> Tested as follows.
>
> Environment:  Windows 10, Chrome/Edge
>JDK-1.8.0_251
>
>- Publisher, Devportal and Admin portal Login
>- Create an API using New Rest API + swagger URL
>- Change the lifecycle events of an API.
>- Generate Token with and without Local Scope
>- Create new subscription policy using the admin portal.
>- Subscribe  and invoke API (With scope/ WIth new subscription policy)
>- Upload thumbnail image.
>
>
> *[+] Stable - Go ahead and release.*
>
> Thanks,
> Krishan.
>
> On Mon, Aug 24, 2020 at 2:25 PM Prasanna Dangalla 
> wrote:
>
>> Hi All,
>>
>> Ran WSO2 enterprise test scenarios. No issues identified.
>>
>> *[+] Stable - Go ahead and release.*
>>
>> Thanks
>> *Prasanna Dangalla* | Associate Technical Lead | WSO2 Inc.
>> (m) +94 718 112 751 | (e) prasa...@wso2.com
>>
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>>
>> On Mon, Aug 24, 2020 at 2:09 PM Sanjeewa Malalgoda 
>> wrote:
>>
>>> I have tested API Manager 3.2.0 against the following criterias.
>>>
>>>- Java Security Manager with JDK 11.0 and tested security flows.
>>>- Developer portal and publisher standard user flows.
>>>- Policy creation wizard and throttling capabilities.
>>>
>>> Found some minor issues[1,2,3] related to policy wizard and scopes. I
>>> don't consider them as blockers.
>>>
>>> [1] https://github.com/wso2/product-apim/issues/9172
>>> [2] https://github.com/wso2/product-apim/issues/9173
>>> [3] https://github.com/wso2/product-apim/issues/9174
>>>
>>> *[+] Stable - Go ahead and release.*
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Sat, Aug 22, 2020 at 12:06 AM Arshardh Ifthikar 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are pleased to announce the sixth release candidate of WSO2 API
>>>> Manager 3.2.0.
>>>>
>>>> This release fixes the following issues.
>>>>
>>>>- Fixes : product-apim
>>>>
>>>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-08-20>
>>>>- Fixes : analytics-apim
>>>><https://github.com/wso2/analytics-apim/milestone/28?closed=1>
>>>>
>>>> Source and distribution,
>>>> Runtime :
>>>> https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc6
>>>> Analytics :
>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc3
>>>>
>>>> Documentation : https://apim.docs.wso2.com/en/3.2.0/
>>>> Migration docs :
>>>> https://apim.docs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/
>>>>
>>>> Please download, test the product and vote.
>>>>
>>>> [+] Stable - go ahead and release
>>>> [-] Broken - do not release (explain why)
>>>>
>>>> Thanks,
>>>> WSO2 API Manager Team
>>>>
>>>> --
>>>> *Arshardh Ifthikar*
>>>> Senior Software Engineer | WSO2 Inc.
>>>>
>>>> Email: arsha...@wso2.com
>>>> Mobile: +94777218551
>>>> Web: http://wso2.com
>>>>
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>> --
>>> *Sanjeewa Malalgoda*
>>> Software Architect | Associate Director, Engineering - WSO2 Inc.
>>> (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger
>>> <http://sanjeewamalalgoda.blogspot.com>, Medium
>>> <https://medium.com/@sanjeewa190>
>>>
>>> GET INTEGRATION AGILE <https://wso2.com/signature>
>>> Integration Agility for Digitally Driven Business
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
>
> *Krishan Wijesena*
> Senior Software Engineer | WSO2
>
> Email : krish...@wso2.com
> Mobile : +94776219923
> WSO2 Inc : http://wso2.com
> [image: http://wso2.com/signature] <http://wso2.com/signature>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

[Dev] WSO2 Committers += Chamod Samarajeewa

[Mushthaq Rumy]

Hi All,

It's my pleasure to announce Chamod Samarajeewa as a WSO2 Committer. He has
been a valuable contributor and enthusiast to the WSO2 API Manager team.

In recognition of his contribution, dedication, and commitment he has been
voted as a WSO2 committer.

Congratulations Chamod and keep up the good work...!!!

Thanks & Regards,
Mushthaq
-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC2

[Mushthaq Rumy]

Hi All,

+1 from the API Manager Team.

Thanks & Regards,
Mushthaq

On Tue, Nov 10, 2020 at 6:11 PM Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

> Hi All,
>
> +1 from the Security Team as all the security scans got completed.
>
> Best Regards,
> Nadeeshani.
>
> On Sat, Nov 7, 2020 at 3:06 PM Kanapriya Kuleswararajan <
> kanapr...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> *WSO2 Carbon Kernel 4.6.1 RC2 Release Vote*.
>>
>> Please download and test your products with kernel 4.6.1 RC2 and vote.
>> The vote will be open for 72 hours or longer as needed.
>>
>> *Maven staging repository:*
>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4915
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC2
>>
>> [- ] Broken - do not release (explain why)
>> [+] Stable - go ahead and release
>>
>> Thanks
>> Kanapriya Kuleswararajan
>> Senior Software Engineer
>> Mobile : - 0774894438
>> Mail : - kanapr...@wso2.com
>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
>> WSO2, Inc.
>> lean . enterprise . middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Pathirennehelage Nadeeshani
> Senior Software Engineer
> Security & Compliance Team
> WSO2 Inc.
> mobile : +94 716545223
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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

Re: [Dev] [Architecture] [Iam-dev] [VOTE] Release WSO2 Identity Server 5.11.0 RC1

[Mushthaq Rumy]

Hi all,

Tested the following flows in an APIM pack with the Identity RC1 release
versions.

   - APIM use cases
   - Password Recovery with Email
   - Self User Registration.
   - Account Locking
   - Password Pattern Validation.

No Blockers found.
[+] Stable - go ahead and release.

Thanks & Regards,
Mushthaq

On Wed, Nov 18, 2020 at 9:35 PM Niluka Sripali Monnankulama 
wrote:

> Hi all,
>  Tested the following without any blockers,
>
>- SCIM2 USER Group CURD
>- Email OTP
>- CURD operation with Console( UniqueIDJDBCUserStoreManager and
>UniqueIDAD)
>- Sanity & Adhoc Test with Console and Myaccount
>
> +1 - go ahead and release
>
> On Wed, Nov 18, 2020 at 8:43 PM Kanapriya Kuleswararajan <
> kanapr...@wso2.com> wrote:
>
>> Hi All,
>>
>> Tested the following and no blocking issues found,
>>
>>1. Workflow user approval with the role and users
>>2. User self-registration (UniqueIDJDBCUserStoreManager secondary
>>user store)
>>3. Ask Password
>>4. SAML SSO/SLO
>>5. Identity Federation with google.
>>6. EmailOTP (Primary and secondary user store
>>(UniqueIDJDBCUserStoreManager))
>>
>> [+] Stable - go ahead and release
>>
>> Thanks
>> Kanapriya Kuleswararajan
>> Senior Software Engineer
>> Mobile : - 0774894438
>> Mail : - kanapr...@wso2.com
>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
>> WSO2, Inc.
>> lean . enterprise . middleware
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Niluka Sripali Monnankulama
> Software Engineer QA - WSO2 Sri Lanka
>
> Mobile : +94 76 76 52843
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Mushthaq Rumy
*Associate Technical Lead*
Mobile : +94 (0) 779 492140
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.

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