Re: [Dev] [DEV] please review and merge

[Senduran Balasubramaniyam]

Hi Daekyung Kim,

Thank you for your contribution.
We will verify the fix and do the necessary

Regards
Senduran



On Tue, Feb 20, 2018 at 12:06 PM, 김대경  wrote:

> Can you please review and merge PR[1] .
>
> [1] https://github.com/wso2/wso2-synapse/pull/1045
>
> Best Regards.
> Daekyung Kim.
>
> ___
> 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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] please review and merge

[김대경]

Can you please review and merge PR[1] .

[1] https://github.com/wso2/wso2-synapse/pull/1045

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

Re: [Dev] Wso2_5.4.0-update-4

[Thanuja Jayasinghe]

Hi Deepak,

Can you please provide the following information,

   1. Is the user authenticated from WSO2 IS or from a federated IdP?
   2. Do you see this warning log for all users or is it for some users?
   3. Is the warning log intermittent?
   4. Can you share the service provider configuration?

Thanks,
Thanuja

On Tue, Feb 20, 2018 at 11:39 AM, Deepak Singla 
wrote:

> Hello Thanuja
>
>
>
> I have installed Wso2_5.4.0-update-4 IS on window environment with
> SQLServer-2014. I am getting below error in carbon logs after some time:
>
>
>
> TID: [-1234] [] [2018-02-12 19:03:48,972]  WARN {org.wso2.carbon.identity.
> application.authentication.framework.handler.claims.impl.DefaultClaimHandler}
> -  Subject claim could not be found amongst service provider mapped
> unfiltered local claims
>
>
>
> TID: [-1234] [] [2018-02-12 19:03:48,972]  WARN {org.wso2.carbon.identity.
> application.authentication.framework.handler.sequence.impl.
> DefaultStepBasedSequenceHandler} -  Subject claim could not be found.
> Defaulting to Name Identifier.
>
> You have mentioned that it is resolved here https://wso2.org/jira/browse/
> IDENTITY-5073, but it is still reproduce able.
>
>
>
> Any suggestion?
>
>
>
> Thanks
>
> Deepak
>



-- 
*Thanuja Lakmal*
Associate Technical Lead
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[Aruna Herath]

On Tue, Feb 20, 2018 at 10:14 AM, SajithAR Ariyarathna 
wrote:

>
>
> On Tue, Feb 20, 2018 at 9:47 AM, Nisala Nanayakkara 
> wrote:
>
>> Hi Sajith,
>>
>> No. I think what we are going to do here is to refer the 'React' which is
>> initialized by the dashboard parent app from the widget level. So setting
>> the React in global context(global.React = React) should be done in the
>> Dashboard parent app.
>>
> +1, even better
>

To be clear this *has* to be done in the parent app. To do this in widgets
would mean that React is bundled with each widget.

>
>
>> So that we can refer it from widgets by using 'externals' in the webpack
>> config.
>>
> We need to document this (putting React as an external dependency and
> using global.React). Is there any docs ATM?
>

Just read the docs. The webpack config contains some unnecessary config for
the HelloWorld.jsx. Like the html, url and css loaders. The webpack config
could be made simpler by removing these. If the user ever comes to need
additional loaders there's enough resources out there to help them figure
it out. :)

Also shall we make a widget code generator using something like yeoman ?
So we can create a configured project for the user for the widget name or
any other config they provide.


>
>> Thanks,
>> Nisala
>>
>> On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna 
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> global.React = React

>>> Can we do above in the parent Widget (https://www.npmjs.com/package
>>> /@wso2-dashboards/widget)? So that the some widget author doesn't need
>>> React as a dependency.
>>>
>>>
>>> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi Aruna,

 +1 for the approach. We have faced a similar issue in Product SP and
 tested the above-mentioned fix in our local environment. It is working 
 fine.

 Thanks,
 Nisala

 On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:

> Loading multiple copies of React in the same page creates problems
> ,
> such as errors with discriptions like "Element ref was specified as a
> string (myRefName) but no owner was set. You may have multiple copies of
> React loaded."
>
> In our dashboards, we have widgets that can be added by dragging and
> dropping. Since it should be possible to add widgets without building the
> whole app, widgets are bundled separate to the parent app. How ever this
> means react is bundled with both the widget and the parent app.
>
> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
> sense if we add the widget as a dependency of the parent app and build the
> parent app only.
>
> To resolve this something we can do is to export React to the global
> scope and allow widgets to use this global reference to React. So we don't
> have to bundle React with widgets.
>
> To put React into global context in the parent dashboard app we can do,
>
> import React from 'react'
> global.React = React
>
> in the widget to use this global React ref instead of bundling use
> webpack externals .
>
> webpack config should be,
>
> externals: {
>   react: 'React'
> }
>
> Instead of the variable name 'React' we can even use some other name
> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>
> --
> Aruna Herath
> Senior Software Engineer | WSO2
> Mobile: 0711 051 799 | 0774 569 555
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Nisala Niroshana Nanayakkara,*
 Software Engineer
 Mobile | +94 717600022
 WSO2 Inc | http://wso2.com/

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


>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>> 
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile | +94 717600022
>> WSO2 Inc | http://wso2.com/
>>
>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
Aruna Herath
Senior Software Engineer | WSO2
Mobile: 0711 051 799 | 0774 569 555


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

Re: [Dev] Query Regarding the JIRA BUG- IDEBTITY-4250

[Sathya Bandara]

Hi Monika,

Have you added the required user attributes under user profile section? If
these attributes are not provided they will not be available in the user
info endpoint response. Please refer [1] for more information.

[1] https://docs.wso2.com/display/IS540/Managing+User+Attributes

Thanks,
Sathya

On Tue, Feb 20, 2018 at 10:30 AM, Darshana Gunawardana 
wrote:

> Hi Monika,
>
> Seems like you haven't subscribed to the dev mailing list properly.. So
> the mails you sent to dev getting on hold.. For the moment, i have fwd the
> mail to the dev mailing list on your behalf..
>
> @Sathya: Can you check on this please..
>
> Thanks,
>
>
> -- Forwarded message --
> From: Monika Sharma 
> Date: Tue, Feb 20, 2018 at 8:29 AM
> Subject: RE: Query Regarding the JIRA BUG- IDEBTITY-4250
> To: Darshana Gunawardana , WSO2 Developers' List <
> dev@wso2.org>
>
>
> Hello sir ,
>
>
>
> Thank you so much for giving your valuable time. I have tried by adding
> requested claims in the SP.
>
> I have added the following request claims in the SP :
>
>
>
> 1.   http://wso2.org/claims/userid
>
> 2.   http://wso2.org/claims/created
>
> 3.   http://wso2.org/claims/country
>
> 4.   http://wso2.org/claims/displayName
>
> 5.   http://wso2.org/claims/emailaddres
>
> 6.   http://wso2.org/claims/givenName
>
> 7.   http://wso2.org/claims/groups
>
>
>
> And subject claim URI is:
>
> 1.   http://wso2.org/claims/emailaddres
>
>
>
> Now response is as below:
>
>
>
> {
>
> "sub”: admin",
>
> "give_name" : "admin",
>
>   "email" : "ad...@wso2.com"
>
> }
>
>
>
> Only few information is displayed. Please let me know is it expected
> result ?
>
>
>
> Thanks & Regards
>
> Monika Sharma
>
>
>
>
>
> *From:* Darshana Gunawardana [mailto:darsh...@wso2.com]
> *Sent:* Saturday, February 17, 2018 10:13 PM
> *To:* Monika Sharma; WSO2 Developers' List
> *Subject:* Re: Query Regarding the JIRA BUG- IDEBTITY-4250
>
>
>
> Hi Monika,
>
>
>
> Have you added requested claims in the SP claim configurations section? If
> you haven't added any requested claims, returning only the subject from the
> userinfo endpoint is expected..
>
>
>
> Try adding requested claims in the SP.
>
>
>
> Regards,
>
>
>
> On Fri, Feb 16, 2018 at 3:29 PM, Monika Sharma <
> monika.sha...@india.nec.com> wrote:
>
> Hello sir,
>
>
>
> I have a query regarding the https://wso2.org/jira/browse/IDENTITY-4250  bug
> of wso2 identity server. It has been fixed in 5.3.0 Beta version of wso2
> identity server. But I am facing the same issue in the 5.3.0 release
> version of wso2 identity server and also verified in the 5.4.0 release
> version, problem is remains in both version. Please check this issue. I
> have followed the below steps to reproduce this issue:
>
> Steps :
>
> 1.   Register a SP for playground app
> Callback URL - http://localhost:8080/playground2/oauth2client
> Allowed Grant Types = Code
>
> 2.   Visit the URL http://localhost:8080/playground2/oauth2.jsp
> and enter the below details
> and submit
> Authorization Grant Type : Authorization Code
> Client ID : (the client id received at the application registration)
> Scope : openid
> Callback URL : http://localhost:8080/playground2/oauth2client
> Authorize Endpoint : https://localhost:9443/oauth2/authorize
>
> 3.   Enter user name and password of the admin and click on login
>
> 4.   Enter callback url and other info
>
> 5.   Enter the user info endpoint and click on get user info
> https://localhost:9443/oauth2/userinfo?schema=openid
>
> I have follow this link to register app https://docs.wso2.com/display/
> IS530/Basic+Client+Profile+with+Playground
>  and
> try to access the user information through the curl command using a valid
> access token
>
>
>
> Issue: Only 'subject' field is returned when userinfo is requested by curl
> command using a valid access token
>
>
>
> e.g  curl -k -H "Authorization: Bearer YOUR_ACCESS_TOKEN" https://loc
> alhost:9443/oauth2/userinfo?schema=openid
>
>
>
> The following response is displayed:
>
> {"sub":"admin”}
>
>
>
> But Expected response should be displayed as below
>
> {
>
>"sub":"admin",
>
>"email":"ad...@wso2.com",
>
>"website":"https://wso2.com; ,
>
>"name":"admin",
>
>"family_name":"admin",
>
>"preferred_username":"admin",
>
>"given_name":"admin",
>
>"profile":"https://wso2.com; ,
>
>"country":"Sri Lanka"
>
> }
>
>
>
> Thanks & Regards
>
> Monika Sharma
>
>
>
>
>
>
>
>
>
> --
>
> Regards,
>
>
>
> *Darshana Gunawardana*
>
> Technical Lead
>
> WSO2 Inc.; http://wso2.com
> * E-mail: **darsh...@wso2.com* 
> * Mobile: +94718566859 <+94%2071%20856%206859>*
> Lean . Enterprise . Middleware
>
>
>
> --
> Regards,
>
>
> 

[Dev] Fwd: Query Regarding the JIRA BUG- IDEBTITY-4250

[Darshana Gunawardana]

Hi Monika,

Seems like you haven't subscribed to the dev mailing list properly.. So the
mails you sent to dev getting on hold.. For the moment, i have fwd the mail
to the dev mailing list on your behalf..

@Sathya: Can you check on this please..

Thanks,


-- Forwarded message --
From: Monika Sharma 
Date: Tue, Feb 20, 2018 at 8:29 AM
Subject: RE: Query Regarding the JIRA BUG- IDEBTITY-4250
To: Darshana Gunawardana , WSO2 Developers' List <
dev@wso2.org>


Hello sir ,



Thank you so much for giving your valuable time. I have tried by adding
requested claims in the SP.

I have added the following request claims in the SP :



1.   http://wso2.org/claims/userid

2.   http://wso2.org/claims/created

3.   http://wso2.org/claims/country

4.   http://wso2.org/claims/displayName

5.   http://wso2.org/claims/emailaddres

6.   http://wso2.org/claims/givenName

7.   http://wso2.org/claims/groups



And subject claim URI is:

1.   http://wso2.org/claims/emailaddres



Now response is as below:



{

"sub”: admin",

"give_name" : "admin",

  "email" : "ad...@wso2.com"

}



Only few information is displayed. Please let me know is it expected result
?



Thanks & Regards

Monika Sharma





*From:* Darshana Gunawardana [mailto:darsh...@wso2.com]
*Sent:* Saturday, February 17, 2018 10:13 PM
*To:* Monika Sharma; WSO2 Developers' List
*Subject:* Re: Query Regarding the JIRA BUG- IDEBTITY-4250



Hi Monika,



Have you added requested claims in the SP claim configurations section? If
you haven't added any requested claims, returning only the subject from the
userinfo endpoint is expected..



Try adding requested claims in the SP.



Regards,



On Fri, Feb 16, 2018 at 3:29 PM, Monika Sharma 
wrote:

Hello sir,



I have a query regarding the https://wso2.org/jira/browse/IDENTITY-4250  bug
of wso2 identity server. It has been fixed in 5.3.0 Beta version of wso2
identity server. But I am facing the same issue in the 5.3.0 release
version of wso2 identity server and also verified in the 5.4.0 release
version, problem is remains in both version. Please check this issue. I
have followed the below steps to reproduce this issue:

Steps :

1.   Register a SP for playground app
Callback URL - http://localhost:8080/playground2/oauth2client
Allowed Grant Types = Code

2.   Visit the URL http://localhost:8080/playground2/oauth2.jsp
and enter the below details
and submit
Authorization Grant Type : Authorization Code
Client ID : (the client id received at the application registration)
Scope : openid
Callback URL : http://localhost:8080/playground2/oauth2client
Authorize Endpoint : https://localhost:9443/oauth2/authorize

3.   Enter user name and password of the admin and click on login

4.   Enter callback url and other info

5.   Enter the user info endpoint and click on get user info
https://localhost:9443/oauth2/userinfo?schema=openid

I have follow this link to register app https://docs.wso2.com/display/
IS530/Basic+Client+Profile+with+Playground
 and
try to access the user information through the curl command using a valid
access token



Issue: Only 'subject' field is returned when userinfo is requested by curl
command using a valid access token



e.g  curl -k -H "Authorization: Bearer YOUR_ACCESS_TOKEN" https://
localhost:9443/oauth2/userinfo?schema=openid



The following response is displayed:

{"sub":"admin”}



But Expected response should be displayed as below

{

   "sub":"admin",

   "email":"ad...@wso2.com",

   "website":"https://wso2.com; ,

   "name":"admin",

   "family_name":"admin",

   "preferred_username":"admin",

   "given_name":"admin",

   "profile":"https://wso2.com; ,

   "country":"Sri Lanka"

}



Thanks & Regards

Monika Sharma









-- 

Regards,



*Darshana Gunawardana*

Technical Lead

WSO2 Inc.; http://wso2.com
* E-mail: **darsh...@wso2.com* 
* Mobile: +94718566859 <+94%2071%20856%206859>*
Lean . Enterprise . Middleware



-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[SajithAR Ariyarathna]

On Tue, Feb 20, 2018 at 10:18 AM, Nisala Nanayakkara 
wrote:

> Hi Sajith,
>
> We need to document this (putting React as an external dependency and
>> using global.React). Is there any docs ATM?
>>
>
> No. We do not add this to document yet. We need to improve the documents
> related "Creating Custom Widgets"[1] with this change.
>
> [1] - https://docs.wso2.com/display/SP400/Creating+Custom+Widgets
>
Let's add this to [1]

>
>
> Thanks,
> Nisala
>
> On Tue, Feb 20, 2018 at 10:14 AM, SajithAR Ariyarathna 
> wrote:
>
>>
>>
>> On Tue, Feb 20, 2018 at 9:47 AM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi Sajith,
>>>
>>> No. I think what we are going to do here is to refer the 'React' which
>>> is initialized by the dashboard parent app from the widget level. So
>>> setting the React in global context(global.React = React) should be
>>> done in the Dashboard parent app.
>>>
>> +1, even better
>>
>>
>>> So that we can refer it from widgets by using 'externals' in the webpack
>>> config.
>>>
>> We need to document this (putting React as an external dependency and
>> using global.React). Is there any docs ATM?
>>
>>
>>> Thanks,
>>> Nisala
>>>
>>> On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna >> > wrote:
>>>
 Hi Nisala,

 global.React = React
>
 Can we do above in the parent Widget (https://www.npmjs.com/package
 /@wso2-dashboards/widget)? So that the some widget author doesn't need
 React as a dependency.


 On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara 
 wrote:

> Hi Aruna,
>
> +1 for the approach. We have faced a similar issue in Product SP and
> tested the above-mentioned fix in our local environment. It is working 
> fine.
>
> Thanks,
> Nisala
>
> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath 
> wrote:
>
>> Loading multiple copies of React in the same page creates problems
>> ,
>> such as errors with discriptions like "Element ref was specified as a
>> string (myRefName) but no owner was set. You may have multiple copies of
>> React loaded."
>>
>> In our dashboards, we have widgets that can be added by dragging and
>> dropping. Since it should be possible to add widgets without building the
>> whole app, widgets are bundled separate to the parent app. How ever this
>> means react is bundled with both the widget and the parent app.
>>
>> Adding react as a peerDep doesn't resolve this, as peerDeps only
>> makes sense if we add the widget as a dependency of the parent app and
>> build the parent app only.
>>
>> To resolve this something we can do is to export React to the global
>> scope and allow widgets to use this global reference to React. So we 
>> don't
>> have to bundle React with widgets.
>>
>> To put React into global context in the parent dashboard app we can
>> do,
>>
>> import React from 'react'
>> global.React = React
>>
>> in the widget to use this global React ref instead of bundling use
>> webpack externals .
>>
>> webpack config should be,
>>
>> externals: {
>>   react: 'React'
>> }
>>
>> Instead of the variable name 'React' we can even use some other name
>> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>>
>> --
>> Aruna Herath
>> Senior Software Engineer | WSO2
>> Mobile: 0711 051 799 | 0774 569 555
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Sajith Janaprasad Ariyarathna
 Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
 

>>>
>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile | +94 717600022
>>> WSO2 Inc | http://wso2.com/
>>>
>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>> 
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>



-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

___
Dev mailing list
Dev@wso2.org

Re: [Dev] Avoid loading multiple copies of React

[Nisala Nanayakkara]

Hi Sajith,

We need to document this (putting React as an external dependency and using
> global.React). Is there any docs ATM?
>

No. We do not add this to document yet. We need to improve the documents
related "Creating Custom Widgets"[1] with this change.

[1] - https://docs.wso2.com/display/SP400/Creating+Custom+Widgets

Thanks,
Nisala

On Tue, Feb 20, 2018 at 10:14 AM, SajithAR Ariyarathna 
wrote:

>
>
> On Tue, Feb 20, 2018 at 9:47 AM, Nisala Nanayakkara 
> wrote:
>
>> Hi Sajith,
>>
>> No. I think what we are going to do here is to refer the 'React' which is
>> initialized by the dashboard parent app from the widget level. So setting
>> the React in global context(global.React = React) should be done in the
>> Dashboard parent app.
>>
> +1, even better
>
>
>> So that we can refer it from widgets by using 'externals' in the webpack
>> config.
>>
> We need to document this (putting React as an external dependency and
> using global.React). Is there any docs ATM?
>
>
>> Thanks,
>> Nisala
>>
>> On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna 
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> global.React = React

>>> Can we do above in the parent Widget (https://www.npmjs.com/package
>>> /@wso2-dashboards/widget)? So that the some widget author doesn't need
>>> React as a dependency.
>>>
>>>
>>> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi Aruna,

 +1 for the approach. We have faced a similar issue in Product SP and
 tested the above-mentioned fix in our local environment. It is working 
 fine.

 Thanks,
 Nisala

 On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:

> Loading multiple copies of React in the same page creates problems
> ,
> such as errors with discriptions like "Element ref was specified as a
> string (myRefName) but no owner was set. You may have multiple copies of
> React loaded."
>
> In our dashboards, we have widgets that can be added by dragging and
> dropping. Since it should be possible to add widgets without building the
> whole app, widgets are bundled separate to the parent app. How ever this
> means react is bundled with both the widget and the parent app.
>
> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
> sense if we add the widget as a dependency of the parent app and build the
> parent app only.
>
> To resolve this something we can do is to export React to the global
> scope and allow widgets to use this global reference to React. So we don't
> have to bundle React with widgets.
>
> To put React into global context in the parent dashboard app we can do,
>
> import React from 'react'
> global.React = React
>
> in the widget to use this global React ref instead of bundling use
> webpack externals .
>
> webpack config should be,
>
> externals: {
>   react: 'React'
> }
>
> Instead of the variable name 'React' we can even use some other name
> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>
> --
> Aruna Herath
> Senior Software Engineer | WSO2
> Mobile: 0711 051 799 | 0774 569 555
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Nisala Niroshana Nanayakkara,*
 Software Engineer
 Mobile | +94 717600022
 WSO2 Inc | http://wso2.com/

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


>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>> 
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile | +94 717600022
>> WSO2 Inc | http://wso2.com/
>>
>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[SajithAR Ariyarathna]

On Tue, Feb 20, 2018 at 9:47 AM, Nisala Nanayakkara  wrote:

> Hi Sajith,
>
> No. I think what we are going to do here is to refer the 'React' which is
> initialized by the dashboard parent app from the widget level. So setting
> the React in global context(global.React = React) should be done in the
> Dashboard parent app.
>
+1, even better


> So that we can refer it from widgets by using 'externals' in the webpack
> config.
>
We need to document this (putting React as an external dependency and using
global.React). Is there any docs ATM?


> Thanks,
> Nisala
>
> On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna 
> wrote:
>
>> Hi Nisala,
>>
>> global.React = React
>>>
>> Can we do above in the parent Widget (https://www.npmjs.com/package
>> /@wso2-dashboards/widget)? So that the some widget author doesn't need
>> React as a dependency.
>>
>>
>> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi Aruna,
>>>
>>> +1 for the approach. We have faced a similar issue in Product SP and
>>> tested the above-mentioned fix in our local environment. It is working fine.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:
>>>
 Loading multiple copies of React in the same page creates problems
 ,
 such as errors with discriptions like "Element ref was specified as a
 string (myRefName) but no owner was set. You may have multiple copies of
 React loaded."

 In our dashboards, we have widgets that can be added by dragging and
 dropping. Since it should be possible to add widgets without building the
 whole app, widgets are bundled separate to the parent app. How ever this
 means react is bundled with both the widget and the parent app.

 Adding react as a peerDep doesn't resolve this, as peerDeps only makes
 sense if we add the widget as a dependency of the parent app and build the
 parent app only.

 To resolve this something we can do is to export React to the global
 scope and allow widgets to use this global reference to React. So we don't
 have to bundle React with widgets.

 To put React into global context in the parent dashboard app we can do,

 import React from 'react'
 global.React = React

 in the widget to use this global React ref instead of bundling use
 webpack externals .

 webpack config should be,

 externals: {
   react: 'React'
 }

 Instead of the variable name 'React' we can even use some other name
 like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.

 --
 Aruna Herath
 Senior Software Engineer | WSO2
 Mobile: 0711 051 799 | 0774 569 555

 

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


>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile | +94 717600022
>>> WSO2 Inc | http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>> 
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>



-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] Avoid loading multiple copies of React

[Nisala Nanayakkara]

Hi Sajith,

No. I think what we are going to do here is to refer the 'React' which is
initialized by the dashboard parent app from the widget level. So setting
the React in global context(global.React = React) should be done in the
Dashboard parent app. So that we can refer it from widgets by using
'externals' in the webpack config.

Thanks,
Nisala

On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna 
wrote:

> Hi Nisala,
>
> global.React = React
>>
> Can we do above in the parent Widget (https://www.npmjs.com/
> package/@wso2-dashboards/widget)? So that the some widget author doesn't
> need React as a dependency.
>
>
> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi Aruna,
>>
>> +1 for the approach. We have faced a similar issue in Product SP and
>> tested the above-mentioned fix in our local environment. It is working fine.
>>
>> Thanks,
>> Nisala
>>
>> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:
>>
>>> Loading multiple copies of React in the same page creates problems
>>> ,
>>> such as errors with discriptions like "Element ref was specified as a
>>> string (myRefName) but no owner was set. You may have multiple copies of
>>> React loaded."
>>>
>>> In our dashboards, we have widgets that can be added by dragging and
>>> dropping. Since it should be possible to add widgets without building the
>>> whole app, widgets are bundled separate to the parent app. How ever this
>>> means react is bundled with both the widget and the parent app.
>>>
>>> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
>>> sense if we add the widget as a dependency of the parent app and build the
>>> parent app only.
>>>
>>> To resolve this something we can do is to export React to the global
>>> scope and allow widgets to use this global reference to React. So we don't
>>> have to bundle React with widgets.
>>>
>>> To put React into global context in the parent dashboard app we can do,
>>>
>>> import React from 'react'
>>> global.React = React
>>>
>>> in the widget to use this global React ref instead of bundling use
>>> webpack externals .
>>>
>>> webpack config should be,
>>>
>>> externals: {
>>>   react: 'React'
>>> }
>>>
>>> Instead of the variable name 'React' we can even use some other name
>>> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>>>
>>> --
>>> Aruna Herath
>>> Senior Software Engineer | WSO2
>>> Mobile: 0711 051 799 | 0774 569 555
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile | +94 717600022
>> WSO2 Inc | http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[SajithAR Ariyarathna]

Hi Nisala,

global.React = React
>
Can we do above in the parent Widget (
https://www.npmjs.com/package/@wso2-dashboards/widget)? So that the some
widget author doesn't need React as a dependency.


On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara  wrote:

> Hi Aruna,
>
> +1 for the approach. We have faced a similar issue in Product SP and
> tested the above-mentioned fix in our local environment. It is working fine.
>
> Thanks,
> Nisala
>
> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:
>
>> Loading multiple copies of React in the same page creates problems
>> ,
>> such as errors with discriptions like "Element ref was specified as a
>> string (myRefName) but no owner was set. You may have multiple copies of
>> React loaded."
>>
>> In our dashboards, we have widgets that can be added by dragging and
>> dropping. Since it should be possible to add widgets without building the
>> whole app, widgets are bundled separate to the parent app. How ever this
>> means react is bundled with both the widget and the parent app.
>>
>> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
>> sense if we add the widget as a dependency of the parent app and build the
>> parent app only.
>>
>> To resolve this something we can do is to export React to the global
>> scope and allow widgets to use this global reference to React. So we don't
>> have to bundle React with widgets.
>>
>> To put React into global context in the parent dashboard app we can do,
>>
>> import React from 'react'
>> global.React = React
>>
>> in the widget to use this global React ref instead of bundling use
>> webpack externals .
>>
>> webpack config should be,
>>
>> externals: {
>>   react: 'React'
>> }
>>
>> Instead of the variable name 'React' we can even use some other name like
>> 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>>
>> --
>> Aruna Herath
>> Senior Software Engineer | WSO2
>> Mobile: 0711 051 799 | 0774 569 555
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] [APIM] Error occurred while connecting to back end

[Lahiru Madushanka]

Hi all,

Got the same issue for MB 3.2.0 when running integration tests.

Workaround :-
replace jks files inside test suit -> resources -> keystore.products folder
from jks files taken from a wum updated MB 3.2.0 pack.

Thanks,
Lahiru

On Wed, Dec 13, 2017 at 9:10 AM, Viduranga Gunarathne 
wrote:

> Hi,
>
> Please find the link below
>
> https://stackoverflow.com/questions/23322676/javax-net-
> ssl-sslhandshakeexception-sun-security-validator-validatorexception
>
> Thanks,
> Viduranga
>
> On Tue, Dec 12, 2017 at 9:35 PM, Senuwan Withana  wrote:
>
>> Thank Guys, I will look into it.
>>
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> On Tue, Dec 12, 2017 at 7:23 PM, Godwin Shrimal  wrote:
>>
>>> Hi Senuwan,
>>>
>>> Check the validity period of the certificate of the ESB. Maybe it's
>>> expired.
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana 
>>> wrote:
>>>
 Hi Abimaran,

 Well, I did not generate any certificate. What I did was, tried to
 create an API using WSO2 API Manager, Publisher. When I was adding
 Production Endpoint that mentioned error was popping up.

 Thanks.
 *Senuwan Withana*
 Software Engineer - Support Team | WSO2

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



 On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan  wrote:

> Hi Senuwan,
>
> By checking your exception, it says, your certificate is expired. You
> have to generate a new certificate.
>
> Caused by: java.security.cert.CertificateExpiredException: NotAfter:
> Mon Jun 19 14:43:07 IST 2017
>
> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana 
> wrote:
>
>> Hi Team,
>>
>> I got below error when I'm trying to connect my ESB proxy into the
>> API Manager.  Any suggestion to solve this error?
>>
>>
>> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error
>> occurred while connecting to backend : https://localhost:8243/service
>> s/EmailSender, reason : sun.security.validator.ValidatorException:
>> PKIX path validation failed: 
>> java.security.cert.CertPathValidatorException:
>> timestamp check failed
>> javax.net.ssl.SSLHandshakeException: 
>> sun.security.validator.ValidatorException:
>> PKIX path validation failed: 
>> java.security.cert.CertPathValidatorException:
>> timestamp check failed
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
>> ndshaker.java:1514)
>> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
>> haker.java:216)
>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
>> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
>> cketImpl.java:1375)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>> java:1403)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>> java:1387)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:533)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:401)
>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
>> enConnection(DefaultClientConnectionOperator.java:178)
>> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
>> anagedClientConnectionImpl.java:304)
>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>> t(DefaultRequestDirector.java:610)
>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>> efaultRequestDirector.java:445)
>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>> tractHttpClient.java:863)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:106)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:57)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
>> dHttpHEADRequest(APIProviderHostObject.java:4781)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
>> unction_isURLValid(APIProviderHostObject.java:4173)

Re: [Dev] Inbound Endpoint | Polling FileURI only daily at Specified Time |WSO2ESB

[Shakila Sasikaran]

Hi,

If the file name is known, you can achieve this requirement in another way
with a scheduled task and read method [2] of file connector [3]. For that,
you can write a proxy service or sequence with the read method of the file
connector with all the required parameters then point this proxy service or
sequence in the scheduled task configuration and schedule it to 9 AM every
day. Please find the cron definition at [4].

[1] https://docs.wso2.com/display/ESB500/Adding+and+Scheduling+Tasks
[2]
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+the+File+Connector#WorkingwiththeFileConnector-read
[3]
https://store.wso2.com/store/assets/esbconnector/details/5d6de1a4-1fa7-434e-863f-95c8533d3df2
[4]
http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger

Thanks

On Mon, Feb 19, 2018 at 4:45 PM, Nirthika Rajendran 
wrote:

> Hi Vivek,
>
> Unfortunately, we do not have this feature currently. But we will consider
> this as an improvement to our product in future.
> I have created an issue to track this improvement [1]
>
> Further, it will be better if you could also copy dev@wso2.org next time
> on your query. So you will get quicker responses from a larger developer
> community
>
> [1] https://github.com/wso2/product-ei/issues/1870
>
>
> Regards,
> *Nirthika Rajendran*
> *Associate Software Engineer*
> WSO2 Inc : http://wso2.org
> Mobile   : +94 77 719 8368 <+94%2077%20719%208368>
> LinkedIn: https://www.linkedin.com/in/nirthika/
> Blog  :
> *http://nirthika-tech-stuff.blogspot.com/
> *
>
> On Mon, Feb 19, 2018 at 3:17 PM, Vivek Kumar  wrote:
>
>> Hi Nirthika,
>>
>> I am using inbound endpoint to process files at regular interval.
>>
>>
>>
>> I want to poll FileURI in Inbound Endpoint only at specified time.So
>> interval parameter provided *Inbound Endpoint* is not serving my purpose.
>>
>>
>>
>> Is there any other parameter using which we can set polling time in cron
>> style(like process files from  input location only at 9.00AM daily)?
>>
>> If not how can we achieve this in WSO2ESB.
>>
>>
>>
>> *Vivek Kumar*
>>
>> *Associate System Analyst*
>>
>> *Office:  *+91-120-4737401 <+91%20120%20473%207401>
>>
>> *Mobile*: +91 8588897434 <+91%2085888%2097434>
>>
>> *Email*:vivku...@salmon.com 
>>
>>
>>
>>
>>
>> Information contained in this e-mail and any attachments is confidential
>> and intended for the use of the addressee only. Dissemination,
>> distribution, copying or use of this communication without prior permission
>> of the addressee is strictly prohibited. If you have received this
>> transmission in error, please advise the originator by reply e-mail and
>> delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
>> 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.
>>
>>
>>
>>
>> Information contained in this e-mail and any attachments is confidential
>> and intended for the use of the addressee only. Dissemination,
>> distribution, copying or use of this communication without prior permission
>> of the addressee is strictly prohibited. If you have received this
>> transmission in error, please advise the originator by reply e-mail and
>> delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
>> 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Shakila Sasikaran
Software Engineer
Mobile :+94 (0) 77 526 6848
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Return to Dashboard after trying out Forgot UserName/Password (IS-5.4.1)

[Godwin Shrimal]

Created issue [1] to track this.

[1] https://github.com/wso2/product-is/issues/2483

Thanks
Godwin

On Thu, Feb 15, 2018 at 12:23 PM, Godwin Shrimal  wrote:

> Hi IAM Team,
>
> Please find the steps to create this issue.
>
> 1. Configure travelocity application with identity server (Service
> providers etc.)
> 2. Click login button in travelocity application
> 3. Click on Forgot Password/Username
> 4. Click cancel button of Forgot password/Username screen
> 5. Enter valid user name and Password and signin
> 6. It is redirecting to Identity Server Dashboard
>
> Ideally it should return to correct service provider which initiated the
> login request. As per the SAML tracer, once we click on cancel button in
> Forget Password/Username, it sends a SAML request with issuer
> "wso2.my.dashboard", So after that its proceeding as Dashboard issuer.
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

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

[Dev] [IS] Not allowing to add Roles for CarbonRemoteUserStoreManger

[Godwin Shrimal]

Hi IAM Team,

I have added user store as CarbonRemoteUserStoreManger. It shows
Roles/Users and it is allowing to add users to remote Identity Server
instance, But user store domain not listing when we trying to add roles.
Please see the screnshot below.

[image: Inline image 1]

Thanks
Godwin
-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

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

Re: [Dev] Inbound Endpoint | Polling FileURI only daily at Specified Time |WSO2ESB

[Nirthika Rajendran]

Hi Vivek,

Unfortunately, we do not have this feature currently. But we will consider
this as an improvement to our product in future.
I have created an issue to track this improvement [1]

Further, it will be better if you could also copy dev@wso2.org next time on
your query. So you will get quicker responses from a larger developer
community

[1] https://github.com/wso2/product-ei/issues/1870


Regards,
*Nirthika Rajendran*
*Associate Software Engineer*
WSO2 Inc : http://wso2.org
Mobile   : +94 77 719 8368
LinkedIn: https://www.linkedin.com/in/nirthika/
Blog  :
*http://nirthika-tech-stuff.blogspot.com/
*

On Mon, Feb 19, 2018 at 3:17 PM, Vivek Kumar  wrote:

> Hi Nirthika,
>
> I am using inbound endpoint to process files at regular interval.
>
>
>
> I want to poll FileURI in Inbound Endpoint only at specified time.So
> interval parameter provided *Inbound Endpoint* is not serving my purpose.
>
>
>
> Is there any other parameter using which we can set polling time in cron
> style(like process files from  input location only at 9.00AM daily)?
>
> If not how can we achieve this in WSO2ESB.
>
>
>
> *Vivek Kumar*
>
> *Associate System Analyst*
>
> *Office:  *+91-120-4737401 <+91%20120%20473%207401>
>
> *Mobile*: +91 8588897434 <+91%2085888%2097434>
>
> *Email*:vivku...@salmon.com 
>
>
>
>
>
> Information contained in this e-mail and any attachments is confidential
> and intended for the use of the addressee only. Dissemination,
> distribution, copying or use of this communication without prior permission
> of the addressee is strictly prohibited. If you have received this
> transmission in error, please advise the originator by reply e-mail and
> delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
> 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.
>
>
>
>
> Information contained in this e-mail and any attachments is confidential
> and intended for the use of the addressee only. Dissemination,
> distribution, copying or use of this communication without prior permission
> of the addressee is strictly prohibited. If you have received this
> transmission in error, please advise the originator by reply e-mail and
> delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
> 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XACML PAP UI

[Godwin Shrimal]

Hi Dakshika,

Please see my answers inline.


IMO that won't fix the issue, Check scenarios like,
>
> 1. If the user wants to get a copy of the policy and rename and save as
> another. (Our documentation also guide this method). If we disable it how
> they understand they can re-edit it.
>
> 2. Publish to PDP has multiple options,( Add, Update, Order, Enable,
> Disable, Delete Policy etc). If we make it disable they can't do further
> actions without editing it.
>

I aggree with you, since we have multiple options we simply cannot disable
Publish option.



> So IMO to avoid this we can have below-listed journey or wizard.
>
> By default, we won't show any policies under policy available list. We can
> show main action button saying "Add New Entitlement Policy"
>
> Step 01: We can have a section called policy templates which includes the
> sample set
>
> Step 02: user can select any by looking at the name and description
>
> Step 03: We will ask for the value of policyID and description including
> the actions with next or create.
>
> Step 04: we will load the template on the editor with given
> policyID filled.
>

PAP is where we list all the Policies and which is correct to show all
policies there IMO. So I am -1 to not showing any policies under list. and
if we are not showing here, where do we show policies which are not
published ?


Thanks
Godwin



> WDYT?
>
> Regards,
>
>
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Associate Technical Lead
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Mon, Feb 19, 2018 at 6:50 AM, Pulasthi Mahawithana 
> wrote:
>
>> +1 for the suggestion.
>>
>> For that, shall we disable the publish link for the already published
>> policies and order the list to bring them to the top? However we'll need
>> to re-enable the publish link if the policy is modified after publishing.
>>
>> On Sun, Feb 18, 2018 at 6:21 AM, Gayan Gunawardana 
>> wrote:
>>
>>> Hi All,
>>>
>>> In current XACML policy administration UI, it is bit hard to
>>> differentiate XACML policies which are already published to PDP.
>>> Can we make better user experience ?
>>>
>>>
>>> ​
>>>
>>>
>>> --
>>> Gayan Gunawardana
>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
>>> Email: ga...@wso2.com
>>> Mobile: +94 (71) 8020933
>>>
>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Associate Technical Lead
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: https://medium.com/@pulasthi7/
>>
>> 
>>
>> ___
>> 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
>
>


-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

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

Re: [Dev] Error in visualizing an execution plan

[Pamoda Wimalasiri]

Hi Mohan,

I added an issue to the w so2
/carbon-event-processing
 repository.

Thanks,
Pamoda

On Fri, Feb 16, 2018 at 8:56 AM, Pamoda Wimalasiri  wrote:

> On Fri, Feb 16, 2018 at 4:49 AM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> Hi Pamoda,
>>
>> I believe this will not affect the event processing cases and only
>> happens when viewing the execution plan. Can you please report a github
>> issue for this?
>>
> Yes. It does not affect the process.
>
>
>>
>> Thanks,
>> Mohan
>>
>>
>> On Thu, Feb 8, 2018 at 11:16 AM, Pamoda Wimalasiri 
>> wrote:
>>
>>> Hi,
>>>
>>> The following error occurred when visualizing an execution plan with a
>>> customized javascript function.
>>>
>>> [2018-02-08 11:11:53,907] ERROR {org.wso2.carbon.event.process
>>> or.ui.executionPlan.flow.ExecutionPlanFlow} -  Error in visualizing
>>> execution plan '/* Enter a unique ExecutionPlan */
>>> @Plan:name('RiskScoreCalculator-AllowedIpRange-ip2-realtime1')
>>>
>>> /* Enter a unique description for ExecutionPlan */
>>> @Plan:description('Detect logins outside the allowed ip range')
>>>
>>> define function ipToLong[JavaScript] return double {
>>> var octetsOfIp = data[0].split(".");
>>> var ipAddressAsLong = octetsOfIp[0]* 256 * 256 * 256
>>> + octetsOfIp[1]* 256 * 256
>>> + octetsOfIp[2] * 256
>>> + octetsOfIp[3] * 1;
>>> return ipAddressAsLong;
>>> };
>>>
>>> /* define streams/tables and write queries here ... */
>>>
>>> @Import('org.wso2.is.analytics.stream.ProcessedOverallAuthen
>>> tication:1.0.0')
>>> define stream ProcessedOverallAuthentication (meta_tenantId int,
>>> contextId string, eventId string, eventType string, authenticationSuccess
>>> bool, username string, localUsername string, userStoreDomain string,
>>> tenantDomain string, remoteIp string, region string, inboundAuthType
>>> string, serviceProvider string, rememberMeEnabled bool, forceAuthEnabled
>>> bool, passiveAuthEnabled bool, rolesCommaSeparated string,
>>> authenticationStep string, identityProvider string, authStepSuccess bool,
>>> stepAuthenticator string, isFirstLogin bool, identityProviderType string,
>>> _timestamp long);
>>>
>>> @Export('org.wso2.is.analytics.stream.SuspiciousLoginAttempt:1.0.0')
>>> define stream SuspiciousLoginAttempt (meta_tenantId int, username
>>> string, userStoreDomain string, tenantDomain string, remoteIp string,
>>> region string, _timestamp long, message string);
>>>
>>> from ProcessedOverallAuthentication[(authStepSuccess == true) AND
>>> (eventType =='step') AND ipToLong(remoteIp) < ipToLong("123.56.7.8") OR
>>> ipToLong(remoteIp) > ipToLong("123.9.9.1")]
>>> select meta_tenantId, username, userStoreDomain, tenantDomain, remoteIp,
>>> region, _timestamp, "WARNING : IP is not in the allowed range" as message
>>> insert into SuspiciousLoginAttempt;
>>> ', null
>>> java.lang.NullPointerException
>>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.Extrac
>>> tJsonValueImpl.setTriggerJsonValue(ExtractJsonValueImpl.java:202)
>>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.Extrac
>>> tJsonValueImpl.setJsonValues(ExtractJsonValueImpl.java:123)
>>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.Execut
>>> ionPlanFlow.getExecutionPlanFlow(ExecutionPlanFlow.java:37)
>>> at org.apache.jsp.eventprocessor.execution_005fplan_005fdetails
>>> _jsp._jspService(execution_005fplan_005fdetails_jsp.java:207)
>>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>>> etWrapper.java:439)
>>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>>> et.java:395)
>>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>>> rvice(ContextPathServletAdaptor.java:37)
>>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>>> n.service(ServletRegistration.java:61)
>>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>>> ssAlias(ProxyServlet.java:128)
>>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>>> ce(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>>> (DelegationServlet.java:68)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>>> lter(ApplicationFilterChain.java:303)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>>> licationFilterChain.java:208)
>>> at 

Re: [Dev] MTOM Attachment to secured Proxy

[Roberto Sanz]

i think i'd found the solution.!!

The reason for that error is that the WSS4J library needs XmlSec libraries
starting from the version 1.5.6 but the SOAPUI is exported with the version
1.4.5.

This issue can be resolved by replacing the following jar 'xmlsec-1.4.5.jar'
with this one 'xmlsec-1.5.6.jar'.

I'm hoping that the SOAPUI team fixes this issue in new releases.

Regards,
R.



--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev