Re: [Dev] Unable to execute WSO2 EI 6.1.1 installer in Ubuntu 17.10

2018-02-18 Thread Miraj Abeysekara 
Hi Niranjan,

Missing libpng shared library is a known issue in latest Ubuntu releases.
We will fix this in a future release.

Thank you and regards,
Miraj

On Mon, Feb 19, 2018 at 4:23 AM, Niranjan Karunanandham <
niranjan.k...@gmail.com> wrote:

> Hi WUM Team,
>
> When I tried to execute the installer (to download the product) in Ubuntu
> 17.10, I got the below issue:
>
> ./wso2ei-6.1.1-downloader-linux-x64.run: error while loading shared 
> libraries: libpng12.so.0: cannot open shared object file: No such file or 
> directory
>
>
> I have created a JIRA[1] for this and a workaround. In addition when the
> installer is running, in the taskbar it displays a generic icon. It will be
> good to have an installer specific icon [2]
>
> [1] - https://wso2.org/jira/browse/WUM-11
> [2] - https://wso2.org/jira/browse/WUM-12
>
> Regards,
> Nira
>
> --
> *Niranjan Karunanandham*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Miraj Abeysekara*
Software Engineer
WSO2, Inc.

Mobile : +94775690822
Twitter : https://twitter.com/miragecreator

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

Re: [Dev] Unable to execute WSO2 EI 6.1.1 installer in Ubuntu 17.10

2018-02-18 Thread Jayanga Dissanayake 
Hi Niranjan,

Thanks for reporting this we will look into this.

Thanks,
*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259


On Mon, Feb 19, 2018 at 4:23 AM, Niranjan Karunanandham <
niranjan.k...@gmail.com> wrote:

> Hi WUM Team,
>
> When I tried to execute the installer (to download the product) in Ubuntu
> 17.10, I got the below issue:
>
> ./wso2ei-6.1.1-downloader-linux-x64.run: error while loading shared 
> libraries: libpng12.so.0: cannot open shared object file: No such file or 
> directory
>
>
> I have created a JIRA[1] for this and a workaround. In addition when the
> installer is running, in the taskbar it displays a generic icon. It will be
> good to have an installer specific icon [2]
>
> [1] - https://wso2.org/jira/browse/WUM-11
> [2] - https://wso2.org/jira/browse/WUM-12
>
> Regards,
> Nira
>
> --
> *Niranjan Karunanandham*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XACML PAP UI

2018-02-18 Thread Dakshika Jayathilaka 
Hi Pulasthi,

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.

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.

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

Re: [Dev] XACML PAP UI

2018-02-18 Thread Pulasthi Mahawithana 
+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
Blog: https://medium.com/@pulasthi7/


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

[Dev] Unable to execute WSO2 EI 6.1.1 installer in Ubuntu 17.10

2018-02-18 Thread Niranjan Karunanandham 
Hi WUM Team,

When I tried to execute the installer (to download the product) in Ubuntu
17.10, I got the below issue:

./wso2ei-6.1.1-downloader-linux-x64.run: error while loading shared
libraries: libpng12.so.0: cannot open shared object file: No such file
or directory


I have created a JIRA[1] for this and a workaround. In addition when the
installer is running, in the taskbar it displays a generic icon. It will be
good to have an installer specific icon [2]

[1] - https://wso2.org/jira/browse/WUM-11
[2] - https://wso2.org/jira/browse/WUM-12

Regards,
Nira

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

Re: [Dev] [IS 5.5.0] Shall we get rid of DB backward compatibility code related to PKCE Support

2018-02-18 Thread Darshana Gunawardana 
Hi Rushmin,

Thanks for bringing this up.. and +1 for the proposal..

PKCE feature added in IS 5.2.0 and IS 5.1.0 to 5.2.0 migration intended to
be done without a schema migration.. That's why the code is written to
handle both cases..

But, we could have get rid of this, from 5.3.0 onwards, since migration to
520-530 mandate db migration hence we could mandate adding these columns as
well..

So, considering the current situation, we can handle adding this column
from the 540-550 migration and get rid from the obsolete code which makes
the OAuth DAOs bulky..

Regards,

On Sun, Feb 18, 2018 at 6:19 PM, Rushmin Fernando  wrote:

> Hi Ruwan,
>
> Sorry if I didn't explain it clearly.
>
> What I meant was ...
>
> The PKCE feature was shipped as an update to IS 5.3.0 initially and it
> had a schema change.
>
> So the code was added in a backward compatible way.
>
> But since 5.5.0 is a minor release we can get rid of the backward
> compatible code since the migration is any way there. (if time permits :-) )
>
> On Sun, Feb 18, 2018 at 6:06 PM, Ruwan Abeykoon  wrote:
>
>> Hi Rushmin,
>> Need clarification, do you mean the table not exist in DB case? DB
>> scripts can be created with migration script.
>>
>> Cheers,
>> Ruwan
>>
>>
>> On Sun, Feb 18, 2018 at 5:12 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> AFAIK this code was introduced to protect backward compatibility while
>>> introducing PKCE support sometime back.
>>>
>>> We still see the following log.
>>>
>>> INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent}
>>> -  PKCE Support enabled.
>>>
>>> Do we still need that code (not only the log but the backward
>>> compatibility code too)?
>>>
>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> mobile : +94775615183
>>>
>>>
>>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Associate Director/Architect**,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,


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

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

Re: [Dev] [IS 5.5.0] Shall we get rid of DB backward compatibility code related to PKCE Support

2018-02-18 Thread Rushmin Fernando 
Hi Ruwan,

Sorry if I didn't explain it clearly.

What I meant was ...

The PKCE feature was shipped as an update to IS 5.3.0 initially and it had
a schema change.

So the code was added in a backward compatible way.

But since 5.5.0 is a minor release we can get rid of the backward
compatible code since the migration is any way there. (if time permits :-) )

On Sun, Feb 18, 2018 at 6:06 PM, Ruwan Abeykoon  wrote:

> Hi Rushmin,
> Need clarification, do you mean the table not exist in DB case? DB scripts
> can be created with migration script.
>
> Cheers,
> Ruwan
>
>
> On Sun, Feb 18, 2018 at 5:12 PM, Rushmin Fernando 
> wrote:
>
>>
>> AFAIK this code was introduced to protect backward compatibility while
>> introducing PKCE support sometime back.
>>
>> We still see the following log.
>>
>> INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent}
>> -  PKCE Support enabled.
>>
>> Do we still need that code (not only the log but the backward
>> compatibility code too)?
>>
>>
>> --
>> *Best Regards*
>>
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> mobile : +94775615183
>>
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
>


-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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

Re: [Dev] [IS 5.5.0] Shall we get rid of DB backward compatibility code related to PKCE Support

2018-02-18 Thread Ruwan Abeykoon 
Hi Rushmin,
Need clarification, do you mean the table not exist in DB case? DB scripts
can be created with migration script.

Cheers,
Ruwan


On Sun, Feb 18, 2018 at 5:12 PM, Rushmin Fernando  wrote:

>
> AFAIK this code was introduced to protect backward compatibility while
> introducing PKCE support sometime back.
>
> We still see the following log.
>
> INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent} -
> PKCE Support enabled.
>
> Do we still need that code (not only the log but the backward
> compatibility code too)?
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>


-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS 5.5.0] Shall we get rid of DB backward compatibility code related to PKCE Support

2018-02-18 Thread Rushmin Fernando 
AFAIK this code was introduced to protect backward compatibility while
introducing PKCE support sometime back.

We still see the following log.

INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent} -
PKCE Support enabled.

Do we still need that code (not only the log but the backward compatibility
code too)?


-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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