Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.

[Samuel Gnaniah]

Ack. Will fix this.

--

*Samuel Gnaniah*
Senior Lead Technical Writer

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

On Tue, Jul 24, 2018 at 10:49 AM, Nirdesha Munasinghe 
wrote:

> Copying the IAM writers...
>
> On Mon, Jul 23, 2018 at 1:02 PM, Ruwan Abeykoon  wrote:
>
>> Hi Farasath,
>> The failing XML file seems semantically identical to the one with
>> namespace.
>> What can be the reason for failure ?
>>
>> Cheers,
>> Ruwan
>>
>> On Mon, Jul 23, 2018 at 12:33 PM Achini Jayasena 
>> wrote:
>>
>>> Hi Farasath and Doc team,
>>>
>>> @ Farasath, I  got the matadata file sample given in the document. [1].
>>> It's working  after add XML name spaces.
>>> And also is there a way to enable the response signing through the
>>> metadata file upload? Is metadata file support for all manual saml
>>> configurations in IS?
>>>
>>> @doc team, Please do the update for metadata configuration file in
>>> document  [1] since the given sample not working without Xml name spaces.
>>>
>>> Please find the updated metadata file attached here with.
>>>
>>> [1] : https://docs.wso2.com/display/IS550/Adding+and+Configuring+a
>>> +Service+Provider#AddingandConfiguringaServiceProvider-Metad
>>> atafileconfiguration
>>>
>>>
>>>
>>> *Thanks & Best Regards!*
>>>
>>> *Achini Jayasena*
>>> *Software Engineer - QA | WSO2*
>>>
>>> Email: achi...@wso2.com
>>> Mobile: +943 882 897
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>> On Fri, Jul 20, 2018 at 8:40 PM, Farasath Ahamed 
>>> wrote:
>>>
 Hi Achini,

 Seems like there is a possible issue with the metadata file you have
 created. (Initially, I thought it was due to a binary character in the
 file, but it doesn't seem to be the case). A similar error has been
 reported in [1]. And the resolution was to fix the 
 with a specific format (With XML namespaces etc.)

 I created a metadata file using https://www.samltool.com
 /sp_metadata.php with the same details(see the attachment) and
 uploaded it to IS 5.5.0 WUM pack and it worked without any issue. To find
 the issue with your metadata file can you explain how you generated the
 metadata file?


 [1] http://codeverge.com/novell.support.access-manager/error
 -importing-saml2-metadata/1980697

 On Fri, Jul 20, 2018 at 4:10 PM, Achini Jayasena 
 wrote:

> Hi all,
>
> Seems this is a bug and I have created a git issue [1]. please find
> the error log from below.
>
> product version. 5.5 latest wum update.
>
> [1] - https://github.com/wso2/product-is/issues/3453
>
> [2018-07-20 15:18:57,194] ERROR 
> {org.wso2.carbon.identity.sp.metadata.saml2.util.Parser}
> -  Error While reading Service Provider metadata xml
> org.xml.sax.SAXParseException: Element type "EntityDescriptor" must be
> followed by either attribute specifications, ">" or "/>".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown
> Source)
> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
> at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.gener
> ateMetadataObjectFromString(Parser.java:252)
> at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.parse
> (Parser.java:199)
> at org.wso2.carbon.identity.sso.saml.admin.SAMLSSOConfigAdmin.u
> ploadRelyingPartyServiceProvider(SAMLSSOConfigAdmin.java:148)
> at org.wso2.carbon.identity.sso.saml.SAMLSSOConfigService.uploa
> dRPServiceProvider(SAMLSSOConfigService.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
> RPCUtil.java:212)
> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
> nessLogic(RPCMessageReceiver.java:117)
> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
> bstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
> essMessage(LocalTransportReceiver.java:170)
> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
> essMessage(LocalTransportReceiver.java:82)
> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at org.apache.axis2.transport.local.LocalTransportSender.invoke

[Dev] Deprecating Mepin Authenticator

[Biruntha Gnaneswaran]

Hi All,

We are planning to deprecate Mepin authenticator[1] from the store[2]. In
our Mepin authenticator, we are using the Mepin simple_api endpoint [3] to
authenticate and retrieve user information. Since this endpoint has been
deprecated recently and giving 502 Bad Gateway error, we are planning to
deprecate.

Please let us know if there are any concerns.

[1] https://docs.wso2.com/display/ISCONNECTORS/MePIN+Authenticator
[2]
https://store.wso2.com/store/assets/isconnector/details/00902cc7-5efc-4b8f-aae7-930e999f8058
[3] https://api.mepin.com/simple_api/

Thanks,
-- 
Biruntha

Software Engineer
WSO2
Email: birun...@wso2.com
LinkedIn: https://lk.linkedin.com/in/biruntha
Mobile : +94773718986
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.

[Nirdesha Munasinghe]

Copying the IAM writers...

On Mon, Jul 23, 2018 at 1:02 PM, Ruwan Abeykoon  wrote:

> Hi Farasath,
> The failing XML file seems semantically identical to the one with
> namespace.
> What can be the reason for failure ?
>
> Cheers,
> Ruwan
>
> On Mon, Jul 23, 2018 at 12:33 PM Achini Jayasena  wrote:
>
>> Hi Farasath and Doc team,
>>
>> @ Farasath, I  got the matadata file sample given in the document. [1].
>> It's working  after add XML name spaces.
>> And also is there a way to enable the response signing through the
>> metadata file upload? Is metadata file support for all manual saml
>> configurations in IS?
>>
>> @doc team, Please do the update for metadata configuration file in
>> document  [1] since the given sample not working without Xml name spaces.
>>
>> Please find the updated metadata file attached here with.
>>
>> [1] : https://docs.wso2.com/display/IS550/Adding+and+Configuring+
>> a+Service+Provider#AddingandConfiguringaServiceProvider-
>> Metadatafileconfiguration
>>
>>
>>
>> *Thanks & Best Regards!*
>>
>> *Achini Jayasena*
>> *Software Engineer - QA | WSO2*
>>
>> Email: achi...@wso2.com
>> Mobile: +943 882 897
>>
>> [image: http://wso2.com/signature] 
>>
>> On Fri, Jul 20, 2018 at 8:40 PM, Farasath Ahamed 
>> wrote:
>>
>>> Hi Achini,
>>>
>>> Seems like there is a possible issue with the metadata file you have
>>> created. (Initially, I thought it was due to a binary character in the
>>> file, but it doesn't seem to be the case). A similar error has been
>>> reported in [1]. And the resolution was to fix the 
>>> with a specific format (With XML namespaces etc.)
>>>
>>> I created a metadata file using https://www.samltool.com/sp_metadata.php
>>> with the same details(see the attachment) and uploaded it to IS 5.5.0 WUM
>>> pack and it worked without any issue. To find the issue with your metadata
>>> file can you explain how you generated the metadata file?
>>>
>>>
>>> [1] http://codeverge.com/novell.support.access-manager/
>>> error-importing-saml2-metadata/1980697
>>>
>>> On Fri, Jul 20, 2018 at 4:10 PM, Achini Jayasena 
>>> wrote:
>>>
 Hi all,

 Seems this is a bug and I have created a git issue [1]. please find the
 error log from below.

 product version. 5.5 latest wum update.

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

 [2018-07-20 15:18:57,194] ERROR 
 {org.wso2.carbon.identity.sp.metadata.saml2.util.Parser}
 -  Error While reading Service Provider metadata xml
 org.xml.sax.SAXParseException: Element type "EntityDescriptor" must be
 followed by either attribute specifications, ">" or "/>".
 at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
 at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
 at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.
 generateMetadataObjectFromString(Parser.java:252)
 at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.
 parse(Parser.java:199)
 at org.wso2.carbon.identity.sso.saml.admin.SAMLSSOConfigAdmin.
 uploadRelyingPartyServiceProvider(SAMLSSOConfigAdmin.java:148)
 at org.wso2.carbon.identity.sso.saml.SAMLSSOConfigService.
 uploadRPServiceProvider(SAMLSSOConfigService.java:71)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 NativeMethodAccessorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.apache.axis2.rpc.receivers.RPCUtil.
 invokeServiceClass(RPCUtil.java:212)
 at org.apache.axis2.rpc.receivers.RPCMessageReceiver.
 invokeBusinessLogic(RPCMessageReceiver.java:117)
 at org.apache.axis2.receivers.AbstractInOutMessageReceiver.
 invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at org.apache.axis2.receivers.AbstractMessageReceiver.receive(
 AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at org.apache.axis2.transport.local.LocalTransportReceiver.
 processMessage(LocalTransportReceiver.java:170)
 at org.apache.axis2.transport.local.LocalTransportReceiver.
 processMessage(LocalTransportReceiver.java:82)
 at org.wso2.carbon.core.transports.local.
 CarbonLocalTransportSender.finalizeSendWithToAddress(
 CarbonLocalTransportSender.java:45)
 at org.apache.axis2.transport.local.LocalTransportSender.
 invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at org.apache.axis2.description.OutInAxisOperationClient.send(
 OutInAxisOperation.java:441)
 at org.apache.axis2.description.OutInAxisOperationClient.
 

Re: [Dev] [IAM] Modifying consent purposes associations

[Darshana Gunawardana]

Hi Omindu,

Could you explain the need of this functionality with the view of the end
user?

Thanks,

On Sun, Jul 22, 2018 at 11:06 PM Omindu Rathnaweera  wrote:

> Hi All,
>
> As per the current implementation, we do not allow to edit or delete
> consent purposes which are associated with a consent receipt. The reason
> behind such a design decision was to preserve the immutability of the
> consent receipt. Meaning, to prevent modifying the existing consent
> receipts which are associated with purposes if a purpose is modified.
>
> However, with the improvements we are introducing with 5.7.0 privacy
> features, Self Signup and JIT functionalities will have a tight dependency
> on purposes and there will be more involvement around configuring purposes.
> The purposes defined for these scenarios cannot be modified once they are
> associated with a consent receipt.
>
> Therefore it would be convenient for the users to have the option to
> modify the existing consent purposes. But doing so should not change the
> existing consent receipts.
>
> In order to achieve this requirement. I see the following
>
> i) We can provide the capability to modify the existing purposes. For this
> we may have to duplicate the purposes when adding receipts and reference
> the duplicated purpose from the receipt.
>
> ii) Without providing the capability to modify the purposes, we can
> maintain a separate association of purposes and Self signup/JIT similar
> to what we are doing for service providers. This way a user can pick what
> purposes should be associated with a certain flow without modifying the
> existing purposes.
>
> Appreciate your thoughts on this.
>
> Regards,
> Omindu.
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>


-- 
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] API Microgateway Ballerina Upgrade to 0.980

[Nuwan Dias]

Let's go through the scenarios on the docs and verify everything. Ex:
changing back-end url and credentials, etc.

On Mon, Jul 23, 2018 at 7:55 AM Sachini De Silva  wrote:

> Tested analytics. Will check rate limiting.
>
> On Mon, Jul 23, 2018 at 6:24 PM, Nuwan Dias  wrote:
>
>> How about Analytics, Rate Limiting?
>>
>> On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva 
>> wrote:
>>
>>> Hi all,
>>>
>>> Adding to the list of tested scenarios,
>>>
>>> 8. Deploy microgateway in kubernetes with a single API and invoke with
>>> JWT token.
>>> 9. Tested same for a group of labeled APIs.
>>>
>>> Thanks,
>>> Sachini
>>>
>>> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Tested 0.980.1 updated microgateway with single API mode for both
 JWT/OAuth token mode in docker and local mode. Didn't noticed any issues
 and its working as expected. If other scenarios also passed i think we can
 go ahead and do release.

 Thanks,
 sanjeewa.

 On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa 
 wrote:

>
>
> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> I think there was an issue with v0.980 and fixed in v0.980.1. Not
>> sure if it will affect MG. Please check that.
>>
> This was a fix related to packerina. However since this is the only
> change included, IMO we can bump the version and do the release.
>
>>
>> Thanks,
>> Bhathiya
>>
>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
>> wrote:
>>
>>> + [dev]
>>>
>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva <
>>> sachi...@wso2.com> wrote:
>>>
 Hi all,

 This is to give an update on how API Microgateway ballerina upgrade
 is going.

 RajithR came up with
 https://github.com/wso2/product-microgateway/pull/202/files which
 contains the syntax changes to support ballerina 0.980.

 I have tested API Microgateway with the above change and listed
 below are the scenarios I tested.

 1. Created gateway distribution for a single API and invoked
 through JWT and Oauth tokens.
 2. Tested the same for labelled APIs
 3. Tested overriding endpoints using system variables.
 4. Microgateway analytics
 6. Deploy microgateway in docker and invoked API using JWT and
 Oauth2.
 7. Deploy a group of labeled APIs in docker. (to verify
 https://github.com/wso2/product-microgateway/issues/199 is fixed)

 Thanks,
 Sachini

 --

 *Sachini De Silva*
 Software Engineer - WSO2

 Email : sachi...@wso2.com
 Mobile : +94714765495


>>>
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax
>> *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


 --
 *Sanjeewa Malalgoda*
 WSO2 Inc.
 Mobile : +94 712933253

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



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


>>>
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Director - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
>

-- 
Nuwan Dias

Director - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729

Re: [Dev] WSO2 module to use Zipkin as tracing tool

[Sinthuja Rajendran]

Hi Jose,

First of all, I would like to Thank you for your contribution, and yes it's
very helpful.

Currently, we are also focusing on providing the distributed tracing for
APIM by OpenTracing  standard, and Praveen (cc'd)
here is working on that. Basically, with that, you are not restricted to
specific tracer and it lets users integrate with any servers that support
open tracing standard such as Zipkin, Jaeger, WSO2 SP, etc without having
tracer specific code.

Also, I would like to highlight as now APIM 2.5.0 is released, the APIM
Microgateway 
has default support to integrate with Zipkin with few steps. And I believe
it'll be very suitable for your microservices architecture.

Thanks,
Sinthuja.

On Mon, Jul 23, 2018 at 4:18 PM JOSE MARIA ALVAREZ FERNANDEZ <
josemaria.alvarezfernan...@elcorteingles.es> wrote:

> Hi,
>
> We have been trying to build a module for WSO2 to work within a
> Microservice environment, and participate in a tracing context (in this
> case with Zipkin B3 Headers ->
> https://github.com/openzipkin/b3-propagation/blob/master/README.md)  and
> the result, although in beta, is here:
>
> https://github.com/jmalvarezf/wso2-zipkin-tracer
>
> We just wanted to know if that could be useful for you. Tracing is a great
> tool for a microservices environment, and in case you want to use WSO2 as
> the Api Manager, we find very important for the gateway to work within that
> context.
>
> The idea was to create an Axis2 module, and a handler, the first one to
> manage all the requests to the gateway, and the second to manage the API
> requests.
>
> Best regards,
>
> Jose Maria.
>
>
>
> ---
>
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información confidencial, siendo para uso exclusivo del
> destinatario, quedando prohibida su divulgación copia o distribución a
> terceros sin la autorización expresa del remitente. Si Vd. ha recibido este
> mensaje erróneamente, se ruega lo notifique al remitente y proceda a su
> borrado.
>
> Gracias por su colaboración.
>
> This message (including any attachments) may contain confidential
> information. It is intended for use by the recipient only. Any
> dissemination, copying or distribution to third parties without the express
> consent of the sender is strictly prohibited. If you have received this
> message in error, please delete it immediately and notify the sender.
>
> Thank you for your collaboration.
>
>
> ---
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Sinthuja Rajendran*
Senior Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Pubudu Gunatilaka]

Hi Sachini,

Before the release, let's fix the issues in [1].

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

Thank you!

On Mon, Jul 23, 2018 at 4:56 PM Sachini De Silva  wrote:

> Tested analytics. Will check rate limiting.
>
> On Mon, Jul 23, 2018 at 6:24 PM, Nuwan Dias  wrote:
>
>> How about Analytics, Rate Limiting?
>>
>> On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva 
>> wrote:
>>
>>> Hi all,
>>>
>>> Adding to the list of tested scenarios,
>>>
>>> 8. Deploy microgateway in kubernetes with a single API and invoke with
>>> JWT token.
>>> 9. Tested same for a group of labeled APIs.
>>>
>>> Thanks,
>>> Sachini
>>>
>>> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Tested 0.980.1 updated microgateway with single API mode for both
 JWT/OAuth token mode in docker and local mode. Didn't noticed any issues
 and its working as expected. If other scenarios also passed i think we can
 go ahead and do release.

 Thanks,
 sanjeewa.

 On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa 
 wrote:

>
>
> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> I think there was an issue with v0.980 and fixed in v0.980.1. Not
>> sure if it will affect MG. Please check that.
>>
> This was a fix related to packerina. However since this is the only
> change included, IMO we can bump the version and do the release.
>
>>
>> Thanks,
>> Bhathiya
>>
>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
>> wrote:
>>
>>> + [dev]
>>>
>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva <
>>> sachi...@wso2.com> wrote:
>>>
 Hi all,

 This is to give an update on how API Microgateway ballerina upgrade
 is going.

 RajithR came up with
 https://github.com/wso2/product-microgateway/pull/202/files which
 contains the syntax changes to support ballerina 0.980.

 I have tested API Microgateway with the above change and listed
 below are the scenarios I tested.

 1. Created gateway distribution for a single API and invoked
 through JWT and Oauth tokens.
 2. Tested the same for labelled APIs
 3. Tested overriding endpoints using system variables.
 4. Microgateway analytics
 6. Deploy microgateway in docker and invoked API using JWT and
 Oauth2.
 7. Deploy a group of labeled APIs in docker. (to verify
 https://github.com/wso2/product-microgateway/issues/199 is fixed)

 Thanks,
 Sachini

 --

 *Sachini De Silva*
 Software Engineer - WSO2

 Email : sachi...@wso2.com
 Mobile : +94714765495


>>>
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax
>> *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


 --
 *Sanjeewa Malalgoda*
 WSO2 Inc.
 Mobile : +94 712933253

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



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


>>>
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Director - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
> ___
> Dev mailing list
> Dev@wso2.org
> 

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Sachini De Silva]

Tested analytics. Will check rate limiting.

On Mon, Jul 23, 2018 at 6:24 PM, Nuwan Dias  wrote:

> How about Analytics, Rate Limiting?
>
> On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva 
> wrote:
>
>> Hi all,
>>
>> Adding to the list of tested scenarios,
>>
>> 8. Deploy microgateway in kubernetes with a single API and invoke with
>> JWT token.
>> 9. Tested same for a group of labeled APIs.
>>
>> Thanks,
>> Sachini
>>
>> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Tested 0.980.1 updated microgateway with single API mode for both
>>> JWT/OAuth token mode in docker and local mode. Didn't noticed any issues
>>> and its working as expected. If other scenarios also passed i think we can
>>> go ahead and do release.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa 
>>> wrote:
>>>


 On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara >>> > wrote:

> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure
> if it will affect MG. Please check that.
>
 This was a fix related to packerina. However since this is the only
 change included, IMO we can bump the version and do the release.

>
> Thanks,
> Bhathiya
>
> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
> wrote:
>
>> + [dev]
>>
>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva > > wrote:
>>
>>> Hi all,
>>>
>>> This is to give an update on how API Microgateway ballerina upgrade
>>> is going.
>>>
>>> RajithR came up with https://github.com/wso2/
>>> product-microgateway/pull/202/files which contains the syntax
>>> changes to support ballerina 0.980.
>>>
>>> I have tested API Microgateway with the above change and listed
>>> below are the scenarios I tested.
>>>
>>> 1. Created gateway distribution for a single API and invoked through
>>> JWT and Oauth tokens.
>>> 2. Tested the same for labelled APIs
>>> 3. Tested overriding endpoints using system variables.
>>> 4. Microgateway analytics
>>> 6. Deploy microgateway in docker and invoked API using JWT and
>>> Oauth2.
>>> 7. Deploy a group of labeled APIs in docker. (to verify
>>> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>>>
>>> Thanks,
>>> Sachini
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>>
>>
>>
>> --
>>
>> *Sachini De Silva*
>> Software Engineer - WSO2
>>
>> Email : sachi...@wso2.com
>> Mobile : +94714765495
>>
>>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax
> *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thanks and Regards,

 Isuru H.
 +94 716 358 048* *


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

>>>
>>>
>>> --
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94 712933253
>>>
>>> blog :http://sanjeewamalalgoda.
>>> blogspot.com/ 
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Sachini De Silva*
>> Software Engineer - WSO2
>>
>> Email : sachi...@wso2.com
>> Mobile : +94714765495
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Nuwan Dias
>
> Director - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

*Sachini De Silva*
Software Engineer - WSO2

Email : sachi...@wso2.com
Mobile : +94714765495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Unsubscribe

[Kartik A]

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

[Dev] Unsubscribe

[Kartik A]

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

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

[Nuwan Dias]

IMO the "iss" claim should be a configurable value. Reusing some other
config such as the Revoke URL is not correct.

IINM, when I went through the code I noticed that we use the same code to
generate backend JWT's "iss" as well as /token API JWT's "iss". So whatever
change we do has to be made in a backwards compatible way so that we don't
break existing applications.

On Mon, Jul 23, 2018 at 6:08 AM Malintha Amarasinghe 
wrote:

> + Dev
>
> On Mon, Jul 23, 2018 at 6:32 PM, Chamin Dias  wrote:
>
>> Hi all,
>>
>> 1. When testing JWT with APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0, we
>> faced an issue.
>>
>> *Setup details : Single node APIM Server (no port offset), ISKM (port
>> offset 1), Default Micro-GW*
>>
>> 2. The issuer (iss) is picked from the  of api-manager.xml
>> in ISKM pack after replacing "/revoke" -> "/token". The default value in
>> ISKM pack is : https://localhost:${https.nio.port}/revoke
>>
>> 3. However, when consuming an API with a JWT token, the Micro-GW shows
>> the below error.
>>
>> ERROR [ballerina/http] - Error while validating JWT token  : {message:"No
>> Registered IDP found for the JWT with issuer name : https://localhost:
>> ${https.nio.port}/token
>>
>> 4. When we decode the JWT (using https://jwt.io/), we found the "iss" as
>> follows. (${https.nio.port} has not been resolved properly)
>>
>> "iss": "https://localhost:${https.nio.port}/token;
>>
>> 5. Then we edited the  of api-manager.xml in ISKM pack as
>> follows.
>>
>> https://localhost:8243/revoke
>>
>> *Note* : In micro-gw.conf of Micro-GW 2.5.0, we have the following.
>>
>> [jwtTokenConfig]
>> issuer="https://localhost:8243/token;
>> audience="http://org.wso2.apimgt/gateway;
>> certificateAlias="wso2apim"
>> trustStore.path="${ballerina.home}/bre/security/ballerinaTruststore.p12"
>> trustStore.password="ballerina"
>>
>> 6. Then, after repeating the process, the API invocation was fine.
>>
>> According to the spec (https://tools.ietf.org/html/rfc7519#section-4.1.1),
>> "iss" claim identifies the principal that issued the JWT. There is
>> another option for this, which is the URL from IS "
>> https://localhost:9444/oauth2/token;. But having this in the JWT token
>> can expose the IS internal oauth2 token URL.
>>
>> So shall we go with the https://localhost:8243 approach?
>>
>> In both cases, we need to hardcode the  as the port
>> property is not resolved properly in non-synapse(IS) environment.
>>
>> Please share your thoughts.
>>
>> (Isuru/Malintha/Fazlan - Please add if I have missed anything.)
>>
>> Thanks.
>>
>> --
>> Chamin Dias
>> Mobile : 0716097455
>> Email : cham...@wso2.com
>> LinkedIn : https://www.linkedin.com/in/chamindias
>>
>>
>
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>


-- 
Nuwan Dias

Director - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0] JWT issuer value

[Malintha Amarasinghe]

+ Dev

On Mon, Jul 23, 2018 at 6:32 PM, Chamin Dias  wrote:

> Hi all,
>
> 1. When testing JWT with APIM 2.5.0 + ISKM 5.6.0 + Micro-GW 2.5.0, we
> faced an issue.
>
> *Setup details : Single node APIM Server (no port offset), ISKM (port
> offset 1), Default Micro-GW*
>
> 2. The issuer (iss) is picked from the  of api-manager.xml
> in ISKM pack after replacing "/revoke" -> "/token". The default value in
> ISKM pack is : https://localhost:${https.nio.port}/revoke
>
> 3. However, when consuming an API with a JWT token, the Micro-GW shows the
> below error.
>
> ERROR [ballerina/http] - Error while validating JWT token  : {message:"No
> Registered IDP found for the JWT with issuer name : https://localhost:
> ${https.nio.port}/token
>
> 4. When we decode the JWT (using https://jwt.io/), we found the "iss" as
> follows. (${https.nio.port} has not been resolved properly)
>
> "iss": "https://localhost:${https.nio.port}/token;
>
> 5. Then we edited the  of api-manager.xml in ISKM pack as
> follows.
>
> https://localhost:8243/revoke
>
> *Note* : In micro-gw.conf of Micro-GW 2.5.0, we have the following.
>
> [jwtTokenConfig]
> issuer="https://localhost:8243/token;
> audience="http://org.wso2.apimgt/gateway;
> certificateAlias="wso2apim"
> trustStore.path="${ballerina.home}/bre/security/ballerinaTruststore.p12"
> trustStore.password="ballerina"
>
> 6. Then, after repeating the process, the API invocation was fine.
>
> According to the spec (https://tools.ietf.org/html/rfc7519#section-4.1.1),
> "iss" claim identifies the principal that issued the JWT. There is
> another option for this, which is the URL from IS "https://localhost:9444/
> oauth2/token". But having this in the JWT token can expose the IS
> internal oauth2 token URL.
>
> So shall we go with the https://localhost:8243 approach?
>
> In both cases, we need to hardcode the  as the port
> property is not resolved properly in non-synapse(IS) environment.
>
> Please share your thoughts.
>
> (Isuru/Malintha/Fazlan - Please add if I have missed anything.)
>
> Thanks.
>
> --
> Chamin Dias
> Mobile : 0716097455
> Email : cham...@wso2.com
> LinkedIn : https://www.linkedin.com/in/chamindias
>
>


-- 
Malintha Amarasinghe
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

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

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Nuwan Dias]

How about Analytics, Rate Limiting?

On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva  wrote:

> Hi all,
>
> Adding to the list of tested scenarios,
>
> 8. Deploy microgateway in kubernetes with a single API and invoke with JWT
> token.
> 9. Tested same for a group of labeled APIs.
>
> Thanks,
> Sachini
>
> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda 
> wrote:
>
>> Tested 0.980.1 updated microgateway with single API mode for both
>> JWT/OAuth token mode in docker and local mode. Didn't noticed any issues
>> and its working as expected. If other scenarios also passed i think we can
>> go ahead and do release.
>>
>> Thanks,
>> sanjeewa.
>>
>> On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa 
>> wrote:
>>
>>>
>>>
>>> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 I think there was an issue with v0.980 and fixed in v0.980.1. Not sure
 if it will affect MG. Please check that.

>>> This was a fix related to packerina. However since this is the only
>>> change included, IMO we can bump the version and do the release.
>>>

 Thanks,
 Bhathiya

 On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
 wrote:

> + [dev]
>
> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
> wrote:
>
>> Hi all,
>>
>> This is to give an update on how API Microgateway ballerina upgrade
>> is going.
>>
>> RajithR came up with
>> https://github.com/wso2/product-microgateway/pull/202/files which
>> contains the syntax changes to support ballerina 0.980.
>>
>> I have tested API Microgateway with the above change and listed below
>> are the scenarios I tested.
>>
>> 1. Created gateway distribution for a single API and invoked through
>> JWT and Oauth tokens.
>> 2. Tested the same for labelled APIs
>> 3. Tested overriding endpoints using system variables.
>> 4. Microgateway analytics
>> 6. Deploy microgateway in docker and invoked API using JWT and
>> Oauth2.
>> 7. Deploy a group of labeled APIs in docker. (to verify
>> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>>
>> Thanks,
>> Sachini
>>
>> --
>>
>> *Sachini De Silva*
>> Software Engineer - WSO2
>>
>> Email : sachi...@wso2.com
>> Mobile : +94714765495
>>
>>
>
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
>

 --
 *Bhathiya Jayasekara*
 *Associate Technical Lead,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

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


>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94 712933253
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Nuwan Dias

Director - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Sachini De Silva]

Hi all,

Adding to the list of tested scenarios,

8. Deploy microgateway in kubernetes with a single API and invoke with JWT
token.
9. Tested same for a group of labeled APIs.

Thanks,
Sachini

On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda 
wrote:

> Tested 0.980.1 updated microgateway with single API mode for both
> JWT/OAuth token mode in docker and local mode. Didn't noticed any issues
> and its working as expected. If other scenarios also passed i think we can
> go ahead and do release.
>
> Thanks,
> sanjeewa.
>
> On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa  wrote:
>
>>
>>
>> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure
>>> if it will affect MG. Please check that.
>>>
>> This was a fix related to packerina. However since this is the only
>> change included, IMO we can bump the version and do the release.
>>
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
>>> wrote:
>>>
 + [dev]

 On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
 wrote:

> Hi all,
>
> This is to give an update on how API Microgateway ballerina upgrade is
> going.
>
> RajithR came up with https://github.com/wso2/
> product-microgateway/pull/202/files which contains the syntax changes
> to support ballerina 0.980.
>
> I have tested API Microgateway with the above change and listed below
> are the scenarios I tested.
>
> 1. Created gateway distribution for a single API and invoked through
> JWT and Oauth tokens.
> 2. Tested the same for labelled APIs
> 3. Tested overriding endpoints using system variables.
> 4. Microgateway analytics
> 6. Deploy microgateway in docker and invoked API using JWT and Oauth2.
> 7. Deploy a group of labeled APIs in docker. (to verify
> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>
> Thanks,
> Sachini
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
>


 --

 *Sachini De Silva*
 Software Engineer - WSO2

 Email : sachi...@wso2.com
 Mobile : +94714765495


>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Associate Technical Lead,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94 712933253
>
> blog :http://sanjeewamalalgoda.
> blogspot.com/ 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sachini De Silva*
Software Engineer - WSO2

Email : sachi...@wso2.com
Mobile : +94714765495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [SP][UX]Dashboard widget drill down views

[Udara Rathnayake]

Thanks Eranga!

On Mon, Jul 23, 2018 at 11:52 AM, Eranga Liyanage  wrote:

> Hi Udara,
>
> Yes, it's the UX approach I was referring to, Had an offline chat with
> Janak as well.
>
> Yes, existing drill-down sample can be used as the baseline. But it needs
> an improvement as well. It does not support returning to the default state
> at the moment. A drill-down option should clearly provide a way to return
> to the default state.
>
> Best regards
> Eranga
>
> On Fri, Jul 20, 2018 at 3:24 PM Udara Rathnayake  wrote:
>
>> Hi Eranga,
>>
>> I hope what you have mentioned is the recommended UX approach.
>> If the above assumption is wrong, Can we come up with a set guideline for
>> this? Can we use the existing drill-down sample as the baseline for
>> developing the drill-down widgets?
>>
>> This will be useful for all other SP based dashboards in the future.
>>
>> Thanks!
>> -UdaraR
>>
>>
>> On Fri, Jul 20, 2018 at 10:30 AM, Eranga Liyanage 
>> wrote:
>>
>>> + Analytics
>>>
>>> Hi Janak,
>>>
>>> Providing a popup view is not a good practice. If you have consistent
>>> views its good to show on the same widget. If you have a totally different
>>> view or too much data to show, it's better to direct to a  different page.
>>>
>>> Best regards
>>> Eranga
>>>
>>> On Fri, Jul 20, 2018 at 10:18 AM Imesh Chandrasiri 
>>> wrote:
>>>
 Hi Janak,

 When it comes to a drilled down chat, the user clearly should know that
 the chart is showing more detailed data in it, while interacting with it.
 Furthermore I found an article[1] which discuss how an intuitive drilled
 down chart should be designed and the points we should consider when
 designing one.

 [1] - https://www.fusioncharts.com/charting-best-practices/
 drill-down-interface/

 *Thanks and Best Regards,*
 Imesh Ashandimal Chandrasiri
 *Software Engineer*
 WSO2, Inc.
 lean . enterprise . middleware
 *E:* ime...@wso2.com | *P:* 0716519187


 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, retransmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.


 On Thu, Jul 19, 2018 at 8:27 PM Janak Amarasena  wrote:

> Hi,
>
> What is the best practice when creating a drilled down view in a
> widget? Is it to completely replace the existing view with the new one or
> to give a popped up view of the details(which may be overlayed over other
> widgets). It is also required to move back and forth between the main view
> and the drilled down view.
>
> Thank you,
> Best Regards,
>
> --
> *Janak Amarasena*
>
> Software Engineer
>
> Email: ja...@wso2.com
>
> Mobile: +9464144
>
> Web: https://wso2.com
>
>
> 
> ___
> 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

>>>
>>>
>>> --
>>> *Eranga Liyanage*
>>> Senior UX Engineer | WSO2
>>> Mob : +94 77 395 
>>> Blog : https://medium.com/@erangatl
>>> Linkedin : https://www.linkedin.com/in/erangaliyanage
>>>
>>>
>>
>>
>> --
>> Regards,
>> UdaraR 
>>
>
>
> --
> *Eranga Liyanage*
> Senior UX Engineer | WSO2
> Mob : +94 77 395 
> Blog : https://medium.com/@erangatl
> Linkedin : https://www.linkedin.com/in/erangaliyanage
>
>


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

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Sanjeewa Malalgoda]

Tested 0.980.1 updated microgateway with single API mode for both JWT/OAuth
token mode in docker and local mode. Didn't noticed any issues and its
working as expected. If other scenarios also passed i think we can go ahead
and do release.

Thanks,
sanjeewa.

On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa  wrote:

>
>
> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara 
> wrote:
>
>> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure if
>> it will affect MG. Please check that.
>>
> This was a fix related to packerina. However since this is the only change
> included, IMO we can bump the version and do the release.
>
>>
>> Thanks,
>> Bhathiya
>>
>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
>> wrote:
>>
>>> + [dev]
>>>
>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
>>> wrote:
>>>
 Hi all,

 This is to give an update on how API Microgateway ballerina upgrade is
 going.

 RajithR came up with
 https://github.com/wso2/product-microgateway/pull/202/files which
 contains the syntax changes to support ballerina 0.980.

 I have tested API Microgateway with the above change and listed below
 are the scenarios I tested.

 1. Created gateway distribution for a single API and invoked through
 JWT and Oauth tokens.
 2. Tested the same for labelled APIs
 3. Tested overriding endpoints using system variables.
 4. Microgateway analytics
 6. Deploy microgateway in docker and invoked API using JWT and Oauth2.
 7. Deploy a group of labeled APIs in docker. (to verify
 https://github.com/wso2/product-microgateway/issues/199 is fixed)

 Thanks,
 Sachini

 --

 *Sachini De Silva*
 Software Engineer - WSO2

 Email : sachi...@wso2.com
 Mobile : +94714765495


>>>
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94 712933253

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

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

[Dev] WSO2 module to use Zipkin as tracing tool

[JOSE MARIA ALVAREZ FERNANDEZ]

Hi,

We have been trying to build a module for WSO2 to work within a Microservice 
environment, and participate in a tracing context (in this case with Zipkin B3 
Headers -> https://github.com/openzipkin/b3-propagation/blob/master/README.md)  
and the result, although in beta, is here:

https://github.com/jmalvarezf/wso2-zipkin-tracer

We just wanted to know if that could be useful for you. Tracing is a great tool 
for a microservices environment, and in case you want to use WSO2 as the Api 
Manager, we find very important for the gateway to work within that context.

The idea was to create an Axis2 module, and a handler, the first one to manage 
all the requests to the gateway, and the second to manage the API requests.

Best regards,

Jose Maria.


---

Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener 
informaci?n confidencial, siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgaci?n copia o distribuci?n a terceros sin la autorizaci?n 
expresa del remitente. Si Vd. ha recibido este mensaje err?neamente, se ruega 
lo notifique al remitente y proceda a su borrado.

Gracias por su colaboraci?n.

This message (including any attachments) may contain confidential information. 
It is intended for use by the recipient only. Any dissemination, copying or 
distribution to third parties without the express consent of the sender is 
strictly prohibited. If you have received this message in error, please delete 
it immediately and notify the sender.

Thank you for your collaboration.

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

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Isuru Haththotuwa]

On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara 
wrote:

> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure if
> it will affect MG. Please check that.
>
This was a fix related to packerina. However since this is the only change
included, IMO we can bump the version and do the release.

>
> Thanks,
> Bhathiya
>
> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva 
> wrote:
>
>> + [dev]
>>
>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is to give an update on how API Microgateway ballerina upgrade is
>>> going.
>>>
>>> RajithR came up with https://github.com/wso2/
>>> product-microgateway/pull/202/files which contains the syntax changes
>>> to support ballerina 0.980.
>>>
>>> I have tested API Microgateway with the above change and listed below
>>> are the scenarios I tested.
>>>
>>> 1. Created gateway distribution for a single API and invoked through JWT
>>> and Oauth tokens.
>>> 2. Tested the same for labelled APIs
>>> 3. Tested overriding endpoints using system variables.
>>> 4. Microgateway analytics
>>> 6. Deploy microgateway in docker and invoked API using JWT and Oauth2.
>>> 7. Deploy a group of labeled APIs in docker. (to verify
>>> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>>>
>>> Thanks,
>>> Sachini
>>>
>>> --
>>>
>>> *Sachini De Silva*
>>> Software Engineer - WSO2
>>>
>>> Email : sachi...@wso2.com
>>> Mobile : +94714765495
>>>
>>>
>>
>>
>> --
>>
>> *Sachini De Silva*
>> Software Engineer - WSO2
>>
>> Email : sachi...@wso2.com
>> Mobile : +94714765495
>>
>>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Bhathiya Jayasekara]

I think there was an issue with v0.980 and fixed in v0.980.1. Not sure if
it will affect MG. Please check that.

Thanks,
Bhathiya

On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva  wrote:

> + [dev]
>
> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
> wrote:
>
>> Hi all,
>>
>> This is to give an update on how API Microgateway ballerina upgrade is
>> going.
>>
>> RajithR came up with
>> https://github.com/wso2/product-microgateway/pull/202/files which
>> contains the syntax changes to support ballerina 0.980.
>>
>> I have tested API Microgateway with the above change and listed below are
>> the scenarios I tested.
>>
>> 1. Created gateway distribution for a single API and invoked through JWT
>> and Oauth tokens.
>> 2. Tested the same for labelled APIs
>> 3. Tested overriding endpoints using system variables.
>> 4. Microgateway analytics
>> 6. Deploy microgateway in docker and invoked API using JWT and Oauth2.
>> 7. Deploy a group of labeled APIs in docker. (to verify
>> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>>
>> Thanks,
>> Sachini
>>
>> --
>>
>> *Sachini De Silva*
>> Software Engineer - WSO2
>>
>> Email : sachi...@wso2.com
>> Mobile : +94714765495
>>
>>
>
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
>

-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.

[Ruwan Abeykoon]

Hi Farasath,
The failing XML file seems semantically identical to the one with namespace.
What can be the reason for failure ?

Cheers,
Ruwan

On Mon, Jul 23, 2018 at 12:33 PM Achini Jayasena  wrote:

> Hi Farasath and Doc team,
>
> @ Farasath, I  got the matadata file sample given in the document. [1].
> It's working  after add XML name spaces.
> And also is there a way to enable the response signing through the
> metadata file upload? Is metadata file support for all manual saml
> configurations in IS?
>
> @doc team, Please do the update for metadata configuration file in
> document  [1] since the given sample not working without Xml name spaces.
>
> Please find the updated metadata file attached here with.
>
> [1] :
> https://docs.wso2.com/display/IS550/Adding+and+Configuring+a+Service+Provider#AddingandConfiguringaServiceProvider-Metadatafileconfiguration
>
>
>
> *Thanks & Best Regards!*
>
> *Achini Jayasena*
> *Software Engineer - QA | WSO2*
>
> Email: achi...@wso2.com
> Mobile: +943 882 897
>
> [image: http://wso2.com/signature] 
>
> On Fri, Jul 20, 2018 at 8:40 PM, Farasath Ahamed 
> wrote:
>
>> Hi Achini,
>>
>> Seems like there is a possible issue with the metadata file you have
>> created. (Initially, I thought it was due to a binary character in the
>> file, but it doesn't seem to be the case). A similar error has been
>> reported in [1]. And the resolution was to fix the 
>> with a specific format (With XML namespaces etc.)
>>
>> I created a metadata file using https://www.samltool.com/sp_metadata.php
>> with the same details(see the attachment) and uploaded it to IS 5.5.0 WUM
>> pack and it worked without any issue. To find the issue with your metadata
>> file can you explain how you generated the metadata file?
>>
>>
>> [1]
>> http://codeverge.com/novell.support.access-manager/error-importing-saml2-metadata/1980697
>>
>> On Fri, Jul 20, 2018 at 4:10 PM, Achini Jayasena 
>> wrote:
>>
>>> Hi all,
>>>
>>> Seems this is a bug and I have created a git issue [1]. please find the
>>> error log from below.
>>>
>>> product version. 5.5 latest wum update.
>>>
>>> [1] - https://github.com/wso2/product-is/issues/3453
>>>
>>> [2018-07-20 15:18:57,194] ERROR
>>> {org.wso2.carbon.identity.sp.metadata.saml2.util.Parser} -  Error While
>>> reading Service Provider metadata xml
>>> org.xml.sax.SAXParseException: Element type "EntityDescriptor" must be
>>> followed by either attribute specifications, ">" or "/>".
>>> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
>>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
>>> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
>>> at org.wso2.carbon.identity.sp.me
>>> tadata.saml2.util.Parser.generateMetadataObjectFromString(Parser.java:252)
>>> at org.wso2.carbon.identity.sp.me
>>> tadata.saml2.util.Parser.parse(Parser.java:199)
>>> at
>>> org.wso2.carbon.identity.sso.saml.admin.SAMLSSOConfigAdmin.uploadRelyingPartyServiceProvider(SAMLSSOConfigAdmin.java:148)
>>> at
>>> org.wso2.carbon.identity.sso.saml.SAMLSSOConfigService.uploadRPServiceProvider(SAMLSSOConfigService.java:71)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:170)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>>> at
>>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:441)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:227)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>> at
>>> 

Re: [Dev] API Microgateway Ballerina Upgrade to 0.980

[Sachini De Silva]

+ [dev]

On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva 
wrote:

> Hi all,
>
> This is to give an update on how API Microgateway ballerina upgrade is
> going.
>
> RajithR came up with https://github.com/wso2/
> product-microgateway/pull/202/files which contains the syntax changes to
> support ballerina 0.980.
>
> I have tested API Microgateway with the above change and listed below are
> the scenarios I tested.
>
> 1. Created gateway distribution for a single API and invoked through JWT
> and Oauth tokens.
> 2. Tested the same for labelled APIs
> 3. Tested overriding endpoints using system variables.
> 4. Microgateway analytics
> 6. Deploy microgateway in docker and invoked API using JWT and Oauth2.
> 7. Deploy a group of labeled APIs in docker. (to verify
> https://github.com/wso2/product-microgateway/issues/199 is fixed)
>
> Thanks,
> Sachini
>
> --
>
> *Sachini De Silva*
> Software Engineer - WSO2
>
> Email : sachi...@wso2.com
> Mobile : +94714765495
>
>


-- 

*Sachini De Silva*
Software Engineer - WSO2

Email : sachi...@wso2.com
Mobile : +94714765495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.

[Achini Jayasena]

Hi Farasath and Doc team,

@ Farasath, I  got the matadata file sample given in the document. [1].
It's working  after add XML name spaces.
And also is there a way to enable the response signing through the metadata
file upload? Is metadata file support for all manual saml configurations in
IS?

@doc team, Please do the update for metadata configuration file in
document  [1] since the given sample not working without Xml name spaces.

Please find the updated metadata file attached here with.

[1] : https://docs.wso2.com/display/IS550/Adding+and+Configuring+a
+Service+Provider#AddingandConfiguringaServiceProvider-Metad
atafileconfiguration



*Thanks & Best Regards!*

*Achini Jayasena*
*Software Engineer - QA | WSO2*

Email: achi...@wso2.com
Mobile: +943 882 897

[image: http://wso2.com/signature] 

On Fri, Jul 20, 2018 at 8:40 PM, Farasath Ahamed  wrote:

> Hi Achini,
>
> Seems like there is a possible issue with the metadata file you have
> created. (Initially, I thought it was due to a binary character in the
> file, but it doesn't seem to be the case). A similar error has been
> reported in [1]. And the resolution was to fix the 
> with a specific format (With XML namespaces etc.)
>
> I created a metadata file using https://www.samltool.com/sp_metadata.php
> with the same details(see the attachment) and uploaded it to IS 5.5.0 WUM
> pack and it worked without any issue. To find the issue with your metadata
> file can you explain how you generated the metadata file?
>
>
> [1] http://codeverge.com/novell.support.access-manager/
> error-importing-saml2-metadata/1980697
>
> On Fri, Jul 20, 2018 at 4:10 PM, Achini Jayasena  wrote:
>
>> Hi all,
>>
>> Seems this is a bug and I have created a git issue [1]. please find the
>> error log from below.
>>
>> product version. 5.5 latest wum update.
>>
>> [1] - https://github.com/wso2/product-is/issues/3453
>>
>> [2018-07-20 15:18:57,194] ERROR 
>> {org.wso2.carbon.identity.sp.metadata.saml2.util.Parser}
>> -  Error While reading Service Provider metadata xml
>> org.xml.sax.SAXParseException: Element type "EntityDescriptor" must be
>> followed by either attribute specifications, ">" or "/>".
>> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
>> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
>> at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.gener
>> ateMetadataObjectFromString(Parser.java:252)
>> at org.wso2.carbon.identity.sp.metadata.saml2.util.Parser.parse
>> (Parser.java:199)
>> at org.wso2.carbon.identity.sso.saml.admin.SAMLSSOConfigAdmin.u
>> ploadRelyingPartyServiceProvider(SAMLSSOConfigAdmin.java:148)
>> at org.wso2.carbon.identity.sso.saml.SAMLSSOConfigService.uploa
>> dRPServiceProvider(SAMLSSOConfigService.java:71)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RP
>> CUtil.java:212)
>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>> nessLogic(RPCMessageReceiver.java:117)
>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>> bstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:170)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:82)
>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>> (LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:441)
>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:227)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.wso2.carbon.identity.sso.saml.stub.IdentitySAMLSSOConfig
>> ServiceStub.uploadRPServiceProvider(IdentitySAMLSSOConfigSer
>> viceStub.java:3033)
>> at org.wso2.carbon.identity.sso.saml.ui.client.SAMLSSOConfigSer
>> viceClient.uploadServiceProvider(SAMLSSOConfigServiceClient.java:95)
>> at org.wso2.carbon.identity.sso.saml.ui.client.SamlSPMetadataUp
>> loadExecutor.execute(SamlSPMetadataUploadExecutor.java:88)
>> 

Re: [Dev] [SP][UX]Dashboard widget drill down views

[Eranga Liyanage]

Hi Udara,

Yes, it's the UX approach I was referring to, Had an offline chat with
Janak as well.

Yes, existing drill-down sample can be used as the baseline. But it needs
an improvement as well. It does not support returning to the default state
at the moment. A drill-down option should clearly provide a way to return
to the default state.

Best regards
Eranga

On Fri, Jul 20, 2018 at 3:24 PM Udara Rathnayake  wrote:

> Hi Eranga,
>
> I hope what you have mentioned is the recommended UX approach.
> If the above assumption is wrong, Can we come up with a set guideline for
> this? Can we use the existing drill-down sample as the baseline for
> developing the drill-down widgets?
>
> This will be useful for all other SP based dashboards in the future.
>
> Thanks!
> -UdaraR
>
>
> On Fri, Jul 20, 2018 at 10:30 AM, Eranga Liyanage 
> wrote:
>
>> + Analytics
>>
>> Hi Janak,
>>
>> Providing a popup view is not a good practice. If you have consistent
>> views its good to show on the same widget. If you have a totally different
>> view or too much data to show, it's better to direct to a  different page.
>>
>> Best regards
>> Eranga
>>
>> On Fri, Jul 20, 2018 at 10:18 AM Imesh Chandrasiri 
>> wrote:
>>
>>> Hi Janak,
>>>
>>> When it comes to a drilled down chat, the user clearly should know that
>>> the chart is showing more detailed data in it, while interacting with it.
>>> Furthermore I found an article[1] which discuss how an intuitive drilled
>>> down chart should be designed and the points we should consider when
>>> designing one.
>>>
>>> [1] -
>>> https://www.fusioncharts.com/charting-best-practices/drill-down-interface/
>>>
>>> *Thanks and Best Regards,*
>>> Imesh Ashandimal Chandrasiri
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> *E:* ime...@wso2.com | *P:* 0716519187
>>>
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>>
>>> On Thu, Jul 19, 2018 at 8:27 PM Janak Amarasena  wrote:
>>>
 Hi,

 What is the best practice when creating a drilled down view in a
 widget? Is it to completely replace the existing view with the new one or
 to give a popped up view of the details(which may be overlayed over other
 widgets). It is also required to move back and forth between the main view
 and the drilled down view.

 Thank you,
 Best Regards,

 --
 *Janak Amarasena*

 Software Engineer

 Email: ja...@wso2.com

 Mobile: +9464144

 Web: https://wso2.com


 
 ___
 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
>>>
>>
>>
>> --
>> *Eranga Liyanage*
>> Senior UX Engineer | WSO2
>> Mob : +94 77 395 
>> Blog : https://medium.com/@erangatl
>> Linkedin : https://www.linkedin.com/in/erangaliyanage
>>
>>
>
>
> --
> Regards,
> UdaraR 
>


-- 
*Eranga Liyanage*
Senior UX Engineer | WSO2
Mob : +94 77 395 
Blog : https://medium.com/@erangatl
Linkedin : https://www.linkedin.com/in/erangaliyanage
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IAM] Modifying consent purposes associations

[Omindu Rathnaweera]

Hi All,

As per the current implementation, we do not allow to edit or delete
consent purposes which are associated with a consent receipt. The reason
behind such a design decision was to preserve the immutability of the
consent receipt. Meaning, to prevent modifying the existing consent
receipts which are associated with purposes if a purpose is modified.

However, with the improvements we are introducing with 5.7.0 privacy
features, Self Signup and JIT functionalities will have a tight dependency
on purposes and there will be more involvement around configuring purposes.
The purposes defined for these scenarios cannot be modified once they are
associated with a consent receipt.

Therefore it would be convenient for the users to have the option to modify
the existing consent purposes. But doing so should not change the existing
consent receipts.

In order to achieve this requirement. I see the following

i) We can provide the capability to modify the existing purposes. For this
we may have to duplicate the purposes when adding receipts and reference
the duplicated purpose from the receipt.

ii) Without providing the capability to modify the purposes, we can
maintain a separate association of purposes and Self signup/JIT similar to
what we are doing for service providers. This way a user can pick what
purposes should be associated with a certain flow without modifying the
existing purposes.

Appreciate your thoughts on this.

Regards,
Omindu.

-- 
Omindu Rathnaweera
Senior Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev