Re: [Dev] WSO2 Docker images layered composition

[Akila Ravihansa Perera]

Hi,

I've merged the PR [1] which introduces wso2base image. This base image
will include packages that were previously installed from Puppet (zip and
unzip), and those are removed from Puppet/Hiera side. With that we should
be able to build WSO2 Docker images in offline mode.

wso2base image is pushed to DockerHub [2] as well. You don't need to build
it locally.

[1] https://github.com/wso2/dockerfiles/pull/46
[2] https://hub.docker.com/r/wso2/wso2base/

Thanks.

On Thu, Jun 23, 2016 at 3:06 PM, Imesh Gunaratne  wrote:

> Hi Isuru/Akila,
>
> On Tue, Jun 21, 2016 at 3:19 PM, Isuru Haththotuwa 
> wrote:
>
> To summarize:
>
>- Publish a wso2 product specific docker image to a local docker
>repository (we can even push to dockerhub, without the JDK distribution and
>ask the users to provide the JDK when spinning up a container from the
>image).
>
> A good suggestion, since we currently track product downloads for
> analytics we might need to find a way to do the same with Docker if we were
> to publicly share WSO2 Docker images. Otherwise using a local registry with
> a base/product image would do.
>
>- Guide the users/developers to create their own Dockerfile extending
>from the original wso2 product Docker image.
>
> We might need to solve 1, to do this.
>
> On Thu, Jun 23, 2016 at 9:42 AM, Isuru Haththotuwa 
> wrote:
>
>>
>> On Tue, Jun 21, 2016 at 6:54 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>>
>>> I'm not against having a base image for the WSO2 Docker images. But,
>> IMHO the advantages should be significant for doing so. AFAIU there is no
>> significant advantage of doing so currently. But, this is my take only.
>> Therefore lets get the input from the community on this matter.
>>
>> @Imesh: WDYT?
>>
>> ​Currently almost all of us use a base image locally to reduce the
> internet bandwidth usage due to executing docker builds from scratch.
> Therefore I think it would be better to push that to the remote repository.
>
> As Akila has mentioned the only downside of this is the image size being
> increased by around 100 MB. ​When creating Docker images for production
> deployment those optimizations can be taken into account.
>
> Thanks
>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> Lean . Enterprise . Middleware
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

[Dev] WSO2 Dashboard Server 2.1.0-M3 Released!

[Sinthuja Ragendran]

WSO2 Dashboard Server 2.1.0-M3 Released!

WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 3. This release comes with the following
bug fixes and features. You can download the distribution from [1].
Bug

[UES-924] - In drill down dashboards (pub-sub model) if subscriber gadget
get maximized it gets redrawn in default state
[UES-933] - Failed to load resource error when loading usa-social gadget
[UES-944] - Maximize gadget is not fitting the screen correctly when the
left pane is expanded
[UES-947] - Scroll bar is shown in the middle of the page when left
navigation pane is collapsed in view mode
[UES-952] - Maximization is not working in designer mode
[UES-955] - Show an error in the front end when the user input db query is
incorrect
[UES-956] - Validate database URL, table name and credentials in configure
provider pane
[UES-960] - Side bar which lists the pages in the view mode is not linked
correctly
[UES-962] - Exported Dashboard.json do not load the pages other than the
landing page.
[UES-966] - location need to be fixed where the backed files are copied
Improvement

[UES-936] - Role based permissions for creating, managing and deleting
dashboards
[UES-967] - Improving and fixing issues in gadget generation wizard
New Feature

[UES-959] - Share Dashboards among tenants
[UES-963] - Role based access control for gadgets
[UES-965] - Add/Delete gadget and layout from portal app
Task

[UES-922] - Update create gadgets flow with new UI/UX
[UES-953] - Show an error in the front end, if the database driver is not
available
Reporting Issues

Issues can be reported through the Public JIRA
 project for WSO2 Dashboard Server.


[1]
https://github.com/wso2/product-ds/releases/download/v2.1.0-m3/wso2ds-2.1.0-SNAPSHOT.zip


Thanks,

Dashboard Server Team.

-- 
*Sinthuja Rajendran*
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] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi all,

This is the list of external libraries I have added to the project. Pleases
let me know if they satisfy the licience requirements.

commons-codec-1.9.jar
json-simple.jar
java-mail-1.4.4.jar
com.sun.net.ssl.jar

Thanks and regards

Nathiesha

On Wed, Jun 22, 2016 at 9:23 AM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi Kavith,
>
> I pushed the latest code to the Git repository now. [1]
> [1]-
> https://github.com/nathiesha/org.wso2.developerstudio.eclipse.errorreporter.git
>
> Thanks and regards
>
> Nathiesha
>
> On Wed, Jun 22, 2016 at 8:48 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Can you please push your latest code Base to the git hub repository? We
>> need to have a code review before winding up mid term evaluation.
>>
>> Thanks
>>
>>
>> On Wednesday, June 22, 2016, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Here I have attached a draft class diagram of the Error Reporting tool.
>>> Please suggest on any modifications needed to be done to its structure.
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>> On Wed, Jun 8, 2016 at 10:44 AM, Nathiesha Maddage <
>>> nathieshamadd...@gmail.com> wrote:
>>>
 Hi all,

 I think what you suggest is a good idea. I am quite familiar with WSO2
 Online Support System now, but I am quite new to WSO2-DAS. I went
 through the http://wso2.com/products/data-analytics-server/ website to
 get a basic idea on what WSO2-DAS is about. I will refer more to get a
 clear picture on how it works.


 Thanks and regards

 Nathiesha

 On Tue, Jun 7, 2016 at 7:12 PM, Susinda Perera 
 wrote:

> Hi All
>
> How about configuring wso2-DAS at the wso2 side to collect and analyse
> error/logs. It is not only reporting to wso2 JIRA, it may be some other
> system so 'reporting to' should be an configurable and pluggable feature.
> If we are publishing to DAS, we have to come up with format for stream
> definition, which may need some literature survey on how other log
> analysers work etc.
>
> Thanks
> Susinda
>
> On Tue, Jun 7, 2016 at 3:48 PM, Jasintha Dasanayake  > wrote:
>
>> HI Nathiesha
>>
>> I couldn't see any commit[1] during the last couple of week, it's
>> good practices to do commit stuff daily basis, because it's easy for us 
>> to
>> review and provide regular feedbacks.
>>
>> Shall we have a progress review during the next week ?.
>>
>> Thanks and Regards
>> /Jasintha
>>
>> [1]-
>> https://github.com/nathiesha/org.wso2.developerstudio.eclipse.errorreporter.git
>>
>> On Sat, May 14, 2016 at 6:12 PM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I formatted and cleaned the code and added the licence header.
>>> Regarding the naming of the project, I named the project
>>> as org.wso2.developerstudio.eclipse.errorreporter for now. And about the
>>> packages, I referred to the developer studio plugins projects you have 
>>> sent
>>> me. However as I am still not familiar with the naming conventions for
>>> developer studio plugins I temporarily created a couple of packages to
>>> group the Java classes. I hope I can do the proper renaming and 
>>> packaging
>>> later with your support.
>>>
>>> I created the ErrorInfoCollector class and there all the system
>>> information and error related information is fetched. However I couldn't
>>> find a method to get the plugin version and I am still working on it. 
>>> And
>>> the error report that I have sent you previously had an attribute called
>>> fingerprint and it also contained a set of bundle information. Those two
>>> parts I could not understand. So I left them for now.
>>> As you suggested, this class can be improved later to
>>> collect further information regarding the error.
>>>
>>> I started with preferences page as well. I created a draft
>>> preference page and currently working on improving it.
>>>
>>> This is the new GitHub link of the project repository. Please refer
>>> to this afterwards.
>>>
>>> Link-
>>> https://github.com/nathiesha/org.wso2.developerstudio.eclipse.errorreporter.git
>>>
>>> Thanks and Regards
>>>
>>> Nathiesha
>>>
>>>
>>>
>>> On Fri, May 13, 2016 at 12:26 PM, Kavith Lokuhewage >> > wrote:
>>>
 Hi Nathiesha,

 Please find my inline comments.

 On Wed, May 11, 2016 at 12:10 PM, Nathiesha Maddage <
 nathieshamadd...@gmail.com> wrote:

> Hi all,
>
> Regarding the preference settings, as I have read, the plugins
> that are started early are listed in preferences-general-startup and

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> I still see some issues in the code.
>
> 1. Make sure to use consts when appropriate [1]
> 2. Where do you use tenantId [2] ?
> 3. Use the actual parameter key in the error message [3] instead of hard
> coding it
> 4. You need to adhere to max line len of 120 chars. I see this standard
> being violated in couple of places [4]. Use IDE formatting tool to fix this
> 5. Do not keep empty spaces [5]. This is bad code styling
>
> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6]. Shall
> we make Netflix Feign the standard for this?
>

​+1 Yes, definitely.

Thanks​


>
> [1]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>
> Thanks.
>
> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes I completed the evaluation.
>>>
>> ​Great! Thanks!​
>>
>>> Thanks,
>>>
>>> Get Outlook for Android 
>>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
>>> im...@wso2.com> wrote:
>>>
>>> Hi Osura,

 Were you able to submit the midterm evaluation? Might be better to do
 it soon.

 Thanks
 ​Imesh​


>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

I still see some issues in the code.

1. Make sure to use consts when appropriate [1]
2. Where do you use tenantId [2] ?
3. Use the actual parameter key in the error message [3] instead of hard
coding it
4. You need to adhere to max line len of 120 chars. I see this standard
being violated in couple of places [4]. Use IDE formatting tool to fix this
5. Do not keep empty spaces [5]. This is bad code styling

@Imesh: Osura has used Apache HTTP client to send HTTP requests [6]. Shall
we make Netflix Feign the standard for this?

[1]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
[2]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
[3]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
[4]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
[5]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
[6]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234

Thanks.

On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne  wrote:

>
>
> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>
>> Hi Imesh,
>>
>> Yes I completed the evaluation.
>>
> ​Great! Thanks!​
>
>> Thanks,
>>
>> Get Outlook for Android 
>>
>>
>>
>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" > > wrote:
>>
>> Hi Osura,
>>>
>>> Were you able to submit the midterm evaluation? Might be better to do it
>>> soon.
>>>
>>> Thanks
>>> ​Imesh​
>>>
>>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> Lean . Enterprise . Middleware
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] Clarification on closing database connections when using DAO Manager

[Samith Dassanayake]

Hi Sabra,

IMHO I think we should close the db connection in the Dao Manager. That way
Dao manager has the control over the transactions and we can implement fine
grained Dao Classes.

Regards,
Samith

On Thu, Jun 23, 2016 at 10:28 PM, Danushka Fernando 
wrote:

> Ping
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Fri, Jun 17, 2016 at 1:55 PM, Sabra Ossen  wrote:
>
>> Hi All,
>>
>> What is the best practice for closing database connections when we are
>> using the DAO Pattern with DAO Manager?
>>
>> According to [1] the suggestion is to create a DAO Manager and include
>> the database connection object within the DAO Manager. Each DAO Object is
>> instantiated by passing the database connection and the connection is
>> closed from the DAO Manager after execution of the query.
>>
>> I went through a lot of WSO2 product related code but was not able to see
>> the usage of a DAO Manager and I saw that the database connections were
>> closed in the DAO class itself.
>>
>> What is the suggested practice? Any clarification on this issue is
>> appreciated.
>>
>> [1] http://tutorials.jenkov.com/java-persistence/dao-manager.html
>>
>> Thanks and Regards.
>>
>> --
>> *Sabra Ossen*
>> *Software Engineer*
>> Email: sa...@wso2.com
>> Mobile: +94 767 837356
>>
>> ___
>> 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
>
>


-- 
Best Regards

Samith Dassanayake
Senior Software Engineer | Cloud TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +947 76207351
Blog : buddycode.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [C5] How do we get IP address of the Carbon Server?

[Manuranga Perera]

Yes, this will work regardless; since Host header is clients way of saying
to the server "this is the name I used to reach you". So it is granted to
reach the server from client, regardless of server IP bindings/ client
proxies/ load balancers.

Places it will not work:
1) Non HTTP flows - Can't use this approach to print "Mgt Console URL: .."
log message. Since at the point server has not received any client request
2) When one node needs other nodes ip - e.g.: When Mgt node has to show
workers ip for the proxy URL
3) HTTP 1.0 protocol - since Host was introduced in HTTP 1.1, but 1.0 is
very rare now.


On Fri, Jun 24, 2016 at 10:10 AM, Isuru Haththotuwa  wrote:

> Hi Manu,
>
> On Fri, Jun 24, 2016 at 7:33 PM, Manuranga Perera  wrote:
>
>> Having server IP/Hostname in configuration/kernel is a mistake we have
>> done in C4. This makes it harder to setup load balances since we have to do
>> more configuration. It's also confusing when same server is in multiple
>> networks and therefore have multiple IPs. Best thing we should do is to use
>> the HTTP Host header to get the server hostname. This is what J2EE returns
>> by default [1] and it will work with loadbancers without extra config from
>> our side when host is forwarded.
>>
> Will this approach work where a server is required to bind to an IP
> address, or when a server needs to bind to one IP and advertise another IP?
>
>>
>> I think we should recommend this approach for all C5 server IP scenarios.
>> (there will be edge cases when there are no HTTP requests, which we have to
>> come up with something, but it's rare)
>>
>> (In UUF we should automatically handle this kind of thing)
>>
>> [1]
>> http://docs.oracle.com/javaee/5/api/javax/servlet/ServletRequest.html#getServerName()
>>
>> On Fri, Jun 24, 2016 at 8:33 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Since there is no transport level information at C5 kernel level, we
>>> can't add this to kernel. The relevant transport implementation should
>>> provide such information IMO. For example, netty based http implementation
>>> can provide information about the IP or Ports when server is ready serve
>>> requests.
>>>
>>> On Fri, Jun 24, 2016 at 2:09 PM, Rasika Perera  wrote:
>>>
 Hi All,

 How do we retrieve $subject that the server has binded? In 4.4.x it was
 available via java system property "bind.address" ?

 There are use-cases such as in IoTS we need to provide server ip
 address for downloading device agents. "localhost" would not work when the
 invoker is remote.

 ​Thanks​

 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: http://lk.linkedin.com/in/rasika90

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Convert a timestamp in long format to readable format in HBS.

[Manuranga Perera]

Hi Hemika,

Converting from long to string should happen on client side. Otherwise we
will display times in server time zone, which is not useful. You should
always record time in long UTC and send to the client in long. UTC to
current time-zone conversion should happen at client as follows.

var d = new Date(132433920);

Additionally if the time is close to the current date you can show the
difference for better UX [1]

[1] https://github.com/odyniec/tinyAgo-js/blob/master/tinyAgo.js

On Fri, Jun 24, 2016 at 1:50 AM, Rasika Perera  wrote:

> Hi Hemika,
>
> I have a list of java objects that I am returning from the server side JS
>> where the object has a timestamp property in long format(milliseconds), in
>> that case I will have to iterate the list and get the timestamp of each
>> object and store them in another list/map and return that separately.
>
> I think this is not specific to the UUF. Even when you are using JSPs you
> have to convert your data model into view model. You may also need to
> prettify data fields such as capitalising first letter etc.
>
> Is it the correct way to do ?
>
> I think you need to retrieve the list/map from the backend(data model) and
> iterate through the fields. When iterating If it is a map, you can make
> changes and store back in the same map and return it(view model) into the
> HBS context.
>
> Regards,
> Rasika
>
> On Fri, Jun 24, 2016 at 10:32 AM, Hemika Kodikara  wrote:
>
>> Hi Rasika,
>>
>> I have a list of java objects that I am returning from the server side JS
>> where the object has a timestamp property in long format(milliseconds), in
>> that case I will have to iterate the list and get the timestamp of each
>> object and store them in another list/map and return that separately.
>>
>> Is it the correct way to do ?
>>
>> Regards,
>> Hemika
>>
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Fri, Jun 24, 2016 at 7:01 AM, Rasika Perera  wrote:
>>
>>> Really ?
 Rasika/Sajith, did you guys implement a way to plug-in helpers?
 I don't believe we should have app specific custom helpers, it makes
 code hard to understand for someone who is not from that team. I believe we
 should use the 'toViewModel' function to do any rendering specific
 conversions. But if there are helpers that is used platform-wide they
 should be implemented/imported by UUF team.
>>>
>>> ​We did not expose handlebar environment into the
>>> controller(serversideJs). Thus, I don't think App developers can register
>>> their handlebar custom-helpers into ​HBS.
>>>
>>> You can process the timestamp in long format to readable format in js
 side and return that to display in hbs.
>>>
>>> ​+1. ​This is the recommended approach.
>>>
>>>
>>> On Fri, Jun 24, 2016 at 1:03 AM, Manuranga Perera  wrote:
>>>
 Yeah, there is a way to write custom helpers in HBS and we can use it
> by registering the helper in HBS.


 Really ?
 Rasika/Sajith, did you guys implement a way to plug-in helpers?

 I don't believe we should have app specific custom helpers, it makes
 code hard to understand for someone who is not from that team. I believe we
 should use the 'toViewModel' function to do any rendering specific
 conversions. But if there are helpers that is used platform-wide they
 should be implemented/imported by UUF team.

 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com

>>>
>>>
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [C5] How do we get IP address of the Carbon Server?

[Isuru Haththotuwa]

Hi Manu,

On Fri, Jun 24, 2016 at 7:33 PM, Manuranga Perera  wrote:

> Having server IP/Hostname in configuration/kernel is a mistake we have
> done in C4. This makes it harder to setup load balances since we have to do
> more configuration. It's also confusing when same server is in multiple
> networks and therefore have multiple IPs. Best thing we should do is to use
> the HTTP Host header to get the server hostname. This is what J2EE returns
> by default [1] and it will work with loadbancers without extra config from
> our side when host is forwarded.
>
Will this approach work where a server is required to bind to an IP
address, or when a server needs to bind to one IP and advertise another IP?

>
> I think we should recommend this approach for all C5 server IP scenarios.
> (there will be edge cases when there are no HTTP requests, which we have to
> come up with something, but it's rare)
>
> (In UUF we should automatically handle this kind of thing)
>
> [1]
> http://docs.oracle.com/javaee/5/api/javax/servlet/ServletRequest.html#getServerName()
>
> On Fri, Jun 24, 2016 at 8:33 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Since there is no transport level information at C5 kernel level, we
>> can't add this to kernel. The relevant transport implementation should
>> provide such information IMO. For example, netty based http implementation
>> can provide information about the IP or Ports when server is ready serve
>> requests.
>>
>> On Fri, Jun 24, 2016 at 2:09 PM, Rasika Perera  wrote:
>>
>>> Hi All,
>>>
>>> How do we retrieve $subject that the server has binded? In 4.4.x it was
>>> available via java system property "bind.address" ?
>>>
>>> There are use-cases such as in IoTS we need to provide server ip address
>>> for downloading device agents. "localhost" would not work when the invoker
>>> is remote.
>>>
>>> ​Thanks​
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.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] [C5] How do we get IP address of the Carbon Server?

[Manuranga Perera]

Having server IP/Hostname in configuration/kernel is a mistake we have done
in C4. This makes it harder to setup load balances since we have to do more
configuration. It's also confusing when same server is in multiple networks
and therefore have multiple IPs. Best thing we should do is to use the HTTP
Host header to get the server hostname. This is what J2EE returns by
default [1] and it will work with loadbancers without extra config from our
side when host is forwarded.

I think we should recommend this approach for all C5 server IP scenarios.
(there will be edge cases when there are no HTTP requests, which we have to
come up with something, but it's rare)

(In UUF we should automatically handle this kind of thing)

[1]
http://docs.oracle.com/javaee/5/api/javax/servlet/ServletRequest.html#getServerName()

On Fri, Jun 24, 2016 at 8:33 AM, Kishanthan Thangarajah  wrote:

> Since there is no transport level information at C5 kernel level, we can't
> add this to kernel. The relevant transport implementation should provide
> such information IMO. For example, netty based http implementation can
> provide information about the IP or Ports when server is ready serve
> requests.
>
> On Fri, Jun 24, 2016 at 2:09 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>> How do we retrieve $subject that the server has binded? In 4.4.x it was
>> available via java system property "bind.address" ?
>>
>> There are use-cases such as in IoTS we need to provide server ip address
>> for downloading device agents. "localhost" would not work when the invoker
>> is remote.
>>
>> ​Thanks​
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM 2.0] Revoked access and revoked refresh tokens returning with http response header

[Nuwan Dias]

Any idea why its bad? That jira doesn't clearly say why. It won't return
anything in those headers if someone sends invalid values. So I'm wondering
how it can be bad.

The reason we use these return values is to clear the gateway cache. When
the key manager refreshes a token, the Gateway doesn't know which access
token was revoked. So it has no knowledge of which tokens to clear from its
cache. Any suggestions on alternative approaches of clearing the cache in
those scenarios?

Thanks,
NuwanD.

On Fri, Jun 24, 2016 at 6:25 PM, Aparna Karunarathna 
wrote:

> Hi Nuwan,
>
> Kavitha was asking, RevokedAccessToken & RevokedRefreshToken are getting
> in the header because it was requested requirement by APIM team [1] ? Jira
> [1] says it's a bad implementation. So are we going to fix[2] ?
>
> [1] https://wso2.org/jira/browse/IDENTITY-4112
> [2] https://wso2.org/jira/browse/APIMANAGER-5098
>
> Regards,
> Aparna.
>
> On Fri, Jun 24, 2016 at 5:44 PM, Nuwan Dias  wrote:
>
>> Can you explain what the issue here is? You have raised the ticket as a
>> bug but you've forgotten to describe what the bug actually is?
>>
>> On Fri, Jun 24, 2016 at 5:39 PM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi apim team,
>>> A jira has been raised to track this issue in [1]
>>>
>>> [1] https://wso2.org/jira/browse/APIMANAGER-5098
>>>
>>> Thanks,
>>>
>>> On Thu, Jun 23, 2016 at 6:31 PM, Kavitha Subramaniyam 
>>> wrote:
>>>
 Hi team,
 Highly appreciate your update on this.

 Thanks,

 On Wed, Jun 22, 2016 at 2:28 PM, Kavitha Subramaniyam  wrote:

> Hi team,
>
> I observed that both revoked access and revoked refresh tokens were
> returning in http response header [3].
> setup : IS as KM
>  - apim 2.0.0 17th nightly build
>  - IS 5.2.0 19th build
>  - Token encryption enabled
>
> Could you please confirm that this behavior is not resolved purposely
> in apim 2.0.0 due to the reasons discussed in mail thread [1], or it has
> been solved?
> Find an identity jira was raised for IS issue [2]
>
> [1] Revoked Access Token and Revoked Refresh Token returned back in
> token revoke endpoint response
>
> [2] https://wso2.org/jira/browse/IDENTITY-4112
>
> [3]
>
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1
> 200 OK
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> AuthorizedUser: WSO2.ORG/admin@carbon.super
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> Cache-Control: no-store
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date:
> Wed, 22 Jun 2016 08:39:00 GMT
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma:
> no-cache
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> RevokedRefreshToken:
> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> Content-Type: text/html
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
> Content-Length: 0
> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server:
> WSO2 Carbon Server
> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1
> 200 OK
> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
> AuthorizedUser: WSO2.ORG/admin@carbon.super
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
> RevokedRefreshToken:
> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
> Content-Type: text/html
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma:
> no-cache
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
> Cache-Control: no-store
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date:
> Wed, 22 Jun 2016 08:39:00 GMT
> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
> Transfer-Encoding: chunked
>
>
>
>
>
> Thanks,
>
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



 --
 Kavitha.S
 *Software Engineer -QA*
 Mobile : +94 (0) 771538811 

Re: [Dev] [APIM 2.0] Revoked access and revoked refresh tokens returning with http response header

[Aparna Karunarathna]

Hi Nuwan,

Kavitha was asking, RevokedAccessToken & RevokedRefreshToken are getting in
the header because it was requested requirement by APIM team [1] ? Jira [1]
says it's a bad implementation. So are we going to fix[2] ?

[1] https://wso2.org/jira/browse/IDENTITY-4112
[2] https://wso2.org/jira/browse/APIMANAGER-5098

Regards,
Aparna.

On Fri, Jun 24, 2016 at 5:44 PM, Nuwan Dias  wrote:

> Can you explain what the issue here is? You have raised the ticket as a
> bug but you've forgotten to describe what the bug actually is?
>
> On Fri, Jun 24, 2016 at 5:39 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi apim team,
>> A jira has been raised to track this issue in [1]
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-5098
>>
>> Thanks,
>>
>> On Thu, Jun 23, 2016 at 6:31 PM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi team,
>>> Highly appreciate your update on this.
>>>
>>> Thanks,
>>>
>>> On Wed, Jun 22, 2016 at 2:28 PM, Kavitha Subramaniyam 
>>> wrote:
>>>
 Hi team,

 I observed that both revoked access and revoked refresh tokens were
 returning in http response header [3].
 setup : IS as KM
  - apim 2.0.0 17th nightly build
  - IS 5.2.0 19th build
  - Token encryption enabled

 Could you please confirm that this behavior is not resolved purposely
 in apim 2.0.0 due to the reasons discussed in mail thread [1], or it has
 been solved?
 Find an identity jira was raised for IS issue [2]

 [1] Revoked Access Token and Revoked Refresh Token returned back in
 token revoke endpoint response

 [2] https://wso2.org/jira/browse/IDENTITY-4112

 [3]

 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1
 200 OK
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 AuthorizedUser: WSO2.ORG/admin@carbon.super
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 Cache-Control: no-store
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date:
 Wed, 22 Jun 2016 08:39:00 GMT
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma:
 no-cache
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 RevokedRefreshToken:
 h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 Content-Type: text/html
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
 Content-Length: 0
 [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server:
 WSO2 Carbon Server
 [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1
 200 OK
 [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
 RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
 [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
 AuthorizedUser: WSO2.ORG/admin@carbon.super
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
 RevokedRefreshToken:
 h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
 Content-Type: text/html
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma:
 no-cache
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
 Cache-Control: no-store
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date:
 Wed, 22 Jun 2016 08:39:00 GMT
 [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
 Transfer-Encoding: chunked





 Thanks,

 --
 Kavitha.S
 *Software Engineer -QA*
 Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
 kavi...@wso2.com 

>>>
>>>
>>>
>>> --
>>> Kavitha.S
>>> *Software Engineer -QA*
>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>>> kavi...@wso2.com 
>>>
>>
>>
>>
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Regards,*

*Aparna Karunarathna.*


*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [C5] How do we get IP address of the Carbon Server?

[Kishanthan Thangarajah]

Since there is no transport level information at C5 kernel level, we can't
add this to kernel. The relevant transport implementation should provide
such information IMO. For example, netty based http implementation can
provide information about the IP or Ports when server is ready serve
requests.

On Fri, Jun 24, 2016 at 2:09 PM, Rasika Perera  wrote:

> Hi All,
>
> How do we retrieve $subject that the server has binded? In 4.4.x it was
> available via java system property "bind.address" ?
>
> There are use-cases such as in IoTS we need to provide server ip address
> for downloading device agents. "localhost" would not work when the invoker
> is remote.
>
> ​Thanks​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
*Kishanthan Thangarajah*
Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM 2.0] Revoked access and revoked refresh tokens returning with http response header

[Nuwan Dias]

Can you explain what the issue here is? You have raised the ticket as a bug
but you've forgotten to describe what the bug actually is?

On Fri, Jun 24, 2016 at 5:39 PM, Kavitha Subramaniyam 
wrote:

> Hi apim team,
> A jira has been raised to track this issue in [1]
>
> [1] https://wso2.org/jira/browse/APIMANAGER-5098
>
> Thanks,
>
> On Thu, Jun 23, 2016 at 6:31 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi team,
>> Highly appreciate your update on this.
>>
>> Thanks,
>>
>> On Wed, Jun 22, 2016 at 2:28 PM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi team,
>>>
>>> I observed that both revoked access and revoked refresh tokens were
>>> returning in http response header [3].
>>> setup : IS as KM
>>>  - apim 2.0.0 17th nightly build
>>>  - IS 5.2.0 19th build
>>>  - Token encryption enabled
>>>
>>> Could you please confirm that this behavior is not resolved purposely in
>>> apim 2.0.0 due to the reasons discussed in mail thread [1], or it has been
>>> solved?
>>> Find an identity jira was raised for IS issue [2]
>>>
>>> [1] Revoked Access Token and Revoked Refresh Token returned back in
>>> token revoke endpoint response
>>>
>>> [2] https://wso2.org/jira/browse/IDENTITY-4112
>>>
>>> [3]
>>>
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1
>>> 200 OK
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> AuthorizedUser: WSO2.ORG/admin@carbon.super
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> Cache-Control: no-store
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date: Wed,
>>> 22 Jun 2016 08:39:00 GMT
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma:
>>> no-cache
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> RevokedRefreshToken:
>>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> Content-Type: text/html
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>>> Content-Length: 0
>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server:
>>> WSO2 Carbon Server
>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1
>>> 200 OK
>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
>>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
>>> AuthorizedUser: WSO2.ORG/admin@carbon.super
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>>> RevokedRefreshToken:
>>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>>> Content-Type: text/html
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma:
>>> no-cache
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>>> Cache-Control: no-store
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date: Wed,
>>> 22 Jun 2016 08:39:00 GMT
>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>>> Transfer-Encoding: chunked
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>> --
>>> Kavitha.S
>>> *Software Engineer -QA*
>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>>> kavi...@wso2.com 
>>>
>>
>>
>>
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



-- 
Nuwan Dias

Technical Lead - 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.0] Revoked access and revoked refresh tokens returning with http response header

[Kavitha Subramaniyam]

Hi apim team,
A jira has been raised to track this issue in [1]

[1] https://wso2.org/jira/browse/APIMANAGER-5098

Thanks,

On Thu, Jun 23, 2016 at 6:31 PM, Kavitha Subramaniyam 
wrote:

> Hi team,
> Highly appreciate your update on this.
>
> Thanks,
>
> On Wed, Jun 22, 2016 at 2:28 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi team,
>>
>> I observed that both revoked access and revoked refresh tokens were
>> returning in http response header [3].
>> setup : IS as KM
>>  - apim 2.0.0 17th nightly build
>>  - IS 5.2.0 19th build
>>  - Token encryption enabled
>>
>> Could you please confirm that this behavior is not resolved purposely in
>> apim 2.0.0 due to the reasons discussed in mail thread [1], or it has been
>> solved?
>> Find an identity jira was raised for IS issue [2]
>>
>> [1] Revoked Access Token and Revoked Refresh Token returned back in token
>> revoke endpoint response
>>
>> [2] https://wso2.org/jira/browse/IDENTITY-4112
>>
>> [3]
>>
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1
>> 200 OK
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> AuthorizedUser: WSO2.ORG/admin@carbon.super
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> Cache-Control: no-store
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date: Wed,
>> 22 Jun 2016 08:39:00 GMT
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma:
>> no-cache
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> RevokedRefreshToken:
>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> Content-Type: text/html
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
>> Content-Length: 0
>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server:
>> WSO2 Carbon Server
>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1
>> 200 OK
>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
>> AuthorizedUser: WSO2.ORG/admin@carbon.super
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>> RevokedRefreshToken:
>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>> Content-Type: text/html
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma:
>> no-cache
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>> Cache-Control: no-store
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date: Wed,
>> 22 Jun 2016 08:39:00 GMT
>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
>> Transfer-Encoding: chunked
>>
>>
>>
>>
>>
>> Thanks,
>>
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Kasun Bandara]

Hi Dinuhsa,

We will be releasing the required repositories on top of the kernel 4.4.6
release next week for the IS 5.3.0-M3. Along with that we have decided to
release a component release for release-productis-5.2.0 branch as well,
which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)

Thanks,
Kasun.

On Fri, Jun 24, 2016 at 12:44 PM, Dinusha Senanayaka 
wrote:

> Hi Kasun,
>
> Please find the identity features used in AppM.
>
>
> org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.core.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.provider.server.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.user.registration.server.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.server.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.server.feature:${carbon.identity.oauth.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.server.feature:${carbon.identity.oauth.version}
>
> org.wso2.carbon:org.wso2.carbon.identity.oauth.common.feature:${identity.oauth.common.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.basicauth.server.feature:${carbon.identity.version}
> 
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.samlsso.server.feature:${carbon.identity.version}
> 
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.claim.mgt.feature:${carbon.identity.version}
> 
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.thrift.authentication.feature:${carbon.identity.version}
> 
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.server.feature:${carbon.identity.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authentication.framework.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.feature:${carbon.identity.version}
> 
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.saml2.sso.feature:${carbon.identity-inbound-auth-saml2.version}
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.mgt.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.xacml.feature:${carbon.identity.version}
>
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.openid.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.oidc.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.passive.sts.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.iwa.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.requestpath.basicauth.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.requestpath.oauth.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.yahoo.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.google.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.live.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.facebook.server.feature:${carbon.identity.version}
>
> 
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.connector.google.server.feature:${carbon.identity.version}
>
> org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature:${carbon.identity.version}
>
> 

Re: [Dev] DASHBOARD: Bar chart isn't displaying results in expected manner

[Tharik Kanaka]

Hi Aneela,

Apparently "logins" attribute is a String type. For bar charts the y axis
needs to be linear scale that means you need to have an attribute type such
as int, long, double and float.

Regards,

On Fri, Jun 24, 2016 at 11:57 AM, Aneela Safdar  wrote:

> Hi all,
>
>
> I am using bar chart to display results outputted from execution plan.
>
> My output stream has results in form:
>
>tslogins
> 1.2016-05-08 08:591
> 2.2016-05-08 09:005
> 3.2016-05-08 09:011
> 4.2016-05-08 09:135
> 5.2016-05-08 09:142
>
>
> I set x-axis as ts and y-axis as logins
>
> Following are the problems I am dealing with:
>
> 1.y-axis values are in ascending order from top to bottom and I want
> vice versa.
> 2.Bars are not being displayed at all on graph. It just looks like a
> blank graph having intervals marked on it.
> Below is aforementioned chart.
>
> [image: Inline image]
> Thanks,
>
> Regards, Aneela Safdar
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharik Kanaka*

WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

Email: tha...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Uvindra Dias Jayasinha]

Problem is the issue is intermittent so its difficult to verify but I will
test the fix out and send a PR

On 24 June 2016 at 13:52, Chanaka Fernando  wrote:

> Hi Uvindra,
>
> Could you please verify the fix and send us a PR so that we can merge it?
>
> On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Hi All,
>>
>> The original issue encountered in [1] was fixed via the resolution of [2].
>>
>> But now this has been reopened and in this case the same issue has got
>> exposed, but on this occasion the call stack is different. This is
>> happening when setting the tenant info at [3]. So we need to apply the same
>> fix that was done in resolving [2] to the WSO2Registry class when setting
>> the tenant info.
>>
>> Can we get this fixed?
>>
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4202
>> [2] https://wso2.org/jira/browse/ESBJAVA-4333
>> [3]
>> https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 
Regards,
Uvindra

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

[Dev] [C5] How do we get IP address of the Carbon Server?

[Rasika Perera]

Hi All,

How do we retrieve $subject that the server has binded? In 4.4.x it was
available via java system property "bind.address" ?

There are use-cases such as in IoTS we need to provide server ip address
for downloading device agents. "localhost" would not work when the invoker
is remote.

​Thanks​

-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kernel] Why don't we support "##" on web app names?

[Thilini Cooray]

Hi Kalpa,

Thanks for pointing it out.

AFAIU what we should do is searching for invalid # sequences such as "###".
Because a WAR names such as api#v1.0##1.war is accepted by our underlying
Tomcat and that approach is highly helpful when we want to indicate the
correct version number of a webapp without effecting the context.

WDYT?

On Fri, Jun 24, 2016 at 1:33 PM, Kalpa Welivitigoda  wrote:

> Hi Thilini,
>
> I guess it is related to https://wso2.org/jira/browse/WSAS-1350
>
> On Fri, Jun 24, 2016 at 1:01 PM, Thilini Cooray  wrote:
>
>> Hi team,
>>
>> Why have we specifically captured web app names with version separator
>> ("##") as not supported [1] ?
>>
>> AFAIU Apache Tomcat supports this property [2].
>> This property is useful when we want to provide the versioning on the WAR
>> name but do not need to change the web app context (Ex : patch release of a
>> webapp). Because changing web app context on every patch release of an API
>> will highly affect its clients.
>>
>> [1]
>> https://github.com/wso2/carbon-deployment/blob/4.6.x/components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/AbstractWebappDeployer.java#L402
>> [2]
>> https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Defining_a_context
>>
>> Thanks.
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>



-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Possible bottleneck in the updatePermissionTree() method of user.core.authorization.PermissionTree class

[Chalitha Kulathunga]

+ IS team members

On Fri, Jun 24, 2016 at 1:37 PM, Chalitha Kulathunga 
wrote:

> Hi kernal team,
>
> When multiple threads access updatePermissionTree() method for the first
> time, they all will end up in the else block. Those threads will call the
> updatePermissionTreeFromDB() method one by one. Seems like this is creating
> a bottleneck in the execution flow.
>
> void updatePermissionTree() throws UserStoreException {
> PermissionTreeCacheKey cacheKey = new 
> PermissionTreeCacheKey(cacheIdentifier, tenantId);
> GhostResource cacheEntry = (GhostResource) 
> permissionCache.get(cacheKey);
> if (permissionCache.containsKey(cacheKey)) {
> if (cacheEntry.getResource() == null) {
> synchronized (this) {
> cacheEntry = (GhostResource) 
> permissionCache.get(cacheKey);
> if (cacheEntry.getResource() == null) {
> updatePermissionTreeFromDB();
> cacheEntry.setResource(root);
> if (log.isDebugEnabled()) {
> log.debug("Set resource to true");
> }
> }
> }
> }
> } else {
> synchronized (this) {
> updatePermissionTreeFromDB();
> cacheKey = new PermissionTreeCacheKey(cacheIdentifier, tenantId);
> cacheEntry = new GhostResource(root);
> permissionCache.put(cacheKey, cacheEntry);
> if (log.isDebugEnabled()) {
> log.debug("Loaded from database");
> }
> }
> }
> }
>
>
> Can this be modified as follows to avoid the above mentioned issue?
>
> void updatePermissionTree() throws UserStoreException {
> PermissionTreeCacheKey cacheKey = new 
> PermissionTreeCacheKey(cacheIdentifier, tenantId);
> GhostResource cacheEntry = (GhostResource) 
> permissionCache.get(cacheKey);
> if (cacheEntry != null && cacheEntry.getResource() != null) {
> return;
> }
> synchronized (this) {
> if (cacheEntry != null && cacheEntry.getResource() != null) {
> return;
> }
> if (cacheEntry == null) {
> cacheEntry = new GhostResource(null);
> permissionCache.put(cacheKey, cacheEntry);
> }
> if (cacheEntry.getResource() == null) {
> updatePermissionTreeFromDB();
> cacheEntry.setResource(root);
> if (log.isDebugEnabled()) {
> log.debug("Resource Loaded from database for cachekey: " + 
> cacheEntry);
> }
> }
> }
> }
>
>
> Thanks,
> Chalitha
>
>
> --
> *Chalitha Sanyuja Kulathunga*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
>



-- 
*Chalitha Sanyuja Kulathunga*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Chanaka Fernando]

Hi Uvindra,

Could you please verify the fix and send us a PR so that we can merge it?

On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha 
wrote:

> Hi All,
>
> The original issue encountered in [1] was fixed via the resolution of [2].
>
> But now this has been reopened and in this case the same issue has got
> exposed, but on this occasion the call stack is different. This is
> happening when setting the tenant info at [3]. So we need to apply the same
> fix that was done in resolving [2] to the WSO2Registry class when setting
> the tenant info.
>
> Can we get this fixed?
>
>
> [1] https://wso2.org/jira/browse/APIMANAGER-4202
> [2] https://wso2.org/jira/browse/ESBJAVA-4333
> [3]
> https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Possible bottleneck in the updatePermissionTree() method of user.core.authorization.PermissionTree class

[Chalitha Kulathunga]

Hi kernal team,

When multiple threads access updatePermissionTree() method for the first
time, they all will end up in the else block. Those threads will call the
updatePermissionTreeFromDB() method one by one. Seems like this is creating
a bottleneck in the execution flow.

void updatePermissionTree() throws UserStoreException {
PermissionTreeCacheKey cacheKey = new
PermissionTreeCacheKey(cacheIdentifier, tenantId);
GhostResource cacheEntry = (GhostResource)
permissionCache.get(cacheKey);
if (permissionCache.containsKey(cacheKey)) {
if (cacheEntry.getResource() == null) {
synchronized (this) {
cacheEntry = (GhostResource)
permissionCache.get(cacheKey);
if (cacheEntry.getResource() == null) {
updatePermissionTreeFromDB();
cacheEntry.setResource(root);
if (log.isDebugEnabled()) {
log.debug("Set resource to true");
}
}
}
}
} else {
synchronized (this) {
updatePermissionTreeFromDB();
cacheKey = new PermissionTreeCacheKey(cacheIdentifier, tenantId);
cacheEntry = new GhostResource(root);
permissionCache.put(cacheKey, cacheEntry);
if (log.isDebugEnabled()) {
log.debug("Loaded from database");
}
}
}
}


Can this be modified as follows to avoid the above mentioned issue?

void updatePermissionTree() throws UserStoreException {
PermissionTreeCacheKey cacheKey = new
PermissionTreeCacheKey(cacheIdentifier, tenantId);
GhostResource cacheEntry = (GhostResource)
permissionCache.get(cacheKey);
if (cacheEntry != null && cacheEntry.getResource() != null) {
return;
}
synchronized (this) {
if (cacheEntry != null && cacheEntry.getResource() != null) {
return;
}
if (cacheEntry == null) {
cacheEntry = new GhostResource(null);
permissionCache.put(cacheKey, cacheEntry);
}
if (cacheEntry.getResource() == null) {
updatePermissionTreeFromDB();
cacheEntry.setResource(root);
if (log.isDebugEnabled()) {
log.debug("Resource Loaded from database for cachekey:
" + cacheEntry);
}
}
}
}


Thanks,
Chalitha


-- 
*Chalitha Sanyuja Kulathunga*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kernel] Why don't we support "##" on web app names?

[Kalpa Welivitigoda]

Hi Thilini,

I guess it is related to https://wso2.org/jira/browse/WSAS-1350

On Fri, Jun 24, 2016 at 1:01 PM, Thilini Cooray  wrote:

> Hi team,
>
> Why have we specifically captured web app names with version separator
> ("##") as not supported [1] ?
>
> AFAIU Apache Tomcat supports this property [2].
> This property is useful when we want to provide the versioning on the WAR
> name but do not need to change the web app context (Ex : patch release of a
> webapp). Because changing web app context on every patch release of an API
> will highly affect its clients.
>
> [1]
> https://github.com/wso2/carbon-deployment/blob/4.6.x/components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/AbstractWebappDeployer.java#L402
> [2]
> https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Defining_a_context
>
> Thanks.
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Best Regards,

Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Uvindra Dias Jayasinha]

Hi All,

The original issue encountered in [1] was fixed via the resolution of [2].

But now this has been reopened and in this case the same issue has got
exposed, but on this occasion the call stack is different. This is
happening when setting the tenant info at [3]. So we need to apply the same
fix that was done in resolving [2] to the WSO2Registry class when setting
the tenant info.

Can we get this fixed?


[1] https://wso2.org/jira/browse/APIMANAGER-4202
[2] https://wso2.org/jira/browse/ESBJAVA-4333
[3]
https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747


-- 
Regards,
Uvindra

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

[Dev] [ESB][4.9.0] Error is starting worker node in clustered setup.

[Anuruddha Liyanarachchi]

Hi,

I am observing the same error[2] reported in JIRA [1] with oracle
jdk-7u80.  Is this bug fixed in the released 4.9.0 pack ?


[1] https://wso2.org/jira/browse/ESBJAVA-4169
[2]
TID: [-1234] [] [2016-06-24 06:46:36,828]  INFO
{org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -  Task service
starting in CLUSTERED mode...
{org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl}
TID: [-1234] [] [2016-06-24 06:46:36,873] ERROR
{org.wso2.carbon.mediation.ntask.NTaskTaskManager} -  Cannot initialize
task manager. Error: null {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
java.lang.UnsupportedOperationException
at
com.hazelcast.util.QueryResultSet$QueryResultIterator.remove(QueryResultSet.java:188)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator.checkAndRemoveExpiredMembers(ClusterGroupCommunicator.java:118)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator.refreshMembers(ClusterGroupCommunicator.java:94)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator.(ClusterGroupCommunicator.java:87)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator.getInstance(ClusterGroupCommunicator.java:71)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.processClusteredTaskTypeRegistration(TaskServiceImpl.java:166)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.registerTaskType(TaskServiceImpl.java:156)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:343)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:365)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:343)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)

[Dev] [Kernel] Why don't we support "##" on web app names?

[Thilini Cooray]

Hi team,

Why have we specifically captured web app names with version separator
("##") as not supported [1] ?

AFAIU Apache Tomcat supports this property [2].
This property is useful when we want to provide the versioning on the WAR
name but do not need to change the web app context (Ex : patch release of a
webapp). Because changing web app context on every patch release of an API
will highly affect its clients.

[1]
https://github.com/wso2/carbon-deployment/blob/4.6.x/components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/AbstractWebappDeployer.java#L402
[2]
https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Defining_a_context

Thanks.

-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Hi Kasun,

Please find the identity features used in AppM.

org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.core.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.provider.server.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.user.registration.server.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.server.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.server.feature:${carbon.identity.oauth.version}
org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.server.feature:${carbon.identity.oauth.version}
org.wso2.carbon:org.wso2.carbon.identity.oauth.common.feature:${identity.oauth.common.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.basicauth.server.feature:${carbon.identity.version}



org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.samlsso.server.feature:${carbon.identity.version}



org.wso2.carbon.identity:org.wso2.carbon.claim.mgt.feature:${carbon.identity.version}



org.wso2.carbon.identity:org.wso2.carbon.identity.thrift.authentication.feature:${carbon.identity.version}



org.wso2.carbon.identity:org.wso2.carbon.user.mgt.server.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.application.authentication.framework.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.feature:${carbon.identity.version}



org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.saml2.sso.feature:${carbon.identity-inbound-auth-saml2.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.mgt.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.xacml.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.openid.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.oidc.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.passive.sts.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.iwa.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.requestpath.basicauth.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.requestpath.oauth.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.yahoo.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.google.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.live.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.facebook.server.feature:${carbon.identity.version}


org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.connector.google.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.connector.spml.server.feature:${carbon.identity.version}

org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.iwa.feature:${carbon.identity.version}
org.wso2.carbon.identity:org.wso2.carbon.identity.notification.mgt.feature:${carbon.identity.version}

Regards,
Dinusha.

On Fri, Jun 24, 2016 at 12:31 PM, Kasun Bandara  wrote:

> Hi Dinusha,
>
> Can you please specify the identity features you are using ?. opensaml
> orbit bundles with other components such as identity-agent-sso [1] as well.
> Hence wanted to know the list of identity features used by AppM for a
> repository release.
>
>

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Kasun Bandara]

Hi Dinusha,

Can you please specify the identity features you are using ?. opensaml
orbit bundles with other components such as identity-agent-sso [1] as well.
Hence wanted to know the list of identity features used by AppM for a
repository release.


[1]
https://github.com/wso2-extensions/identity-agent-sso/blob/master/features/org.wso2.carbon.identity.sso.agent.server.feature/pom.xml

Thanks,
Kasun.

On Fri, Jun 24, 2016 at 12:21 PM, Dinusha Senanayaka 
wrote:

>
> We are using several identity features. "
> org.wso2.carbon.identity.xacml.feature"  is causing the issue it seems.
>
> On Fri, Jun 24, 2016 at 12:12 PM, Kasun Bandara  wrote:
>
>> Hi Dinusha,
>>
>> Can you please specify the relevant identity features you are using ?.
>> IS-5.2.0 will be based on kernel 4.4.6. We are planning the component
>> release along with the IS 5.2.0 GA release .
>>
>> Thanks,
>> Kasun.
>>
>> On Fri, Jun 24, 2016 at 11:44 AM, Dinusha Senanayaka 
>> wrote:
>>
>>> Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do
>>> this today ? I thought IS-5.2.0 is already based on kernel 4.4.6.
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara  wrote:
>>>
 Hi Dinusha,

 Yes. we will be fixing this issue with once we upgrade the kernel
 version to 4.4.6. The opensaml version of the feature you have mentioned
 will be upgraded to opensaml-2.6.4.wso2v3. The corresponding repository
 release will be done along with the IS 5.2.0 GA release.

 Thanks,
 Kasun.

 On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka 
 wrote:

> Hi Kasun,
>
> Non of the appmgt features are bundling opensaml. It's comes to AppM
> product through identity features. Seems through the
> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
> this.
>
> [1]
> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
> [2]
> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>
> Regards,
> Dinusha.
>
> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara 
> wrote:
>
>> Hi Sajith,
>>
>> This issue was identified in [1] and we have fixed the issue with
>> [2]. This issue can be resolve by using the new opensaml orbit. We are
>> planning to release identity repositories (~50) on top of kernel 4.4.6,
>> after fixing the security vulnerabilities as stated in [3]. You can refer
>> [4] to get the latest updates on IS 5.2.0 GA release.
>>
>> Thanks,
>> Kasun.
>>
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>
>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
>> orbit
>>
>> [3] [Engineering] Security Hackathon to start from tomorrow
>>
>> [4] [Engineering] IS 5.2.0 GA Update
>>
>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana <
>> saji...@wso2.com> wrote:
>>
>>> Hi IS Team,
>>>
>>> AppM has been updated to the carbon kernel 4.4.6, and also I updated
>>> the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
>>> jaggery app I got below exception[1].
>>>
>>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't
>>> properly imported the required bouncy castle version which is version 
>>> 1.52.0.wso2v1(packed
>>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>>
>>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
>>> the git repo with the required bouncy castle version[3]. So when
>>> you are planning to release the IS version, which bundles the
>>> opensaml_2.6.4.wso2v3 into a feature? Currently, we are blocking
>>> due to this issue.
>>>
>>>
>>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>>> threw exception [Servlet execution threw an exception] with root cause
>>> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
>>> cannot be found by opensaml_2.6.4.wso2v2
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>> at
>>> 

[Dev] JSON Path support for Mediators from Developer Studio

[Sohani Weerasinghe]

Hi All,

As per discussed at [1], since json path support was not facilitated in
Call- Template and Validate mediators, I have made changes to support json
path for those two mediators from DevS side.

Since json path was already supported in switch and filter mediators, AFAIK
DevS is now compatible with ESB in supporting the json path. Appreciate
your input if any improvements needs to be done.

[1] Facilitating the JSON path support for ESB mediators in DevS

Thanks,
Sohani
Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

We are using several identity features. "
org.wso2.carbon.identity.xacml.feature"  is causing the issue it seems.

On Fri, Jun 24, 2016 at 12:12 PM, Kasun Bandara  wrote:

> Hi Dinusha,
>
> Can you please specify the relevant identity features you are using ?.
> IS-5.2.0 will be based on kernel 4.4.6. We are planning the component
> release along with the IS 5.2.0 GA release .
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 11:44 AM, Dinusha Senanayaka 
> wrote:
>
>> Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do
>> this today ? I thought IS-5.2.0 is already based on kernel 4.4.6.
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara  wrote:
>>
>>> Hi Dinusha,
>>>
>>> Yes. we will be fixing this issue with once we upgrade the kernel
>>> version to 4.4.6. The opensaml version of the feature you have mentioned
>>> will be upgraded to opensaml-2.6.4.wso2v3. The corresponding repository
>>> release will be done along with the IS 5.2.0 GA release.
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka 
>>> wrote:
>>>
 Hi Kasun,

 Non of the appmgt features are bundling opensaml. It's comes to AppM
 product through identity features. Seems through the
 org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
 opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
 this.

 [1]
 https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
 [2]
 https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476

 Regards,
 Dinusha.

 On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara 
 wrote:

> Hi Sajith,
>
> This issue was identified in [1] and we have fixed the issue with [2].
> This issue can be resolve by using the new opensaml orbit. We are planning
> to release identity repositories (~50) on top of kernel 4.4.6, after 
> fixing
> the security vulnerabilities as stated in [3]. You can refer [4] to get 
> the
> latest updates on IS 5.2.0 GA release.
>
> Thanks,
> Kasun.
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-4680
>
> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
> orbit
>
> [3] [Engineering] Security Hackathon to start from tomorrow
>
> [4] [Engineering] IS 5.2.0 GA Update
>
> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana <
> saji...@wso2.com> wrote:
>
>> Hi IS Team,
>>
>> AppM has been updated to the carbon kernel 4.4.6, and also I updated
>> the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
>> jaggery app I got below exception[1].
>>
>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't
>> properly imported the required bouncy castle version which is version 
>> 1.52.0.wso2v1(packed
>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>
>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
>> the git repo with the required bouncy castle version[3]. So when you
>> are planning to release the IS version, which bundles the opensaml_2.
>> 6.4.wso2v3 into a feature? Currently, we are blocking due to this
>> issue.
>>
>>
>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>> threw exception [Servlet execution threw an exception] with root cause
>> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
>> cannot be found by opensaml_2.6.4.wso2v2
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>> at
>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
>> at
>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
>> at
>> org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
>> at
>> org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
>> at
>> org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor.process(SPInitSSOAuthnRequestProcessor.java:160)
>> at
>> 

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Kasun Bandara]

Hi Dinusha,

Can you please specify the relevant identity features you are using ?.
IS-5.2.0 will be based on kernel 4.4.6. We are planning the component
release along with the IS 5.2.0 GA release .

Thanks,
Kasun.

On Fri, Jun 24, 2016 at 11:44 AM, Dinusha Senanayaka 
wrote:

> Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do
> this today ? I thought IS-5.2.0 is already based on kernel 4.4.6.
>
> Regards,
> Dinusha.
>
> On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara  wrote:
>
>> Hi Dinusha,
>>
>> Yes. we will be fixing this issue with once we upgrade the kernel version
>> to 4.4.6. The opensaml version of the feature you have mentioned will be
>> upgraded to opensaml-2.6.4.wso2v3. The corresponding repository release
>> will be done along with the IS 5.2.0 GA release.
>>
>> Thanks,
>> Kasun.
>>
>> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka 
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> Non of the appmgt features are bundling opensaml. It's comes to AppM
>>> product through identity features. Seems through the
>>> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
>>> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
>>> this.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
>>> [2]
>>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara  wrote:
>>>
 Hi Sajith,

 This issue was identified in [1] and we have fixed the issue with [2].
 This issue can be resolve by using the new opensaml orbit. We are planning
 to release identity repositories (~50) on top of kernel 4.4.6, after fixing
 the security vulnerabilities as stated in [3]. You can refer [4] to get the
 latest updates on IS 5.2.0 GA release.

 Thanks,
 Kasun.


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

 [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
 orbit

 [3] [Engineering] Security Hackathon to start from tomorrow

 [4] [Engineering] IS 5.2.0 GA Update

 On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana  wrote:

> Hi IS Team,
>
> AppM has been updated to the carbon kernel 4.4.6, and also I updated
> the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
> jaggery app I got below exception[1].
>
> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't properly
> imported the required bouncy castle version which is version 
> 1.52.0.wso2v1(packed
> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>
> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
> the git repo with the required bouncy castle version[3]. So when you
> are planning to release the IS version, which bundles the opensaml_2.
> 6.4.wso2v3 into a feature? Currently, we are blocking due to this
> issue.
>
>
> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
> Servlet.service() for servlet [bridgeservlet] in context with path [/]
> threw exception [Servlet execution threw an exception] with root cause
> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
> cannot be found by opensaml_2.6.4.wso2v2
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at
> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
> at
> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
> at
> org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
> at
> org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
> at
> org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor.process(SPInitSSOAuthnRequestProcessor.java:160)
> at
> org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:164)
> at
> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleAuthenticationReponseFromFramework(SAMLSSOProviderServlet.java:702)
> at
> 

Re: [Dev] [UUF] [Clarification] Retrieve data without Postback using serverside JS (Fwd: [UUF] Pagination support in UUF)

[Rasika Perera]

Hi Manu & All,

Small correction. This should be corrected as;

if (env.params
> ​ && (​
> env.params.offset && env.params.limit
> ​)​
> ) {


You can access the same with query params as below. Note that
env.request.queryParams
is an empty-map when there is no query params.

if (env.request.queryParams.offset && env.request.queryParams.limit) {


 env.queryParams && should be removed since we should always have an empty
> map. Otherwise it's easy for developers to get null pointer errors

+1, We should also add empty map for env.params as well.​

Thanks,
Rasika

On Thu, Jun 23, 2016 at 9:34 PM, Manuranga Perera  wrote:

> if (env.queryParams && (env.queryParams.offset && env.queryParams.limit))
>> {
>
>  env.queryParams && should be removed since we should always have an
> empty map. Otherwise it's easy for developers to get null pointer errors
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon-datasources: Supporting Database Properties

[Chanaka Cooray]

Hi all,

I will look into the issue.

Thanks,
Chanaka.

On Fri, Jun 24, 2016 at 11:01 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> We will add this for the next minor release.
>
> @Isuru, you can go ahead with the version range as you mentioned for
> package imports.
>
> On Thu, Jun 23, 2016 at 1:21 PM, Afkham Azeez  wrote:
>
>> Can we get a quick turnaround on this please?
>>
>> On Thu, Jun 23, 2016 at 12:10 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> This regarding CDATASRCS-2 .
>>> I guess that won't be fixed soon. But as I mentioned, this issue is a
>>> blocker for Metrics release. Since we need to release Metrics soon (by next
>>> week), I'll release the Metrics with datasources import range "[1.0.0,
>>> 2.0.0)"
>>>
>>> I hope this issue will be fixed in a Minor release. I also hope the
>>> datasource properties will be supported using the same configuration
>>> elements used in C4. See:
>>> https://github.com/wso2/carbon-metrics/blob/v1.2.1/features/carbon-metrics/org.wso2.carbon.metrics.server.feature/src/main/resources/conf/metrics-datasources.xml#L144-L146
>>>
>>> Please let me know the plan to support datasource properties in C5.
>>>
>>> Thanks!
>>>
>>> Best Regards,
>>>
>>> On Thu, Jun 2, 2016 at 12:25 PM, Isuru Perera  wrote:
>>>
 Hi,

 This is regarding [1]. Supporting database properties is required for
 Carbon Metrics.

 It will be a blocker when someone wants to use Carbon Metrics with
 Oracle database.

 Can we get it fixed soon?

 Thanks!

 Best Regards,

 [1] https://wso2.org/jira/browse/CDATASOURC-2

 --
 Isuru Perera
 Associate Technical Lead | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha
 Contact: +IsuruPereraWSO2
 

>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>> Contact: +IsuruPereraWSO2
>>> 
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Chanaka Cooray
Software Engineer, WSO2 Inc. http://wso2.com
Email: chana...@wso2.com
Mobile: +94713149860
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 IS Analytics v1.0.0-BETA Released

[Damith Wickramasinghe]

Hi Suresh,

Please make sure

tcp://127.0.0.1:7612

 7612 port should corresponds to port offset value of analytics server. Not
IS server in AuthenticationDataPublisher.xml

Regards,
Damith.

On Fri, Jun 24, 2016 at 11:43 AM, Damith Wickramasinghe 
wrote:

> Hi Suresh,
>
> configuration seems to be fine. Can you let us know the steps used to
> publish data to analytic server.
>
>
> Regards,
> Damith.
>
> On Fri, Jun 24, 2016 at 11:20 AM, Suresh Thivanka Rupasinghe <
> sureshthiva...@gmail.com> wrote:
>
>> Hi Damith,
>>
>> yes i checked already. but no data available. here i attached the
>> Identity.xml file and AuthenticationDataPublisher.xml.
>>
>> Regards,
>> Suresh
>>
>> On Fri, Jun 24, 2016 at 11:14 AM, Damith Wickramasinghe > > wrote:
>>
>>> Hi Suresh,
>>>
>>> Can you verify whether data is populated in DB. Please log in to
>>> management console and navigate to data explorer under interactive
>>> analytics . There you will find the tables which used to retrieve data to
>>> dashboard. Check whether data is exist in the table 
>>> AUTHENTICATION-ANALYTICS-STREAM.
>>> You only need to check this table because if data exist in this table then
>>> other tables should also have data.
>>>
>>> Regards,
>>> Damith.
>>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:03 AM, Suresh Thivanka Rupasinghe <
>>> sureshthiva...@gmail.com> wrote:
>>>
 Hi Damith,


 I started both server in CentOS 7 and did all changes mentioned in the
 document. but i cannot see any data on IS analytic server. Any Idea?

 Regards,
 Suresh

 On Sat, Jun 18, 2016 at 10:03 PM, Damith Wickramasinghe <
 dami...@wso2.com> wrote:

> *WSO2 IS Analytics v1.0.0-BETA Released*
>
> We are pleased to announce the beta release of WSO2 IS Analytics
> v1.0.0 [1
> ]
> which is powered by WSO2 Data Analytics Server. IS Analytics can be
> used to monitor authentication related analytics for residence and
> federated authentication scenarios.[2
> ] Please use
> the nightly build IS pack [3
> ]
> which includes necessary instruments to publish data to analytics IS.Your
> feedback is highly appreciated, any bugs or issues can be reported here [
> 4 ].
>
> This release contains the following capabilities:-
>
>1. View Authentication analytics for Federated Identity scenarios
>which includes viewing overall success and failure login attempts and
>authentication attempts views for multiple dimensions of Service 
> Provider,
>Identity Providers,Users,Region and also first time login of service
>Providers.
>2. View Authentication analytics for Federated scenarios which
>includes viewing
>overall success and failure login attempts and authentication
>attempts views for multiple dimensions of service provider, roles , 
> user,
>region and user-stores
>
> Also includes
> Bug
>
>- [ANLYIS-5 ] - Lexical
>error thrown when click on horizontal bar corresponding to the role
>'Internal/Everyone'
>- [ANLYIS-6 ] - isFederated
>attribute value is wrong for federated scenario in authentication 
> stream
>- [ANLYIS-9 ] - Date Range
>Picker date label is not updated when a range is selected from Area 
> chart
>- [ANLYIS-10 ] -
>Auto-complete box contains invalid suggestions lists
>- [ANLYIS-14 ] - UI Issues
>fixed related to Theme and gadets
>
> Improvement
>
>- [ANLYIS-1 ] - Ip to Geo
>map implementation
>- [ANLYIS-3 ] - Provide
>default values to all username,roles etc which will have null or empty
>strings
>
> Task
>
>- [ANLYIS-11 ] - Apply
>Identity Server Theme for Analytics IS
>- [ANLYIS-12 ] - Upgrade
>to latest dashboard version in analytics IS
>
>
> [1]
> https://github.com/wso2/analytics-is/releases/download/v1.0.0-beta/wso2analytics-is-1.0.0-beta.zip
> [2] https://docs.wso2.com/display/IS520/WSO2+IS+Analytics
> [3] 
> *https://svn.wso2.org/repos/wso2/people/mohan/is-5.2.0-with-analytics/beta/
> *
> [4] 

[Dev] DASHBOARD: Bar chart isn't displaying results in expected manner

[Aneela Safdar]

Hi all,

I am using bar chart to display results outputted from execution plan.
My output stream has results in form:
           ts    logins1.
2016-05-08 08:59    12.2016-05-08 09:00 
   53.2016-05-08 09:01    14.
2016-05-08 09:13    55.2016-05-08 09:14 
   2

I set x-axis as ts and y-axis as logins
Following are the problems I am dealing with:
1.y-axis values are in ascending order from top to bottom and I want vice 
versa.2.Bars are not being displayed at all on graph. It just looks like a 
blank graph having intervals marked on it.Below is aforementioned chart.


Thanks,

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

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do this
today ? I thought IS-5.2.0 is already based on kernel 4.4.6.

Regards,
Dinusha.

On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara  wrote:

> Hi Dinusha,
>
> Yes. we will be fixing this issue with once we upgrade the kernel version
> to 4.4.6. The opensaml version of the feature you have mentioned will be
> upgraded to opensaml-2.6.4.wso2v3. The corresponding repository release
> will be done along with the IS 5.2.0 GA release.
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka 
> wrote:
>
>> Hi Kasun,
>>
>> Non of the appmgt features are bundling opensaml. It's comes to AppM
>> product through identity features. Seems through the
>> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
>> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
>> this.
>>
>> [1]
>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
>> [2]
>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara  wrote:
>>
>>> Hi Sajith,
>>>
>>> This issue was identified in [1] and we have fixed the issue with [2].
>>> This issue can be resolve by using the new opensaml orbit. We are planning
>>> to release identity repositories (~50) on top of kernel 4.4.6, after fixing
>>> the security vulnerabilities as stated in [3]. You can refer [4] to get the
>>> latest updates on IS 5.2.0 GA release.
>>>
>>> Thanks,
>>> Kasun.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>>
>>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
>>> orbit
>>>
>>> [3] [Engineering] Security Hackathon to start from tomorrow
>>>
>>> [4] [Engineering] IS 5.2.0 GA Update
>>>
>>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana 
>>> wrote:
>>>
 Hi IS Team,

 AppM has been updated to the carbon kernel 4.4.6, and also I updated
 the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
 jaggery app I got below exception[1].

 The root cause is for this is, opensaml_2.6.4.wso2v2 haven't properly
 imported the required bouncy castle version which is version 
 1.52.0.wso2v1(packed
 with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].

 Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
 the git repo with the required bouncy castle version[3]. So when you
 are planning to release the IS version, which bundles the opensaml_2.
 6.4.wso2v3 into a feature? Currently, we are blocking due to this
 issue.


 [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
 Servlet.service() for servlet [bridgeservlet] in context with path [/]
 threw exception [Servlet execution threw an exception] with root cause
 java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
 cannot be found by opensaml_2.6.4.wso2v2
 at
 org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
 at
 org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
 at
 org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
 at
 org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
 at
 org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
 at
 org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
 at
 org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
 at
 org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
 at
 org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor.process(SPInitSSOAuthnRequestProcessor.java:160)
 at
 org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:164)
 at
 org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleAuthenticationReponseFromFramework(SAMLSSOProviderServlet.java:702)
 at
 org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleRequest(SAMLSSOProviderServlet.java:178)
 at
 org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.doGet(SAMLSSOProviderServlet.java:95)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
 at
 

Re: [Dev] WSO2 IS Analytics v1.0.0-BETA Released

[Damith Wickramasinghe]

Hi Suresh,

configuration seems to be fine. Can you let us know the steps used to
publish data to analytic server.


Regards,
Damith.

On Fri, Jun 24, 2016 at 11:20 AM, Suresh Thivanka Rupasinghe <
sureshthiva...@gmail.com> wrote:

> Hi Damith,
>
> yes i checked already. but no data available. here i attached the
> Identity.xml file and AuthenticationDataPublisher.xml.
>
> Regards,
> Suresh
>
> On Fri, Jun 24, 2016 at 11:14 AM, Damith Wickramasinghe 
> wrote:
>
>> Hi Suresh,
>>
>> Can you verify whether data is populated in DB. Please log in to
>> management console and navigate to data explorer under interactive
>> analytics . There you will find the tables which used to retrieve data to
>> dashboard. Check whether data is exist in the table 
>> AUTHENTICATION-ANALYTICS-STREAM.
>> You only need to check this table because if data exist in this table then
>> other tables should also have data.
>>
>> Regards,
>> Damith.
>>
>>
>>
>> On Fri, Jun 24, 2016 at 10:03 AM, Suresh Thivanka Rupasinghe <
>> sureshthiva...@gmail.com> wrote:
>>
>>> Hi Damith,
>>>
>>>
>>> I started both server in CentOS 7 and did all changes mentioned in the
>>> document. but i cannot see any data on IS analytic server. Any Idea?
>>>
>>> Regards,
>>> Suresh
>>>
>>> On Sat, Jun 18, 2016 at 10:03 PM, Damith Wickramasinghe <
>>> dami...@wso2.com> wrote:
>>>
 *WSO2 IS Analytics v1.0.0-BETA Released*

 We are pleased to announce the beta release of WSO2 IS Analytics
 v1.0.0 [1
 ]
 which is powered by WSO2 Data Analytics Server. IS Analytics can be
 used to monitor authentication related analytics for residence and
 federated authentication scenarios.[2
 ] Please use
 the nightly build IS pack [3
 ]
 which includes necessary instruments to publish data to analytics IS.Your
 feedback is highly appreciated, any bugs or issues can be reported here [
 4 ].

 This release contains the following capabilities:-

1. View Authentication analytics for Federated Identity scenarios
which includes viewing overall success and failure login attempts and
authentication attempts views for multiple dimensions of Service 
 Provider,
Identity Providers,Users,Region and also first time login of service
Providers.
2. View Authentication analytics for Federated scenarios which
includes viewing
overall success and failure login attempts and authentication
attempts views for multiple dimensions of service provider, roles , 
 user,
region and user-stores

 Also includes
 Bug

- [ANLYIS-5 ] - Lexical
error thrown when click on horizontal bar corresponding to the role
'Internal/Everyone'
- [ANLYIS-6 ] - isFederated
attribute value is wrong for federated scenario in authentication stream
- [ANLYIS-9 ] - Date Range
Picker date label is not updated when a range is selected from Area 
 chart
- [ANLYIS-10 ] -
Auto-complete box contains invalid suggestions lists
- [ANLYIS-14 ] - UI Issues
fixed related to Theme and gadets

 Improvement

- [ANLYIS-1 ] - Ip to Geo
map implementation
- [ANLYIS-3 ] - Provide
default values to all username,roles etc which will have null or empty
strings

 Task

- [ANLYIS-11 ] - Apply
Identity Server Theme for Analytics IS
- [ANLYIS-12 ] - Upgrade to
latest dashboard version in analytics IS


 [1]
 https://github.com/wso2/analytics-is/releases/download/v1.0.0-beta/wso2analytics-is-1.0.0-beta.zip
 [2] https://docs.wso2.com/display/IS520/WSO2+IS+Analytics
 [3] 
 *https://svn.wso2.org/repos/wso2/people/mohan/is-5.2.0-with-analytics/beta/
 *
 [4] *https://wso2.org/jira/browse/ANLYIS
 *


 Analytics IS Team


 --
 Software Engineer
 WSO2 Inc.; http://wso2.com
 
 lean.enterprise.middleware

 mobile: *+94728671315 <%2B94728671315>*


 

Re: [Dev] Same scope name cannot be used in different APIs

[Nuwan Dias]

A scope defines a unique action (view_user_profile, update_profile_status,
etc). You won't have two APIs performing the same action.

And it confuses the authorization part too. Ex: If role 'a' has permissions
for scope 'x' on 'API1', it won't necessarily mean role 'a' can perform the
same action on 'API2' because what API2 does is different to what API1 does.

Thanks,
NuwanD.

On Fri, Jun 24, 2016 at 11:33 AM, Niranjan Karunanandham 
wrote:

> Hi APIM,
>
> In APIM 1.10.0, I need to use the same scope name for two different API.
> When I try to assign a scope (which is already assigned to an API) to an
> API, I get the error message "Scope is already assigned by another API". Is
> this by design? Any reason as to why we can't apply the same scope to
> multiple APIs?
>
> Regards,
> Nira
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Nuwan Dias

Technical Lead - 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] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Kasun Bandara]

Hi Dinusha,

Yes. we will be fixing this issue with once we upgrade the kernel version
to 4.4.6. The opensaml version of the feature you have mentioned will be
upgraded to opensaml-2.6.4.wso2v3. The corresponding repository release
will be done along with the IS 5.2.0 GA release.

Thanks,
Kasun.

On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka 
wrote:

> Hi Kasun,
>
> Non of the appmgt features are bundling opensaml. It's comes to AppM
> product through identity features. Seems through the
> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
> this.
>
> [1]
> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
> [2]
> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>
> Regards,
> Dinusha.
>
> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara  wrote:
>
>> Hi Sajith,
>>
>> This issue was identified in [1] and we have fixed the issue with [2].
>> This issue can be resolve by using the new opensaml orbit. We are planning
>> to release identity repositories (~50) on top of kernel 4.4.6, after fixing
>> the security vulnerabilities as stated in [3]. You can refer [4] to get the
>> latest updates on IS 5.2.0 GA release.
>>
>> Thanks,
>> Kasun.
>>
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>
>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3 orbit
>>
>> [3] [Engineering] Security Hackathon to start from tomorrow
>>
>> [4] [Engineering] IS 5.2.0 GA Update
>>
>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana 
>> wrote:
>>
>>> Hi IS Team,
>>>
>>> AppM has been updated to the carbon kernel 4.4.6, and also I updated the
>>> IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher jaggery
>>> app I got below exception[1].
>>>
>>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't properly
>>> imported the required bouncy castle version which is version 
>>> 1.52.0.wso2v1(packed
>>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>>
>>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in the
>>> git repo with the required bouncy castle version[3]. So when you are
>>> planning to release the IS version, which bundles the opensaml_2.6.4.wso2v3
>>> into a feature? Currently, we are blocking due to this issue.
>>>
>>>
>>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>>> threw exception [Servlet execution threw an exception] with root cause
>>> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
>>> cannot be found by opensaml_2.6.4.wso2v2
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>> at
>>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
>>> at
>>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
>>> at
>>> org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
>>> at
>>> org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
>>> at
>>> org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor.process(SPInitSSOAuthnRequestProcessor.java:160)
>>> at
>>> org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:164)
>>> at
>>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleAuthenticationReponseFromFramework(SAMLSSOProviderServlet.java:702)
>>> at
>>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleRequest(SAMLSSOProviderServlet.java:178)
>>> at
>>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.doGet(SAMLSSOProviderServlet.java:95)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at
>>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> 

[Dev] Same scope name cannot be used in different APIs

[Niranjan Karunanandham]

Hi APIM,

In APIM 1.10.0, I need to use the same scope name for two different API.
When I try to assign a scope (which is already assigned to an API) to an
API, I get the error message "Scope is already assigned by another API". Is
this by design? Any reason as to why we can't apply the same scope to
multiple APIs?

Regards,
Nira

-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] encodeURIComponent is not working in ESB-BETA

[Hariprasath Thanarajah]

Hi Nuwan,

Now it is working as we expected. Thank you for your prompt response.

On Fri, Jun 24, 2016 at 10:36 AM, Nuwan Wimalasekara 
wrote:

> Hi Hariprasath,
>
> Seems this is also the same issue as [1] with the rhino17 upgrade. You can
> get rid of this issue when using toString() function whenever accessing a
> string which is concatenated using +.
>
> mc.setProperty('uri.var.requestQuery',requestQuery.toString());
>
> [1]
> https://mozilla.github.io/rhino/javadoc/org/mozilla/javascript/ConsString.html
>
>
> Thanks,
> Nuwanw
>
> On Fri, Jun 24, 2016 at 9:01 AM, Malaka Silva  wrote:
>
>> Seems like the behavior of encodeURIComponent
>> ​ changed due to rhino upgrade.
>>
>> @Hariprasath - Can you compare the out put from ESB 490 vs ESB 500?
>> ​ Also why are we using ​[1] to call the endpoint
>> instead of call mediator? AFAIK we agreed to change this during the review?
>>
>>
>> @​NuwanW - Any idea?
>>
>> [1]
>> https://github.com/wso2-extensions/esb-connector-powerbi/blob/master/src/main/java/org/wso2/carbon/connector/powerbi/auth/PowerBIAccessTokenGenerator.java
>>
>> On Thu, Jun 23, 2016 at 8:39 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> When we trying to run the integration test for PowerBI with the BETA
>>> release we got the following error[1], but in 4.9.0 it is working fine. I
>>> think it is because of [2]. How can we handle this?
>>>
>>> [1]
>>> [2016-06-23 20:19:14,807]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[\r][\n]"
>>> [2016-06-23 20:19:14,807]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "{[\n]"
>>> [2016-06-23 20:19:14,807]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[\n]"
>>> [2016-06-23 20:19:14,807]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[0x9]"authorizationCode":"AAABiL9Kn2Z27UubvWFPbm0gLdM9QCaEE__Umb9UkVqMUwnGW5ABwXLBdG5PDZbal_1sPGCDl9hb0BntSwR-Ru3gD5buzl8WmK-Xr2k8bIOw5sVZJgQOngtTEZIavKvrWs7vdbJy8VXNyv3YAlQrKDDwZ-MO8cZIOMDzg38LQUa4QwDZeaMr-xBenghSVA91OSr-GRtaMxEo_AZg_q_ajQEMThWYFMIfcjwPsXGf9YkMhNMW_rM_sKm6imyk9L6fkmCqL_AzdvT8WjbPHtam8uyQnTFKtv3Jt7wh3DVfVd1W73_I1k7LJd7ruKyMwiZOXwUDB_S4MnYUS-93_oPQm8V92c6aEOi87Hw9QdYP38mPY-mgYt8DcvSNYH8kBnUO59pC4MjLz34TjJA3VqfsOtUJ1o-AyLDZfpoxmMAIhhfq9gpnfBVA4vK22h_a8RHTQH--H1VUUiHQFhQAQVVsXVMPq2RensvexaJDHhDyhz-g6IKct9dZx6PwnFlHXYsmMuzTeC2BTKhdRnag1ZDzNIA7Q0C7C-mnWFR7n63VtMyMrwWXJQHStkWP7C0KjQFOBQCeZbQyJdGVRCc0nSELCtsgKkgnahvm_9mxmv3AlYjXUkGcUGzMAzsgVQxFzFn23B3B4at9N1BB69gm6vtUMTIkBwUqHtwzQqEEs4WO7WDVYPluq23i1IrmXug8qkoykarPujcccII57plUcj99_vVPPbfjIq51PjmMHpFZxbqjKQZ-pNy-OOLgTVyZDgit8Pt3IAA",[\n]"
>>> [2016-06-23 20:19:14,808]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,807] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
>>> "[0x9]"resource":"https://analysis.windows.net/powerbi/api"[\n];
>>> [2016-06-23 20:19:14,808]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,808] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "}"
>>> [2016-06-23 20:19:14,852]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,852] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.apiUrl>. Returning empty result. Error>>> invalid
>>> path
>>> [2016-06-23 20:19:14,856]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,856] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.defaultRetentionPolicy>. Returning empty result.
>>> Error>>> invalid path
>>> [2016-06-23 20:19:14,859]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,859] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.datasetName>. Returning empty result. Error>>>
>>> invalid path
>>> [2016-06-23 20:19:14,861]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,861] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.tables>. Returning empty result. Error>>> invalid
>>> path
>>> [2016-06-23 20:19:14,862]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2016-06-23 20:19:14,862] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.groupId>. Returning empty result. Error>>> invalid
>>> path
>>> [2016-06-23 20:19:14,863]  INFO
>>>