Re: [Dev] [IS] Identity Server 5.3.0 Clustering document is missing in Clustering Documentation

[Maneesha Wijesekara]

Thanks a lot Samuel.

Regards
Maneesha

On Thu, Nov 30, 2017 at 1:14 PM, Samuel Gnaniah  wrote:

> Linked to [2]. Thanks for reporting.
>
> --
>
> *Samuel Gnaniah*
> Lead Technical Writer
>
> WSO2 (pvt.) Ltd.
> Colombo, Sri Lanka
> (+94) 773131798 <+94%2077%20313%201798>
>
> On Thu, Nov 30, 2017 at 12:35 PM, Maneesha Wijesekara 
> wrote:
>
>> Hi All,
>>
>> When checking cluster documentation for Identity Server 5.3.0, I've
>> noticed that related documentation was missing from [1]. Any particular
>> reason for excluding this document ?
>>
>> It's better if we can at least link [2] in Clustering Guide for the
>> reference of Identity Server 5.3.0 Clustering.
>>
>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server
>> [2] https://docs.wso2.com/display/IS530/Clustered+Deployment
>>
>> Regards
>> Maneesha
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>
>


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

Re: [Dev] [IS] Identity Server 5.3.0 Clustering document is missing in Clustering Documentation

[Samuel Gnaniah]

Linked to [2]. Thanks for reporting.

--

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Thu, Nov 30, 2017 at 12:35 PM, Maneesha Wijesekara 
wrote:

> Hi All,
>
> When checking cluster documentation for Identity Server 5.3.0, I've
> noticed that related documentation was missing from [1]. Any particular
> reason for excluding this document ?
>
> It's better if we can at least link [2] in Clustering Guide for the
> reference of Identity Server 5.3.0 Clustering.
>
> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server
> [2] https://docs.wso2.com/display/IS530/Clustered+Deployment
>
> Regards
> Maneesha
> --
> 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

[Dev] [IS] Identity Server 5.3.0 Clustering document is missing in Clustering Documentation

[Maneesha Wijesekara]

Hi All,

When checking cluster documentation for Identity Server 5.3.0, I've noticed
that related documentation was missing from [1]. Any particular reason for
excluding this document ?

It's better if we can at least link [2] in Clustering Guide for the
reference of Identity Server 5.3.0 Clustering.

[1] https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server
[2] https://docs.wso2.com/display/IS530/Clustered+Deployment

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

Re: [Dev] How to set the property name="backendServerURL" and property name="mgtConsoleURL" in carbon.xml for the gateway cluster

[Sashika Wijesinghe]

Hi Dushantha,

AFAIK you don't need to manually specify the 'backendServerURL' and
'mgtConsoleURL'
in axis2.xml as it is parameterized.

Regards,
Sashika

On Thu, Nov 30, 2017 at 10:38 AM, Dushantha Batuwita 
wrote:

> Hi  Dev
>
> I'm involved in developing a Gateway cluster and the particulars  are as
> follows
>
>
>- Cluster is developed in the local machine
>- consists of two Gateway Nodes
>- One is a* Gateway worker offset by 3*
>- Other is a *Gateway worker and Manager* *offset by 2*
>- Those nodes are fronted by LB (am.wso2.com)
>
>
>
> I'm configuring the carbon.Xml by setting the well-known address members
> (wka).
>
> My question is while configuring the bellow entry in Gateway worker node
> 
> 
> 
> 
> 
> 
>
>
> what should be the value for *backendServerURL and **mgtConsoleURL*
>
>
>- Should the backendServerURL be the LB address?
>- While mgtConsoleURL being the URL of Manager Gateway node?
>
>
> please advice
>  Regards
>
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set the property name="backendServerURL" and property name="mgtConsoleURL" in carbon.xml for the gateway cluster

[Dushantha Batuwita]

Sorry for the mistake;

The mail should be corrected as follows

The above changes have been done in the

*/repository/conf/axis2/axis2.xml*
by setting the well-known address members (wka).

My question is while configuring the bellow entry in Gateway worker node



https://${hostName}:${
httpsPort}/"/>




what should be the value for *backendServerURL and **mgtConsoleURL*


   - Should the backendServerURL be the LB address?
   - While mgtConsoleURL being the URL of Manager Gateway node?

Regards

On Thu, Nov 30, 2017 at 10:38 AM, Dushantha Batuwita 
wrote:

> Hi  Dev
>
> I'm involved in developing a Gateway cluster and the particulars  are as
> follows
>
>
>- Cluster is developed in the local machine
>- consists of two Gateway Nodes
>- One is a* Gateway worker offset by 3*
>- Other is a *Gateway worker and Manager* *offset by 2*
>- Those nodes are fronted by LB (am.wso2.com)
>
>
>
> I'm configuring the carbon.Xml by setting the well-known address members
> (wka).
>
> My question is while configuring the bellow entry in Gateway worker node
> 
> 
> 
> 
> 
> 
>
>
> what should be the value for *backendServerURL and **mgtConsoleURL*
>
>
>- Should the backendServerURL be the LB address?
>- While mgtConsoleURL being the URL of Manager Gateway node?
>
>
> please advice
>  Regards
>
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010
>



-- 
*Dushantha Nayanajith Chandima Batuwita*
Software Engineer Support | WSO2
dushan...@wso2.com
mobile : 0094777453010
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to set the property name="backendServerURL" and property name="mgtConsoleURL" in carbon.xml for the gateway cluster

[Dushantha Batuwita]

Hi  Dev

I'm involved in developing a Gateway cluster and the particulars  are as
follows


   - Cluster is developed in the local machine
   - consists of two Gateway Nodes
   - One is a* Gateway worker offset by 3*
   - Other is a *Gateway worker and Manager* *offset by 2*
   - Those nodes are fronted by LB (am.wso2.com)



I'm configuring the carbon.Xml by setting the well-known address members
(wka).

My question is while configuring the bellow entry in Gateway worker node








what should be the value for *backendServerURL and **mgtConsoleURL*


   - Should the backendServerURL be the LB address?
   - While mgtConsoleURL being the URL of Manager Gateway node?


please advice
 Regards

-- 
*Dushantha Nayanajith Chandima Batuwita*
Software Engineer Support | WSO2
dushan...@wso2.com
mobile : 0094777453010
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shouldnt we validate issuer id among users in service providers?

[Ishara Karunarathna]

Hi Ushani,

How did you test this scenarios. It does not allow to register two SPs with
same issuer id.

-Ishara

On Thu, Nov 30, 2017 at 8:22 AM, Ushani Balasooriya  wrote:

> Hi IAM team,
>
> Please consider the below scenario.
>
> When I think of a system as an admin and developer personas in a same
> tenant,
>
> 1. Admin registers a service provider as *travelocity* with issuer id as 
> *travelocity.com
> * and assertion consumer url as
> http://localhost:8080/travelocity.com/home.jsp and configure Federated
> IDP as Google
>
> 2. Then developer persona registers a service provider as *travelocity.com
> *  with same issuer id as *travelocity.com
> * and assertion consumer url as
> http://localhost:8080/travelocity.com/home.jsp since it does not validate
> issuer id and configure federated IDP as facebook.
>
> In this scenario, only the *service provider name* will be *validated*
> and *issuer id* will *not be validated.*
>
> Therefore when we try to access service provider, it will federate only
> through google.
>
> This is a very rare negative use case, but when you think of different
> personas, I think this should be considered.
>
> Please correct me if I am wrong.
>
> Thanks,
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


-- 
Ishara Karunarathna
Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Shavindri Dissanayake]

Hi Ushani,

Great! Thank you!

Thanks & Regards
Shavindri Dissanayake
Senior Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Thu, Nov 30, 2017 at 10:12 AM, Ushani Balasooriya 
wrote:

> Hi Shavindri,
>
> I have already created a doc jira [1].
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-7097
>
> Thanks
>
>
> On 30 Nov 2017 10:01 am, "Shavindri Dissanayake" 
> wrote:
>
>> Hi Ushani,
>>
>> Following up. As per Maneesha's reply, there seems to be a doc gap. Can
>> you create a doc JIRA with the doc gap you identified, please?
>>
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Senior Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Wed, Nov 29, 2017 at 5:53 PM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi Ishara,
>>>
>>> Thanks a lot for the clarification.
>>>
>>> Regards,
>>> Ushani
>>>
>>> On 29 Nov 2017 5:46 pm, "Ishara Karunarathna"  wrote:
>>>
 Hi Ushani,


 On Wed, Nov 29, 2017 at 5:26 PM, Ushani Balasooriya 
 wrote:

> Hi IAM Team,
>
> Any update on this?
>
 SP applications are specific to clients and IDP configurations are
 specific to the Sever.

 For example lets say you create an application in FB and you can manage
 it, if needed you assign different users to admin role then only they can
 mange that application.
 And FB support for user name password authentication later they decide
 to add federation authentication support which is an IDP configuration so
 thats managed by FB server admins.

 -Ishara



> Thanks,
> Ushani
>
> On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
> wrote:
>
>> Hi Maneesha,
>>
>> Thanks for the clarification. Appreciate if someone can explain why
>> this behavior is different for SP and IDPs? If there is an explanation
>> would be great to add it in to docs .
>>
>> Thanks,
>> Ushani
>>
>> On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara <
>> manee...@wso2.com> wrote:
>>
>>> Hi Ushani,
>>>
>>> As per the current implementation, a service provider only visible
>>> to the user who created, at first. When creating service providers, by
>>> default a role created as 'Application/{SERVICE_PROVIDER_NAME}. In
>>> order to make the service provider available for the selected users, you
>>> can assign users to this role and SP will visible to them as well.
>>>
>>> +1 to add this to the documents.
>>>
>>> Regards
>>> Maneesha
>>>
>>> On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya <
>>> ush...@wso2.com> wrote:
>>>
 Hi IAM team,

 Please consider the below example.

 1. *admin* user belongs to *admin* role creates a SP named
 *adminsp* and an IDP named *adminidp*

 2. *admin1* user belongs to the same *admin* role creates a SP
 named *admin1sp* and an IDP names *admin1idp*.

 So the current behavior is,
 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
 *adminidp* and *admin1idp*) when they log in to the management
 console.

 2. But they can only see the *SP*  created by themselves. E.g.,
 *admin* can see only *adminsp* and *admin1* can see only *admin1sp*
 .

 Can you please explain whether this contradicting behavior is
 expected or whether this is a bug?

 If not a bug please explain this why and it should go to documents.

 Thanks,
 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


>>>
>>>
>>> --
>>> Maneesha Wijesekara
>>> Software Engineer - QA Team
>>> WSO2 Inc.
>>>
>>> Email: manee...@wso2.com
>>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>>> Mobile: +94712443119
>>>
>>
>>
>>
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


 --
 Ishara Karunarathna
 Technical Lead
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791 <+94%2071%20799%206791>



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

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Ushani Balasooriya]

Hi Shavindri,

I have already created a doc jira [1].

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

Thanks


On 30 Nov 2017 10:01 am, "Shavindri Dissanayake"  wrote:

> Hi Ushani,
>
> Following up. As per Maneesha's reply, there seems to be a doc gap. Can
> you create a doc JIRA with the doc gap you identified, please?
>
>
> Thanks & Regards
> Shavindri Dissanayake
> Senior Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Wed, Nov 29, 2017 at 5:53 PM, Ushani Balasooriya 
> wrote:
>
>> Hi Ishara,
>>
>> Thanks a lot for the clarification.
>>
>> Regards,
>> Ushani
>>
>> On 29 Nov 2017 5:46 pm, "Ishara Karunarathna"  wrote:
>>
>>> Hi Ushani,
>>>
>>>
>>> On Wed, Nov 29, 2017 at 5:26 PM, Ushani Balasooriya 
>>> wrote:
>>>
 Hi IAM Team,

 Any update on this?

>>> SP applications are specific to clients and IDP configurations are
>>> specific to the Sever.
>>>
>>> For example lets say you create an application in FB and you can manage
>>> it, if needed you assign different users to admin role then only they can
>>> mange that application.
>>> And FB support for user name password authentication later they decide
>>> to add federation authentication support which is an IDP configuration so
>>> thats managed by FB server admins.
>>>
>>> -Ishara
>>>
>>>
>>>
 Thanks,
 Ushani

 On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
 wrote:

> Hi Maneesha,
>
> Thanks for the clarification. Appreciate if someone can explain why
> this behavior is different for SP and IDPs? If there is an explanation
> would be great to add it in to docs .
>
> Thanks,
> Ushani
>
> On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara <
> manee...@wso2.com> wrote:
>
>> Hi Ushani,
>>
>> As per the current implementation, a service provider only visible to
>> the user who created, at first. When creating service providers, by 
>> default
>> a role created as 'Application/{SERVICE_PROVIDER_NAME}. In order to
>> make the service provider available for the selected users, you can 
>> assign
>> users to this role and SP will visible to them as well.
>>
>> +1 to add this to the documents.
>>
>> Regards
>> Maneesha
>>
>> On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya > > wrote:
>>
>>> Hi IAM team,
>>>
>>> Please consider the below example.
>>>
>>> 1. *admin* user belongs to *admin* role creates a SP named *adminsp*
>>> and an IDP named *adminidp*
>>>
>>> 2. *admin1* user belongs to the same *admin* role creates a SP
>>> named *admin1sp* and an IDP names *admin1idp*.
>>>
>>> So the current behavior is,
>>> 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
>>> *adminidp* and *admin1idp*) when they log in to the management
>>> console.
>>>
>>> 2. But they can only see the *SP*  created by themselves. E.g.,
>>> *admin* can see only *adminsp* and *admin1* can see only *admin1sp*.
>>>
>>> Can you please explain whether this contradicting behavior is
>>> expected or whether this is a bug?
>>>
>>> If not a bug please explain this why and it should go to documents.
>>>
>>> Thanks,
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>
>
>
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


>>>
>>>
>>> --
>>> Ishara Karunarathna
>>> Technical Lead
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>>> +94717996791 <+94%2071%20799%206791>
>>>
>>>
>>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Shavindri Dissanayake]

Hi Ushani,

Following up. As per Maneesha's reply, there seems to be a doc gap. Can you
create a doc JIRA with the doc gap you identified, please?


Thanks & Regards
Shavindri Dissanayake
Senior Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Wed, Nov 29, 2017 at 5:53 PM, Ushani Balasooriya  wrote:

> Hi Ishara,
>
> Thanks a lot for the clarification.
>
> Regards,
> Ushani
>
> On 29 Nov 2017 5:46 pm, "Ishara Karunarathna"  wrote:
>
>> Hi Ushani,
>>
>>
>> On Wed, Nov 29, 2017 at 5:26 PM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi IAM Team,
>>>
>>> Any update on this?
>>>
>> SP applications are specific to clients and IDP configurations are
>> specific to the Sever.
>>
>> For example lets say you create an application in FB and you can manage
>> it, if needed you assign different users to admin role then only they can
>> mange that application.
>> And FB support for user name password authentication later they decide to
>> add federation authentication support which is an IDP configuration so
>> thats managed by FB server admins.
>>
>> -Ishara
>>
>>
>>
>>> Thanks,
>>> Ushani
>>>
>>> On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
>>> wrote:
>>>
 Hi Maneesha,

 Thanks for the clarification. Appreciate if someone can explain why
 this behavior is different for SP and IDPs? If there is an explanation
 would be great to add it in to docs .

 Thanks,
 Ushani

 On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara <
 manee...@wso2.com> wrote:

> Hi Ushani,
>
> As per the current implementation, a service provider only visible to
> the user who created, at first. When creating service providers, by 
> default
> a role created as 'Application/{SERVICE_PROVIDER_NAME}. In order to
> make the service provider available for the selected users, you can assign
> users to this role and SP will visible to them as well.
>
> +1 to add this to the documents.
>
> Regards
> Maneesha
>
> On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya 
> wrote:
>
>> Hi IAM team,
>>
>> Please consider the below example.
>>
>> 1. *admin* user belongs to *admin* role creates a SP named *adminsp*
>> and an IDP named *adminidp*
>>
>> 2. *admin1* user belongs to the same *admin* role creates a SP named
>> *admin1sp* and an IDP names *admin1idp*.
>>
>> So the current behavior is,
>> 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
>> *adminidp* and *admin1idp*) when they log in to the management
>> console.
>>
>> 2. But they can only see the *SP*  created by themselves. E.g.,
>> *admin* can see only *adminsp* and *admin1* can see only *admin1sp*.
>>
>> Can you please explain whether this contradicting behavior is
>> expected or whether this is a bug?
>>
>> If not a bug please explain this why and it should go to documents.
>>
>> Thanks,
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
> Maneesha Wijesekara
> Software Engineer - QA Team
> WSO2 Inc.
>
> Email: manee...@wso2.com
> Linkedin: http://linkedin.com/in/maneeshawijesekara
> Mobile: +94712443119
>



 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


>>>
>>>
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>
>>
>> --
>> Ishara Karunarathna
>> Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <+94%2071%20799%206791>
>>
>>
>>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Praminda Jayawardana]

Hi Fazlan,

I've pointed [1] to this information.

[1]: https://docs.wso2.com/display/AM200/Configuring+APIM+Analytics

Thanks,
Praminda

On Wed, Nov 29, 2017 at 4:49 PM, Fazlan Nazeem  wrote:

> Can we please add this info to the apim analytics docs please.
>
> On Wed, Nov 29, 2017 at 4:22 PM, Praminda Jayawardana 
> wrote:
>
>> Thanks Rukshan and Sajith. I'll refer this doc.
>>
>> On Wed, Nov 29, 2017 at 4:11 PM, Sajith Perera  wrote:
>>
>>> Hi Preminda,
>>>
>>> DAS_AGENT uses databridge publisher, so you can setup the DAS thrift
>>> urls relevant to your use case. Pleas follow the steps given in the doc 1.
>>>
>>> [1] - https://docs.wso2.com/m/mobile.action#page/47530694
>>>
>>> On Wed, Nov 29, 2017 at 3:57 PM Praminda Jayawardana 
>>> wrote:
>>>
 Hi All,

 If I have multiple analytics nodes configured and I need to publish to
 all nodes, how can I configure DAS_AGENT.url in log4j.properties? Will
 comma separated values work?
 Ex:
 log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613

 Thanks,
 Praminda

 --

 *Praminda Jayawardana*
 Software Engineer
 WSO2 Inc.; http://wso2.com
 Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>

>>> --
>>> 
>>> Sajith Dimal
>>> Software Engineer
>>> Email : saji...@wso2.com
>>> Mobile : +94783101496
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>>
>> *Praminda Jayawardana*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>>
>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 

*Praminda Jayawardana*
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

Re: [Dev] Shouldnt we validate issuer id among users in service providers?

[Ushani Balasooriya]

Addition to above, the main problem in this scenario is,
When you figure out SP issuer ID is duplicate and if you delete one of
those SP belong to one user, it will delete the issuer id and the assertion
consumer url of the other SP as well which can cause an issue that can hide
the actual root cause.

On Thu, Nov 30, 2017 at 8:22 AM, Ushani Balasooriya  wrote:

> Hi IAM team,
>
> Please consider the below scenario.
>
> When I think of a system as an admin and developer personas in a same
> tenant,
>
> 1. Admin registers a service provider as *travelocity* with issuer id as 
> *travelocity.com
> * and assertion consumer url as
> http://localhost:8080/travelocity.com/home.jsp and configure Federated
> IDP as Google
>
> 2. Then developer persona registers a service provider as *travelocity.com
> *  with same issuer id as *travelocity.com
> * and assertion consumer url as
> http://localhost:8080/travelocity.com/home.jsp since it does not validate
> issuer id and configure federated IDP as facebook.
>
> In this scenario, only the *service provider name* will be *validated*
> and *issuer id* will *not be validated.*
>
> Therefore when we try to access service provider, it will federate only
> through google.
>
> This is a very rare negative use case, but when you think of different
> personas, I think this should be considered.
>
> Please correct me if I am wrong.
>
> Thanks,
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


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

[Dev] Shouldnt we validate issuer id among users in service providers?

[Ushani Balasooriya]

Hi IAM team,

Please consider the below scenario.

When I think of a system as an admin and developer personas in a same
tenant,

1. Admin registers a service provider as *travelocity* with issuer id
as *travelocity.com
* and assertion consumer url as
http://localhost:8080/travelocity.com/home.jsp and configure Federated IDP
as Google

2. Then developer persona registers a service provider as *travelocity.com
*  with same issuer id as *travelocity.com
* and assertion consumer url as
http://localhost:8080/travelocity.com/home.jsp since it does not validate
issuer id and configure federated IDP as facebook.

In this scenario, only the *service provider name* will be *validated*
and *issuer
id* will *not be validated.*

Therefore when we try to access service provider, it will federate only
through google.

This is a very rare negative use case, but when you think of different
personas, I think this should be considered.

Please correct me if I am wrong.

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

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Irham Iqbal]

Hi Sashika,

I recently tried the billing engine war by deploying it on APIM 2.1.0 it
self, it worked for me without any issue.

Thanks,
Iqbal

On Wed, Nov 29, 2017 at 5:08 PM, Sashika Wijesinghe 
wrote:

> Hi Rukshan,
>
> Thanks for the quick response. I have used the billing engine version
> linked in the APIM documentation (1.2.0).
>
> Further, I have tried with the artefacts you shared in [1] but still
> getting the same issue even after manually executing all the available
> analytics scripts.
>
> Attached the tomcat logs and application logs.
>
> Thanks
> Sashika
>
>
> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>
> On Wed, Nov 29, 2017 at 2:39 PM, Rukshan Premathunga 
> wrote:
>
>> Hi Sashika,
>>
>> Which billing engine version did you check? Can you check on the
>> following[1] if not already. *invoice* table is empty because invoice
>> generation is failed. Also in the billing capp, it take time to generate
>> summary tables and please wait bit longer or execute the script manually to
>> generate data. If you observed this again, can you please attached the full
>> log as well?
>>
>> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>>
>> Thanks and Regards
>>
>> On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tried to generate an invoice for the monetized APIs as documented
>>> in [1].
>>>
>>> When I select the 'invoice' tab in the sample billing engine to generate
>>> the invoices observed the following error from the billing engine deployed
>>> in tomcat server.
>>>
>>> *HTTP Status 500 - Request processing failed; nested exception is
>>> org.springframework.webflow.execution.ActionExecutionException: Exception
>>> thrown executing [AnnotatedAction@3fa06082 targetAction =
>>> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
>>> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
>>> 'invoiceHome' of flow 'account' -- action execution attributes were
>>> 'map[[empty]]'*
>>>
>>> After verifying the 'billing' database observed that there are
>>> no records in the "*invoice*" table.  However, as per the API
>>> statistics, there are 20 API calls for that particular API.
>>>
>>> May I know how to solve this issue?
>>>
>>>
>>> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>>>
>>>
>>> --
>>>
>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 774537487
>>> sash...@wso2.com
>>>
>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>> +94711822074 <+94%2071%20182%202074>
>>
>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Irham Iqbal
Software Engineer
WSO2
phone: +94 777888452

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

Re: [Dev] [C5] Setting TrustStore and KeyStore as Java System properties

[Dulanja Liyanage]

Hi Abimaran,

I'm actually talking about the following two System properties. They are
used only for SSL:

   - javax.net.ssl.keyStore
   - javax.net.ssl.trustStore

IIRC these were set during the bootstrap time in C4.

Thanks,
Dulanja


On Wed, Nov 29, 2017 at 5:18 PM, Abimaran Kugathasan 
wrote:

> Hi Dulanja,
>
> If we set these keystores through system properties, we will be losing
> the flexibility of having different keystore for different purposes like
> SSL, JWT signing, etc.
>
> On Wed, Nov 29, 2017 at 4:09 PM, Dulanja Liyanage 
> wrote:
>
>> Hi All,
>>
>> From the conversations I had with some of the developers, it seems
>> $subject is not done from the kernel level. Is my understanding correct?
>>
>> If so, any particular reason for not doing this from the kernel level?
>>
>> Thanks,
>> Dulanja
>>
>> --
>> Thanks & Regards,
>> Dulanja Liyanage
>> Lead, Platform Security Team
>> WSO2 Inc.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <077%20392%202820>
>
> 
> 
>   
> 
>
>


-- 
Thanks & Regards,
Dulanja Liyanage
Lead, Platform Security Team
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Ushani Balasooriya]

Hi Ishara,

Thanks a lot for the clarification.

Regards,
Ushani

On 29 Nov 2017 5:46 pm, "Ishara Karunarathna"  wrote:

> Hi Ushani,
>
>
> On Wed, Nov 29, 2017 at 5:26 PM, Ushani Balasooriya 
> wrote:
>
>> Hi IAM Team,
>>
>> Any update on this?
>>
> SP applications are specific to clients and IDP configurations are
> specific to the Sever.
>
> For example lets say you create an application in FB and you can manage
> it, if needed you assign different users to admin role then only they can
> mange that application.
> And FB support for user name password authentication later they decide to
> add federation authentication support which is an IDP configuration so
> thats managed by FB server admins.
>
> -Ishara
>
>
>
>> Thanks,
>> Ushani
>>
>> On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi Maneesha,
>>>
>>> Thanks for the clarification. Appreciate if someone can explain why this
>>> behavior is different for SP and IDPs? If there is an explanation would be
>>> great to add it in to docs .
>>>
>>> Thanks,
>>> Ushani
>>>
>>> On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara >> > wrote:
>>>
 Hi Ushani,

 As per the current implementation, a service provider only visible to
 the user who created, at first. When creating service providers, by default
 a role created as 'Application/{SERVICE_PROVIDER_NAME}. In order to
 make the service provider available for the selected users, you can assign
 users to this role and SP will visible to them as well.

 +1 to add this to the documents.

 Regards
 Maneesha

 On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya 
 wrote:

> Hi IAM team,
>
> Please consider the below example.
>
> 1. *admin* user belongs to *admin* role creates a SP named *adminsp*
> and an IDP named *adminidp*
>
> 2. *admin1* user belongs to the same *admin* role creates a SP named
> *admin1sp* and an IDP names *admin1idp*.
>
> So the current behavior is,
> 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
> *adminidp* and *admin1idp*) when they log in to the management
> console.
>
> 2. But they can only see the *SP*  created by themselves. E.g.,
> *admin* can see only *adminsp* and *admin1* can see only *admin1sp*.
>
> Can you please explain whether this contradicting behavior is expected
> or whether this is a bug?
>
> If not a bug please explain this why and it should go to documents.
>
> Thanks,
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


 --
 Maneesha Wijesekara
 Software Engineer - QA Team
 WSO2 Inc.

 Email: manee...@wso2.com
 Linkedin: http://linkedin.com/in/maneeshawijesekara
 Mobile: +94712443119

>>>
>>>
>>>
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>
>>
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
> Ishara Karunarathna
> Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Ishara Karunarathna]

Hi Ushani,


On Wed, Nov 29, 2017 at 5:26 PM, Ushani Balasooriya  wrote:

> Hi IAM Team,
>
> Any update on this?
>
SP applications are specific to clients and IDP configurations are specific
to the Sever.

For example lets say you create an application in FB and you can manage it,
if needed you assign different users to admin role then only they can mange
that application.
And FB support for user name password authentication later they decide to
add federation authentication support which is an IDP configuration so
thats managed by FB server admins.

-Ishara



> Thanks,
> Ushani
>
> On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
> wrote:
>
>> Hi Maneesha,
>>
>> Thanks for the clarification. Appreciate if someone can explain why this
>> behavior is different for SP and IDPs? If there is an explanation would be
>> great to add it in to docs .
>>
>> Thanks,
>> Ushani
>>
>> On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara 
>> wrote:
>>
>>> Hi Ushani,
>>>
>>> As per the current implementation, a service provider only visible to
>>> the user who created, at first. When creating service providers, by default
>>> a role created as 'Application/{SERVICE_PROVIDER_NAME}. In order to
>>> make the service provider available for the selected users, you can assign
>>> users to this role and SP will visible to them as well.
>>>
>>> +1 to add this to the documents.
>>>
>>> Regards
>>> Maneesha
>>>
>>> On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya 
>>> wrote:
>>>
 Hi IAM team,

 Please consider the below example.

 1. *admin* user belongs to *admin* role creates a SP named *adminsp*
 and an IDP named *adminidp*

 2. *admin1* user belongs to the same *admin* role creates a SP named
 *admin1sp* and an IDP names *admin1idp*.

 So the current behavior is,
 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
 *adminidp* and *admin1idp*) when they log in to the management
 console.

 2. But they can only see the *SP*  created by themselves. E.g., *admin*
 can see only *adminsp* and *admin1* can see only *admin1sp*.

 Can you please explain whether this contradicting behavior is expected
 or whether this is a bug?

 If not a bug please explain this why and it should go to documents.

 Thanks,
 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


>>>
>>>
>>> --
>>> Maneesha Wijesekara
>>> Software Engineer - QA Team
>>> WSO2 Inc.
>>>
>>> Email: manee...@wso2.com
>>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>>> Mobile: +94712443119
>>>
>>
>>
>>
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


-- 
Ishara Karunarathna
Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the correct way to display service providers and identity providers for different admin role users

[Ushani Balasooriya]

Hi IAM Team,

Any update on this?

Thanks,
Ushani

On Wed, Nov 29, 2017 at 11:47 AM, Ushani Balasooriya 
wrote:

> Hi Maneesha,
>
> Thanks for the clarification. Appreciate if someone can explain why this
> behavior is different for SP and IDPs? If there is an explanation would be
> great to add it in to docs .
>
> Thanks,
> Ushani
>
> On Wed, Nov 29, 2017 at 11:42 AM, Maneesha Wijesekara 
> wrote:
>
>> Hi Ushani,
>>
>> As per the current implementation, a service provider only visible to the
>> user who created, at first. When creating service providers, by default a
>> role created as 'Application/{SERVICE_PROVIDER_NAME}. In order to make
>> the service provider available for the selected users, you can assign users
>> to this role and SP will visible to them as well.
>>
>> +1 to add this to the documents.
>>
>> Regards
>> Maneesha
>>
>> On Wed, Nov 29, 2017 at 11:02 AM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi IAM team,
>>>
>>> Please consider the below example.
>>>
>>> 1. *admin* user belongs to *admin* role creates a SP named *adminsp*
>>> and an IDP named *adminidp*
>>>
>>> 2. *admin1* user belongs to the same *admin* role creates a SP named
>>> *admin1sp* and an IDP names *admin1idp*.
>>>
>>> So the current behavior is,
>>> 1. Both *admin* and *admin1* users can see the existing *IDPs*  (
>>> *adminidp* and *admin1idp*) when they log in to the management console.
>>>
>>> 2. But they can only see the *SP*  created by themselves. E.g., *admin*
>>> can see only *adminsp* and *admin1* can see only *admin1sp*.
>>>
>>> Can you please explain whether this contradicting behavior is expected
>>> or whether this is a bug?
>>>
>>> If not a bug please explain this why and it should go to documents.
>>>
>>> Thanks,
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>
>
>
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


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

Re: [Dev] [C5] Setting TrustStore and KeyStore as Java System properties

[Abimaran Kugathasan]

Hi Dulanja,

If we set these keystores through system properties, we will be losing
the flexibility of having different keystore for different purposes like
SSL, JWT signing, etc.

On Wed, Nov 29, 2017 at 4:09 PM, Dulanja Liyanage  wrote:

> Hi All,
>
> From the conversations I had with some of the developers, it seems
> $subject is not done from the kernel level. Is my understanding correct?
>
> If so, any particular reason for not doing this from the kernel level?
>
> Thanks,
> Dulanja
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Sashika Wijesinghe]

Hi Rukshan,

Thanks for the quick response. I have used the billing engine version
linked in the APIM documentation (1.2.0).

Further, I have tried with the artefacts you shared in [1] but still
getting the same issue even after manually executing all the available
analytics scripts.

Attached the tomcat logs and application logs.

Thanks
Sashika


[1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0

On Wed, Nov 29, 2017 at 2:39 PM, Rukshan Premathunga 
wrote:

> Hi Sashika,
>
> Which billing engine version did you check? Can you check on the
> following[1] if not already. *invoice* table is empty because invoice
> generation is failed. Also in the billing capp, it take time to generate
> summary tables and please wait bit longer or execute the script manually to
> generate data. If you observed this again, can you please attached the full
> log as well?
>
> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>
> Thanks and Regards
>
> On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> I have tried to generate an invoice for the monetized APIs as documented
>> in [1].
>>
>> When I select the 'invoice' tab in the sample billing engine to generate
>> the invoices observed the following error from the billing engine deployed
>> in tomcat server.
>>
>> *HTTP Status 500 - Request processing failed; nested exception is
>> org.springframework.webflow.execution.ActionExecutionException: Exception
>> thrown executing [AnnotatedAction@3fa06082 targetAction =
>> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
>> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
>> 'invoiceHome' of flow 'account' -- action execution attributes were
>> 'map[[empty]]'*
>>
>> After verifying the 'billing' database observed that there are no records
>> in the "*invoice*" table.  However, as per the API statistics, there are
>> 20 API calls for that particular API.
>>
>> May I know how to solve this issue?
>>
>>
>> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
> +94711822074 <+94%2071%20182%202074>
>



-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com


catalina.out
Description: Binary data
HTTP Status 500 - Request processing failed; nested exception is org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@69db59a4 targetAction = [EvaluateAction@408aee5d expression = invoiceService.createInvoice(user), resultExpression = viewScope.invoice], attributes = map[[empty]]] in state 'invoiceHome' of flow 'account' -- action execution attributes were 'map[[empty]]'

type Exception report

message Request processing failed; nested exception is org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@69db59a4 targetAction = [EvaluateAction@408aee5d expression = invoiceService.createInvoice(user), resultExpression = viewScope.invoice], attributes = map[[empty]]] in state 'invoiceHome' of flow 'account' -- action execution attributes were 'map[[empty]]'

description The server encountered an internal error that prevented it from fulfilling this request.

exception

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@69db59a4 targetAction = [EvaluateAction@408aee5d expression = invoiceService.createInvoice(user), resultExpression = viewScope.invoice], attributes = map[[empty]]] in state 'invoiceHome' of flow 'account' -- action execution attributes were 'map[[empty]]'
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:894)
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
	org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
	org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
	org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
	org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
	org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
	org.springframework.security

Re: [Dev] How to validate email adddress

[Senuwan Withana]

Hi Team,

Regular expression should be like below




Regards,

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Nov 28, 2017 at 2:18 PM, Dilusha Alphonso  wrote:

> Hi,
>
> Thank you for the response. I changed my configuration as mentioned above
> it's working.
>
> Thanks
> Dilusha
>
>
> On Mon, Nov 27, 2017 at 3:35 PM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Also you need to use the template with + sign since its value can contain
>> @
>>
>> uri-template="/{*+*id}"
>>
>> Regards
>> Senduran
>>
>>
>>
>>
>> On Mon, Nov 27, 2017 at 3:24 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Dilusha,
>>>
>>> Since you have defined is as path parameter in the template, you must
>>> use 'uri.var.id' instead of 'query.param.id' in the filter mediator
>>> like below.
>>>
>>> >> regex="/^([A-Za-z0-9_\-\.])+\@([A-Za-z0-9_\-\.])+\.([A-Za-z]{2,4})$/">
>>>
>>> On Sat, Nov 25, 2017 at 11:37 AM, Dilusha Alphonso 
>>> wrote:
>>>
 Hi All,

 Requirement: I need to check a condition " Patient ID is the email
 address of given patient". When I give any string to the ID, it must be an
 email address. I have to validate ID whether it is in email format. For
 this, I used the filter mediator in ESB, But I noticed my request didn't go
 through that filter mediator.

 I attached my API configuration in ESB. Please, anyone, help me to
 validate the email address with ID.

 http://ws.apache.org/ns/synapse"; name="Durdan"
 context="/test">

   
  
  >>> regex="/^([A-Za-z0-9_\-\.])+\@([A-Za-z0-9_\-\.])+\.([A-Za-z]{2,4})$/">
 


   
  http://schemas.
 xmlsoap.org/soap/envelope/">
 
17
 
 
http://service.sample.durdans.com";>
   $1

 
  
   
   
  
   


>>> scope="transport"/>

   
  
   


>>> value="application/soap+xml" scope="axis2" type="STRING"/>
 
 

   >>> value="deef"/>

 
  
   
   
  
   

 

 Thanks
 Dilusha





 before loop back to out sequence whether the USER_NAME and PATIENT_ID
 are equal.

 --


 *Best Regards,Dilusha Alphonso*

 *Software Engineer - Support Team*


 *WSO2*
 *Mobile : *

 *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
 *

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


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>>
>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Fazlan Nazeem]

Can we please add this info to the apim analytics docs please.

On Wed, Nov 29, 2017 at 4:22 PM, Praminda Jayawardana 
wrote:

> Thanks Rukshan and Sajith. I'll refer this doc.
>
> On Wed, Nov 29, 2017 at 4:11 PM, Sajith Perera  wrote:
>
>> Hi Preminda,
>>
>> DAS_AGENT uses databridge publisher, so you can setup the DAS thrift urls
>> relevant to your use case. Pleas follow the steps given in the doc 1.
>>
>> [1] - https://docs.wso2.com/m/mobile.action#page/47530694
>>
>> On Wed, Nov 29, 2017 at 3:57 PM Praminda Jayawardana 
>> wrote:
>>
>>> Hi All,
>>>
>>> If I have multiple analytics nodes configured and I need to publish to
>>> all nodes, how can I configure DAS_AGENT.url in log4j.properties? Will
>>> comma separated values work?
>>> Ex:
>>> log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613
>>>
>>> Thanks,
>>> Praminda
>>>
>>> --
>>>
>>> *Praminda Jayawardana*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>>>
>> --
>> 
>> Sajith Dimal
>> Software Engineer
>> Email : saji...@wso2.com
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>



-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior 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

[Dev] ACK interleaving

[Marco Sessa]

Hi All,
I am struggling with an drawback related to ACK interleaving on a HL7 proxy
(EI 6.1.0).
In some conditions (parallel request to the same proxy) the system sender
seems to receive Interleaved ACKs .
I have no control on sender(and on receiver) system and in the log the ACKs
come in to the correct sequence.
In the Analytics profile the messages and relative ACK are paired
correctly, but the sender receive a wrokg ACKs for some request.

The proxy is in attachment

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


Thank in advance
Marco

*Marco Sessa*


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

http://ws.apache.org/ns/synapse";>





























200
false
9298
false
50
5000

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

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Praminda Jayawardana]

Thanks Rukshan and Sajith. I'll refer this doc.

On Wed, Nov 29, 2017 at 4:11 PM, Sajith Perera  wrote:

> Hi Preminda,
>
> DAS_AGENT uses databridge publisher, so you can setup the DAS thrift urls
> relevant to your use case. Pleas follow the steps given in the doc 1.
>
> [1] - https://docs.wso2.com/m/mobile.action#page/47530694
>
> On Wed, Nov 29, 2017 at 3:57 PM Praminda Jayawardana 
> wrote:
>
>> Hi All,
>>
>> If I have multiple analytics nodes configured and I need to publish to
>> all nodes, how can I configure DAS_AGENT.url in log4j.properties? Will
>> comma separated values work?
>> Ex:
>> log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613
>>
>> Thanks,
>> Praminda
>>
>> --
>>
>> *Praminda Jayawardana*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>>
> --
> 
> Sajith Dimal
> Software Engineer
> Email : saji...@wso2.com
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 

*Praminda Jayawardana*
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

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Sajith Perera]

Hi Preminda,

DAS_AGENT uses databridge publisher, so you can setup the DAS thrift urls
relevant to your use case. Pleas follow the steps given in the doc 1.

[1] - https://docs.wso2.com/m/mobile.action#page/47530694

On Wed, Nov 29, 2017 at 3:57 PM Praminda Jayawardana 
wrote:

> Hi All,
>
> If I have multiple analytics nodes configured and I need to publish to all
> nodes, how can I configure DAS_AGENT.url in log4j.properties? Will comma
> separated values work?
> Ex:
> log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613
>
> Thanks,
> Praminda
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918
>
-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [C5] Setting TrustStore and KeyStore as Java System properties

[Dulanja Liyanage]

Hi All,

>From the conversations I had with some of the developers, it seems $subject
is not done from the kernel level. Is my understanding correct?

If so, any particular reason for not doing this from the kernel level?

Thanks,
Dulanja

-- 
Thanks & Regards,
Dulanja Liyanage
Lead, Platform Security Team
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Rukshan Premathunga]

Hi Praminda,

You want to send a event to all the nodes? That's mean with with
duplication? If so you can use multiple URL groups like {ip1},{ip2},{ip3}
etc.

But i think, since we have enable event sync in the event receivers,
fail-over or load balancing is sufficient.
For more about the event receiver configuration please check following
document[1]

[1]
https://docs.wso2.com/display/DAS310/Setting+up+Multi+Receiver+and+Load+Balancing+Data+Agent

Thanks and Regards

On Wed, Nov 29, 2017 at 3:57 PM, Praminda Jayawardana 
wrote:

> Hi All,
>
> If I have multiple analytics nodes configured and I need to publish to all
> nodes, how can I configure DAS_AGENT.url in log4j.properties? Will comma
> separated values work?
> Ex:
> log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613
>
> Thanks,
> Praminda
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>



-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Praminda Jayawardana]

Hi All,

If I have multiple analytics nodes configured and I need to publish to all
nodes, how can I configure DAS_AGENT.url in log4j.properties? Will comma
separated values work?
Ex:
log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613

Thanks,
Praminda

-- 

*Praminda Jayawardana*
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

Re: [Dev] Please review and merge

[Danesh Kuruppu]

Hi Nuwandi,

Reviewed and merged the PR[1]

1. https://github.com/wso2/carbon-registry/pull/268

Thanks
Danesh

On Wed, Nov 29, 2017 at 1:41 PM, Nuwandi Wickramasinghe 
wrote:

> Hi,
>
> Please review and merge [1]
>
> [1] https://github.com/wso2/carbon-registry/pull/264
>
> thanks
> Nuwandi
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Senior Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>



-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
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

[Krishan Wijesena]

Hi shanika,

did you use "Gmail" authentications(username/password)
in output-event-adapters.xml. you need do setup[1]

[1] https://support.google.com/mail/answer/7104828?hl=en

Thanks,
krishan.

On Wed, Nov 29, 2017 at 3:07 PM, Mushthaq Rumy  wrote:

> 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 <
>> shani...@wso2.com> 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
>>>
>>> 
>>>
>>
>>
>>
>> --
>> *Shanika Wickramasinghe*
>> Software Engineer - QA Team
>>
>> Email: shani...@wso2.com
>> Mobile  : +94713503563 <+94%2071%20350%203563>
>> Web : http://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.
>
> 
>
> ___
> 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
WSO2 Inc : http://wso2.com
[image: 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

[Chamin Dias]

Hi,

You can try the instructions in this document
 and add the
corresponding user with necessary privileges and try it.

Thanks.

On Wed, Nov 29, 2017 at 3:07 PM, Mushthaq Rumy  wrote:

> 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 <
>> shani...@wso2.com> 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
>>>
>>> 
>>>
>>
>>
>>
>> --
>> *Shanika Wickramasinghe*
>> Software Engineer - QA Team
>>
>> Email: shani...@wso2.com
>> Mobile  : +94713503563 <+94%2071%20350%203563>
>> Web : http://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.
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stress Test Google Federated Authenticator as IDP

[Chankami Maddumage]

Hi Ishara,

Thanks for the suggestion.

On Wed, Nov 29, 2017 at 3:18 PM, Ishara Karunarathna 
wrote:

> HI Chankami,
>
> In this cases these IDPs will identify these request as an attack and
> block. And I don't think its useful to load the IDP.
> I think your objective is to check whether IS can handle federation flow.
>
> In that case you can use another IS as a IDP and do the test.
>
> -Ishara
>
> On Wed, Nov 29, 2017 at 3:03 PM, Chankami Maddumage 
> wrote:
>
>> Hi All
>>
>> We have a solution  to automate Google federated authenticator as IDP
>> where travelocity is used as SP.
>>
>> I have used Jmeter to automate this scenario. When I access my SP,
>> travelocity, it redirects to the Federated IDP Google Login page. Ideally
>> if I login via Google login page, it redirects me to the tavelocity logged
>> in page.
>>
>> When I capture the request, I can see multiple parameters which are
>> auto-generated from Google side is passed for the login request.
>>
>> Also, When we try to load test Google side, they block our requests.
>>
>> My question is, since I am in a process to Stress test WSO2 IS  federated
>> authenticator login scenario, please advice me up to which level I should
>> do the stress testing?
>>
>>
>> Example, should I stress test only up to the login page or is there any
>> other correct way to proceed with this scenario.
>>
>>
>> This problem is there for other connectors like Facebook, twitter etc
>>
>> --
>> Best Regards,
>>
>>
>> *Chankami Maddumage*
>> Software Engineer - QA Team
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
>>
>>
>
>
> --
> Ishara Karunarathna
> Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>


-- 
Best Regards,


*Chankami Maddumage*
Software Engineer - QA Team
WSO2 Inc; http://www.wso2.com/.
Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stress Test Google Federated Authenticator as IDP

[Ishara Karunarathna]

HI Chankami,

In this cases these IDPs will identify these request as an attack and
block. And I don't think its useful to load the IDP.
I think your objective is to check whether IS can handle federation flow.

In that case you can use another IS as a IDP and do the test.

-Ishara

On Wed, Nov 29, 2017 at 3:03 PM, Chankami Maddumage 
wrote:

> Hi All
>
> We have a solution  to automate Google federated authenticator as IDP
> where travelocity is used as SP.
>
> I have used Jmeter to automate this scenario. When I access my SP,
> travelocity, it redirects to the Federated IDP Google Login page. Ideally
> if I login via Google login page, it redirects me to the tavelocity logged
> in page.
>
> When I capture the request, I can see multiple parameters which are
> auto-generated from Google side is passed for the login request.
>
> Also, When we try to load test Google side, they block our requests.
>
> My question is, since I am in a process to Stress test WSO2 IS  federated
> authenticator login scenario, please advice me up to which level I should
> do the stress testing?
>
>
> Example, should I stress test only up to the login page or is there any
> other correct way to proceed with this scenario.
>
>
> This problem is there for other connectors like Facebook, twitter etc
>
> --
> Best Regards,
>
>
> *Chankami Maddumage*
> Software Engineer - QA Team
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
>
>


-- 
Ishara Karunarathna
Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to configure the Cache mediator in ESB 5.0.0

[Susankha Nirmala]

Hi Dilusha,

You can achieve your requirement with below sample API configuration.

http://ws.apache.org/ns/synapse"; name="TestAPI" context="/abc">
   
  
 

 
 

   
  
   


 
 

   http://www.mocky.io/v2/5a158a1f2e5f00eab752"/>

 
  
  
 

 
 
 
  
   


Thanks,
/Susankha.


On Wed, Nov 29, 2017 at 1:34 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> I have created an API in wso2 ESB 5.0.0  to call the SOAP back-end
> service. I have used cache mediator for a normal GET method.  What I want
> is, I have used a GET Method to get some details, I passed the id with the
> URL.
>
> Requirement- When I call the service through API for a given id in the
> first time I need a proper response for particular id, then for next call
> for the same id it should get the response from the cache itself up-to-the
> given Timeout period. if I change the id then it should hit the service.
>
> I attached my configuration.
>
> http://ws.apache.org/ns/synapse"; name="Durdan"
> context="/test">
>  
>   
>  
>   hashGenerator="org.wso2.carbon.mediator.cache.digest.REQUESTHASHGenerator"
> timeout="60">
> 
>  
>  
>   
>
>
>   
>  http://schemas.
> xmlsoap.org/soap/envelope/">
> 
>12
> 
> 
>http://service.
> sample.durdans.com">
>   $1
>
> 
>  
>   
>   
>  
>   
>
>  
>   scope="transport"/>
>  
> 
>
> 
>  
>   
>   
> 
>  
>   
>
> 
>
>
> Above configuration, I was able to get the response for proper id. but
> cache mediator is not working.
>
>
> Can anyone help me to solve this??
>
> Thanks in advance.
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Susankha Nirmala
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware

Mobile : +94 77 593 2146
blog : https://susankhanirmala.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Problem with IP level throttling in distributed setup

[Sanjeewa Malalgoda]

Can you try to spoof your ip address as follows and see what happens. We do
not know what really submit as client IP here.
Or you can intercept message and see what actually goes to client.

curl --header "X-Forwarded-For: 192.168.0.2"

Thanks,
sanjeewa.

On Wed, Nov 29, 2017 at 2:47 PM, Buddhimala Ranasinghe 
wrote:

> Hi Prasanna,
>
> I checked the throttle policy file in the given location and it is updated.
>
> Thanks
>
> On Wed, Nov 29, 2017 at 12:41 PM, Prasanna Dangalla 
> wrote:
>
>> Hi Buddhimala,
>>
>> Can you check the throttle policy file whether the policy is updated or
>> not. Ex: repository/deployment/server/executionplans/carbon.super_res
>> ource_100KKBPerMin_default.siddhiql and repository/deployment/server/e
>> xecutionplans/carbon.super_resource_100KKBPerMin_condition_1.siddhiql
>>
>> Thanks
>>
>> *Prasanna Dangalla*
>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>>
>> *cell: +94 718 11 27 51*
>> *twitter: @prasa77*
>>
>> On Wed, Nov 29, 2017 at 12:34 PM, Buddhimala Ranasinghe <
>> buddhim...@wso2.com> wrote:
>>
>>> Hi Dinusha,Irham,
>>>
>>> I tried header condition throttling as well. The same behavior can be
>>> observed in there also. Throttling out occurs after the default limit and
>>> not after the condition request limit.
>>>
>>> Thanks
>>>
>>> On Wed, Nov 29, 2017 at 12:18 PM, Dinusha Dissanayake >> > wrote:
>>>
 Hi Buddhimala,

 Did you observe this behavior only for IP based throttle condition or
 with other conditions as well (eg. header condition, IP range condition )?

 Thanks,
 DinushaD.

 On Wed, Nov 29, 2017 at 11:47 AM, Buddhimala Ranasinghe <
 buddhim...@wso2.com> wrote:

> Hi All,
>
> I have a distributed deployment in API Manager which contains
>
> 1GW
> Pub+Store+TM
> Is as KM
>
> I tried to implement IP level throttling for my API in this setup. I
> have put 20 as my default equest limit and under IP condition I gave
> request count as 5. I gave my local IP address as the IP condition to
> thrttle out.
> But when I invoked the API, it throttles out at the 21st request and
> not at 6th request.
>
> I also tried the same with another pack where only IS was configured
> as KM (Pub,Store,GW,TM+IS as KM). There I could successfully throttle out
> at the 6th request.
>
> What can be the reason for this behaviour? Can you please help me to
> resolve 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] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Dinusha Dissanayake
 Software Engineer
 WSO2 Inc
 Mobile: +94712939439 <+94%2071%20293%209439>
 

>>>
>>>
>>>
>>> --
>>>
>>>
>>> *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] 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

___
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
>>
>> 
>>
>
>
>
> --
> *Shanika Wickramasinghe*
> Software Engineer - QA Team
>
> Email: shani...@wso2.com
> Mobile  : +94713503563 <+94%2071%20350%203563>
> Web : http://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.


___
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

[Harsha Kumara]

Adding Sam.

@Shanika did you do the configurations specified in the documentation? Did
you see any errors in the log?

The subscriber mail is getting from the user profile of the particular
user, You can go to the user management and check the user profile of your
user. If you haven't set an email please set and try.


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
>>
>> 
>>
>
>
>
> --
> *Shanika Wickramasinghe*
> Software Engineer - QA Team
>
> Email: shani...@wso2.com
> Mobile  : +94713503563 <+94%2071%20350%203563>
> Web : http://wso2.com
>
> 
>



-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stress Test Google Federated Authenticator as IDP

[Chankami Maddumage]

Hi All

We have a solution  to automate Google federated authenticator as IDP where
travelocity is used as SP.

I have used Jmeter to automate this scenario. When I access my SP,
travelocity, it redirects to the Federated IDP Google Login page. Ideally
if I login via Google login page, it redirects me to the tavelocity logged
in page.

When I capture the request, I can see multiple parameters which are
auto-generated from Google side is passed for the login request.

Also, When we try to load test Google side, they block our requests.

My question is, since I am in a process to Stress test WSO2 IS  federated
authenticator login scenario, please advice me up to which level I should
do the stress testing?


Example, should I stress test only up to the login page or is there any
other correct way to proceed with this scenario.


This problem is there for other connectors like Facebook, twitter etc

-- 
Best Regards,


*Chankami Maddumage*
Software Engineer - QA Team
WSO2 Inc; http://www.wso2.com/.
Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Problem with IP level throttling in distributed setup

[Buddhimala Ranasinghe]

Hi Prasanna,

I checked the throttle policy file in the given location and it is updated.

Thanks

On Wed, Nov 29, 2017 at 12:41 PM, Prasanna Dangalla 
wrote:

> Hi Buddhimala,
>
> Can you check the throttle policy file whether the policy is updated or
> not. Ex: repository/deployment/server/executionplans/carbon.super_
> resource_100KKBPerMin_default.siddhiql and repository/deployment/server/
> executionplans/carbon.super_resource_100KKBPerMin_condition_1.siddhiql
>
> Thanks
>
> *Prasanna Dangalla*
> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
>
> *cell: +94 718 11 27 51*
> *twitter: @prasa77*
>
> On Wed, Nov 29, 2017 at 12:34 PM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi Dinusha,Irham,
>>
>> I tried header condition throttling as well. The same behavior can be
>> observed in there also. Throttling out occurs after the default limit and
>> not after the condition request limit.
>>
>> Thanks
>>
>> On Wed, Nov 29, 2017 at 12:18 PM, Dinusha Dissanayake 
>> wrote:
>>
>>> Hi Buddhimala,
>>>
>>> Did you observe this behavior only for IP based throttle condition or
>>> with other conditions as well (eg. header condition, IP range condition )?
>>>
>>> Thanks,
>>> DinushaD.
>>>
>>> On Wed, Nov 29, 2017 at 11:47 AM, Buddhimala Ranasinghe <
>>> buddhim...@wso2.com> wrote:
>>>
 Hi All,

 I have a distributed deployment in API Manager which contains

 1GW
 Pub+Store+TM
 Is as KM

 I tried to implement IP level throttling for my API in this setup. I
 have put 20 as my default equest limit and under IP condition I gave
 request count as 5. I gave my local IP address as the IP condition to
 thrttle out.
 But when I invoked the API, it throttles out at the 21st request and
 not at 6th request.

 I also tried the same with another pack where only IS was configured as
 KM (Pub,Store,GW,TM+IS as KM). There I could successfully throttle out at
 the 6th request.

 What can be the reason for this behaviour? Can you please help me to
 resolve 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] 

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


>>>
>>>
>>> --
>>> Dinusha Dissanayake
>>> Software Engineer
>>> WSO2 Inc
>>> Mobile: +94712939439 <+94%2071%20293%209439>
>>> 
>>>
>>
>>
>>
>> --
>>
>>
>> *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] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 


*Buddhimala Ranasinghe*
Software Engineer-Support Team | WSO2
Emil: buddhim...@wso2.com
Mobile:+94771563138
Web:http://wso2.com
[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Rukshan Premathunga]

Hi Sashika,

Which billing engine version did you check? Can you check on the
following[1] if not already. *invoice* table is empty because invoice
generation is failed. Also in the billing capp, it take time to generate
summary tables and please wait bit longer or execute the script manually to
generate data. If you observed this again, can you please attached the full
log as well?

[1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0

Thanks and Regards

On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
wrote:

> Hi All,
>
> I have tried to generate an invoice for the monetized APIs as documented
> in [1].
>
> When I select the 'invoice' tab in the sample billing engine to generate
> the invoices observed the following error from the billing engine deployed
> in tomcat server.
>
> *HTTP Status 500 - Request processing failed; nested exception is
> org.springframework.webflow.execution.ActionExecutionException: Exception
> thrown executing [AnnotatedAction@3fa06082 targetAction =
> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
> 'invoiceHome' of flow 'account' -- action execution attributes were
> 'map[[empty]]'*
>
> After verifying the 'billing' database observed that there are no records
> in the "*invoice*" table.  However, as per the API statistics, there are
> 20 API calls for that particular API.
>
> May I know how to solve this issue?
>
>
> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>



-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Rukshan Premathunga]

Hi Sashika,

Which billing engine version did you check? Can you check on the
following[1] if not already. *invoice* table is empty because invoice
generation is failed. Also in the billing capp, it take time to generate
summary tables and please wait bit longer or execute the script manually to
generate data. If you observed this again, can you please attached the full
log as well?

[1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0

Thanks and Regards

On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
wrote:

> Hi All,
>
> I have tried to generate an invoice for the monetized APIs as documented
> in [1].
>
> When I select the 'invoice' tab in the sample billing engine to generate
> the invoices observed the following error from the billing engine deployed
> in tomcat server.
>
> *HTTP Status 500 - Request processing failed; nested exception is
> org.springframework.webflow.execution.ActionExecutionException: Exception
> thrown executing [AnnotatedAction@3fa06082 targetAction =
> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
> 'invoiceHome' of flow 'account' -- action execution attributes were
> 'map[[empty]]'*
>
> After verifying the 'billing' database observed that there are no records
> in the "*invoice*" table.  However, as per the API statistics, there are
> 20 API calls for that particular API.
>
> May I know how to solve this issue?
>
>
> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>



-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error after enabling secure vault in APIM 2.2.0 (TBR) pack

[Harsha Kumara]

Hi Tharindu,

I think we need to upgrade the Kernel to get the fix to APIM 2.2.0. We
encounter the same issue in APIM 2.1.0 fresh pack and WUM updated one fixed
it.

Thanks,
Harsha

On Wed, Nov 29, 2017 at 2:23 PM, Tharindu Edirisinghe 
wrote:

> Hi Devs,
>
> I'm trying to build the APIM 2.2.0 (to be released) pack. For that, I
> built the carbon-apimgt [1] and then the product-apim [2]. Build was
> successful and I got the *wso2am-2.2.0-SNAPSHOT* pack.
>
> Then, I need to test secure vault and for that I ran *./ciphertool.sh
> -Dconfigure* from bin directory without changing anything. Then I started
> the pack and it prints the following error and the pack doesn't startup.
>
> [2017-11-29 14:16:20,748]  INFO - TemplateDeployerServiceTrackerDS
> Successfully deployed the execution manager tracker service
>
> *[2017-11-29 14:16:21,528] FATAL - TomcatBundleActivator Error while
> starting server NOT_FOUND_ERR: An attempt is made to reference a node in a
> context where it does not exist.org.w3c.dom.DOMException: NOT_FOUND_ERR: An
> attempt is made to reference a node in a context where it does not exist.*
> at org.apache.xerces.dom.AttributeMap.internalRemoveNamedItem(Unknown
> Source)
> at org.apache.xerces.dom.AttributeMap.removeNamedItem(Unknown Source)
> at org.wso2.carbon.tomcat.internal.ServerManager.init(
> ServerManager.java:107)
> at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.start(
> TomcatBundleActivator.java:45)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(
> BundleContextImpl.java:711)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> startActivator(BundleContextImpl.java:702)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(
> BundleContextImpl.java:683)
> at org.eclipse.osgi.framework.internal.core.BundleHost.
> startWorker(BundleHost.java:381)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.
> resume(AbstractBundle.java:390)
> at org.eclipse.osgi.framework.internal.core.Framework.
> resumeBundle(Framework.java:1176)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.
> resumeBundles(StartLevelManager.java:559)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.
> resumeBundles(StartLevelManager.java:544)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(
> StartLevelManager.java:457)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.
> doSetStartLevel(StartLevelManager.java:243)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.
> dispatchEvent(StartLevelManager.java:438)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.
> dispatchEvent(StartLevelManager.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
>
> It seems this is the same issue reported in [3] (according to JIRA, it's
> already fixed). I tested above scenario with APIM 2.1.0 (both vanilla and
> WUM packs) and there was no error.
>
> So, I guess this should have been introduced in the 2.2.0 pack.
>
> Please check.
>
> [1] https://github.com/wso2/carbon-apimgt/tree/6.x
> [2] https://github.com/wso2/product-apim/tree/2.x
> [3] https://wso2.org/jira/browse/CARBON-16104
>
> Thanks,
> TharinduE
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : http://tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>



-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error after enabling secure vault in APIM 2.2.0 (TBR) pack

[Tharindu Edirisinghe]

Hi Devs,

I'm trying to build the APIM 2.2.0 (to be released) pack. For that, I built
the carbon-apimgt [1] and then the product-apim [2]. Build was successful
and I got the *wso2am-2.2.0-SNAPSHOT* pack.

Then, I need to test secure vault and for that I ran *./ciphertool.sh
-Dconfigure* from bin directory without changing anything. Then I started
the pack and it prints the following error and the pack doesn't startup.

[2017-11-29 14:16:20,748]  INFO - TemplateDeployerServiceTrackerDS
Successfully deployed the execution manager tracker service

*[2017-11-29 14:16:21,528] FATAL - TomcatBundleActivator Error while
starting server NOT_FOUND_ERR: An attempt is made to reference a node in a
context where it does not exist.org.w3c.dom.DOMException: NOT_FOUND_ERR: An
attempt is made to reference a node in a context where it does not exist.*
at org.apache.xerces.dom.AttributeMap.internalRemoveNamedItem(Unknown
Source)
at org.apache.xerces.dom.AttributeMap.removeNamedItem(Unknown Source)
at
org.wso2.carbon.tomcat.internal.ServerManager.init(ServerManager.java:107)
at
org.wso2.carbon.tomcat.internal.TomcatBundleActivator.start(TomcatBundleActivator.java:45)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

It seems this is the same issue reported in [3] (according to JIRA, it's
already fixed). I tested above scenario with APIM 2.1.0 (both vanilla and
WUM packs) and there was no error.

So, I guess this should have been introduced in the 2.2.0 pack.

Please check.

[1] https://github.com/wso2/carbon-apimgt/tree/6.x
[2] https://github.com/wso2/product-apim/tree/2.x
[3] https://wso2.org/jira/browse/CARBON-16104

Thanks,
TharinduE
-- 

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

[Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Sashika Wijesinghe]

Hi All,

I have tried to generate an invoice for the monetized APIs as documented in
[1].

When I select the 'invoice' tab in the sample billing engine to generate
the invoices observed the following error from the billing engine deployed
in tomcat server.

*HTTP Status 500 - Request processing failed; nested exception is
org.springframework.webflow.execution.ActionExecutionException: Exception
thrown executing [AnnotatedAction@3fa06082 targetAction =
[EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
'invoiceHome' of flow 'account' -- action execution attributes were
'map[[empty]]'*

After verifying the 'billing' database observed that there are no records
in the "*invoice*" table.  However, as per the API statistics, there are 20
API calls for that particular API.

May I know how to solve this issue?


[1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs


-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] nginx master_process on; (code=exited, status=1/FAILURE)

[Abimaran Kugathasan]

Hi Dushantha,

There is a chance that apache 2 respawn new instance when you kill earlier
one in Linux. You can change the port to 81, if don't succeed in killing
apache2 process.

On Wed, Nov 29, 2017 at 1:38 PM, Dushantha Batuwita 
wrote:

> Hi Senduran/ Isuru
>
> Many thanks for the advice, and I got the point now.
>
> I installed a fresh nginx because I was thinking that the files might have
> been corrupted as I have tried many things from the internet applying some
> configurations to files in sites-available,sites-enabled as well.
>
> It works fine now.
>
> Cheers
>
>
> On Wed, Nov 29, 2017 at 12:59 PM, Isuru Udana  wrote:
>
>> Hi Dushantha,
>>
>> Installing a fresh nginx doesn't make any difference or any sense as port
>> is occupied by something else :)
>>
>>
>>
>> On Wed, Nov 29, 2017 at 12:49 PM, Dushantha Batuwita 
>> wrote:
>>
>>> Hi Senduran:
>>>
>>> I have tried your command and it is the apache2 process.
>>>
>>> sudo netstat -nlp | grep :80
>>> tcp6   0  0 :::80   :::*
>>> LISTEN  1076/apache2
>>>
>>>
>>>
>>>
>>> further, *when I try installing the nginx freshly* the following error
>>> can be seen too (with details I have mentioned in the above mail)
>>>
>>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>>> [emerg] still could not bind()
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>> nginx.service: Control process exited, code=exited status=1
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: Failed to
>>> start A high performance web server and a reverse proxy server.
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>> nginx.service: Unit entered failed state.
>>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>> nginx.service: Failed with result 'exit-code'.
>>> dpkg: error processing package nginx-core (--configure):
>>>  subprocess installed post-installation script returned error exit
>>> status 1
>>> dpkg: dependency problems prevent configuration of nginx:
>>>  nginx depends on nginx-core (<< 1.10.3-1ubuntu3.1.1~) | nginx-full (<<
>>> 1.10.3-1ubuntu3.1.1~) | nginx-light (<< 1.10.3-1ubuntu3.1.1~) |
>>> nginx-extras (<< 1.10.3-1ubuntu3.1.1~); however:
>>>   Package nginx-core is not configured yet.
>>>   Package nginx-full is not installed.
>>>   Package nginx-light is not installed.
>>>   Package nginx-extras is not installed.
>>>  nginx depends on nginx-core (>= 1.10.3-1ubuntu3.1) | nginx-full (>=
>>> 1.10.3-1ubuntu3.1) | nginx-light (>= 1.10.3-1ubuntu3.1) | nginx-extras (>=
>>> 1.10.3-1ubuntu3.1); however:
>>>   Package nginx-core is not configured yet.
>>>   Package nginx-full is not installed.
>>>   Package nginx-light is not installed.
>>>   Package nginx-extras is not installed.
>>>
>>> dpkg: error processing package nginx (--configure):
>>>  dependency problems - leaving unconfigured
>>> No apport report written because the error message indicates its a
>>> followup error from a previous failure.
>>>
>>>   Processing triggers for ureadahead
>>> (0.100.0-20) ...
>>> Processing triggers for ufw (0.35-5) ...
>>> Errors were encountered while processing:
>>>  nginx-core
>>>  nginx
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>
>>> Kindly advice if I have done something incorrect here
>>>
>>> Regards
>>>
>>>
>>> On Wed, Nov 29, 2017 at 11:21 AM, Senduran Balasubramaniyam <
>>> sendu...@wso2.com> wrote:
>>>
 As the error says "Address already in use" you have to find which
 process is bound to port 80 already. the following command will help you
 identify the process running on port 80

 sudo netstat -nlp | grep :80

 find the process and stop that process first before trying to start the
 nginx

 Regards
 Senduran

 On Wed, Nov 29, 2017 at 11:06 AM, Dushantha Batuwita <
 dushan...@wso2.com> wrote:

> Hi
>
> I completely uninstall NGINX from my machine and reinstalled it again
> and but the NGINX server gives me the same error.
>
> *Things I have done*
>
>
>- I have run the command
>
> sudo netstat -tulpn
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreig

[Dev] Please review and merge

[Nuwandi Wickramasinghe]

Hi,

Please review and merge [1]

[1] https://github.com/wso2/carbon-registry/pull/264

thanks
Nuwandi

-- 

Best Regards,

Nuwandi Wickramasinghe

Senior Software Engineer

WSO2 Inc.

Web : http://wso2.com

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

Re: [Dev] nginx master_process on; (code=exited, status=1/FAILURE)

[Dushantha Batuwita]

Hi Senduran/ Isuru

Many thanks for the advice, and I got the point now.

I installed a fresh nginx because I was thinking that the files might have
been corrupted as I have tried many things from the internet applying some
configurations to files in sites-available,sites-enabled as well.

It works fine now.

Cheers


On Wed, Nov 29, 2017 at 12:59 PM, Isuru Udana  wrote:

> Hi Dushantha,
>
> Installing a fresh nginx doesn't make any difference or any sense as port
> is occupied by something else :)
>
>
>
> On Wed, Nov 29, 2017 at 12:49 PM, Dushantha Batuwita 
> wrote:
>
>> Hi Senduran:
>>
>> I have tried your command and it is the apache2 process.
>>
>> sudo netstat -nlp | grep :80
>> tcp6   0  0 :::80   :::*
>> LISTEN  1076/apache2
>>
>>
>>
>>
>> further, *when I try installing the nginx freshly* the following error
>> can be seen too (with details I have mentioned in the above mail)
>>
>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>> නෙවැ 29 12:31:07 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th nginx[8144]: nginx:
>> [emerg] still could not bind()
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>> nginx.service: Control process exited, code=exited status=1
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: Failed to
>> start A high performance web server and a reverse proxy server.
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>> nginx.service: Unit entered failed state.
>> නෙවැ 29 12:31:08 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>> nginx.service: Failed with result 'exit-code'.
>> dpkg: error processing package nginx-core (--configure):
>>  subprocess installed post-installation script returned error exit status
>> 1
>> dpkg: dependency problems prevent configuration of nginx:
>>  nginx depends on nginx-core (<< 1.10.3-1ubuntu3.1.1~) | nginx-full (<<
>> 1.10.3-1ubuntu3.1.1~) | nginx-light (<< 1.10.3-1ubuntu3.1.1~) |
>> nginx-extras (<< 1.10.3-1ubuntu3.1.1~); however:
>>   Package nginx-core is not configured yet.
>>   Package nginx-full is not installed.
>>   Package nginx-light is not installed.
>>   Package nginx-extras is not installed.
>>  nginx depends on nginx-core (>= 1.10.3-1ubuntu3.1) | nginx-full (>=
>> 1.10.3-1ubuntu3.1) | nginx-light (>= 1.10.3-1ubuntu3.1) | nginx-extras (>=
>> 1.10.3-1ubuntu3.1); however:
>>   Package nginx-core is not configured yet.
>>   Package nginx-full is not installed.
>>   Package nginx-light is not installed.
>>   Package nginx-extras is not installed.
>>
>> dpkg: error processing package nginx (--configure):
>>  dependency problems - leaving unconfigured
>> No apport report written because the error message indicates its a
>> followup error from a previous failure.
>>
>> Processing triggers for ureadahead
>> (0.100.0-20) ...
>> Processing triggers for ufw (0.35-5) ...
>> Errors were encountered while processing:
>>  nginx-core
>>  nginx
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> Kindly advice if I have done something incorrect here
>>
>> Regards
>>
>>
>> On Wed, Nov 29, 2017 at 11:21 AM, Senduran Balasubramaniyam <
>> sendu...@wso2.com> wrote:
>>
>>> As the error says "Address already in use" you have to find which
>>> process is bound to port 80 already. the following command will help you
>>> identify the process running on port 80
>>>
>>> sudo netstat -nlp | grep :80
>>>
>>> find the process and stop that process first before trying to start the
>>> nginx
>>>
>>> Regards
>>> Senduran
>>>
>>> On Wed, Nov 29, 2017 at 11:06 AM, Dushantha Batuwita >> > wrote:
>>>
 Hi

 I completely uninstall NGINX from my machine and reinstalled it again
 and but the NGINX server gives me the same error.

 *Things I have done*


- I have run the command

 sudo netstat -tulpn

 Active Internet connections (only servers)
 Proto Recv-Q Send-Q Local Address   Foreign Address
  State   PID/Program name
 tcp0  0 127.0.0.1:631   0.0.0.0:*
  LISTEN  32365/cupsd
 tcp0  0 0.0.0.0:389 0.0.0.0:*
  LISTEN  1401/slapd
 tcp0  0 0.0.0.0:33060.0.0.0:*
  LISTEN  987/mysqld
 tcp0  0 0.0.0.0:53550.0.0.0:*
  LISTEN  976/systemd-re

[Dev] How to configure the Cache mediator in ESB 5.0.0

[Dilusha Alphonso]

Hi All,

I have created an API in wso2 ESB 5.0.0  to call the SOAP back-end service.
I have used cache mediator for a normal GET method.  What I want is, I have
used a GET Method to get some details, I passed the id with the URL.

Requirement- When I call the service through API for a given id in the
first time I need a proper response for particular id, then for next call
for the same id it should get the response from the cache itself up-to-the
given Timeout period. if I change the id then it should hit the service.

I attached my configuration.

http://ws.apache.org/ns/synapse"; name="Durdan" context="/test">
 
  
 
 

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

   12


   http://service.sample.durdans.com";>
  $1
   

 
  
  
 
  
   
 
 
 

   

 
  
  

 
  
   



Above configuration, I was able to get the response for proper id. but
cache mediator is not working.


Can anyone help me to solve this??

Thanks in advance.
-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

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