Re: [Dev] [DEV][API-M] Localization at tenant level

[Pubudu Priyashan]

@Amila: True. But that will be a common set of strings per language
displayed for anyone who is using that particular language as default in
the browser.

It might be worth considering if we can support this at tenant level as we
discussed offline if tenant A and tenant B are using the same language (eg:
French) and A and B would prefer to have their own customised text even
though it is the same language. WDYT?

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Tue, May 9, 2017 at 11:22 AM, Amila Maha Arachchi <ami...@wso2.com>
wrote:

> I just learned that this doen't necessarily should be a tenant level
> thing. We can define the locale strings and anyone who uses the locale will
> see the string we have defined.
>
> On Mon, May 8, 2017 at 6:59 PM, Amila Maha Arachchi <ami...@wso2.com>
> wrote:
>
>> This doesn't look like a tenant level thing. Once these instructions are
>> followed, it will change the language for anyone who access the publisher
>> or store.
>>
>> On Mon, May 8, 2017 at 3:14 PM, Pubudu Priyashan <pubu...@wso2.com>
>> wrote:
>>
>>> Hey guys,
>>>
>>> I was going through the document at [1] on changing the language in
>>> API-M Publisher/Store. I would like to know if this is possible to do at
>>> tenant level? Or would that automatically pick up if we place the language
>>> specific files in advised locations in the document and update the default
>>> language of the browser?
>>>
>>> Please advise how I can go about this for a tenant domain.
>>>
>>> [1] https://docs.wso2.com/display/AM210/Adding+International
>>> ization+and+Localization
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547 <+94%2077%20546%204547>
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>
>>
>> --
>> *Amila Maharachchi*
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446 <+94%2071%20937%201446>
>>
>>
>
>
> --
> *Amila Maharachchi*
> Software Architect
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446 <+94%2071%20937%201446>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][API-M] Localization at tenant level

[Pubudu Priyashan]

Hey guys,

I was going through the document at [1] on changing the language in API-M
Publisher/Store. I would like to know if this is possible to do at tenant
level? Or would that automatically pick up if we place the language
specific files in advised locations in the document and update the default
language of the browser?

Please advise how I can go about this for a tenant domain.

[1]
https://docs.wso2.com/display/AM210/Adding+Internationalization+and+Localization

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB] Appending the file name dynamically in WSO2 file connector

[Pubudu Priyashan]

Thanks Shafreen and Keerthika,

This approach works fine.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Thu, Nov 24, 2016 at 1:54 PM, Shafreen Anfar <shafr...@wso2.com> wrote:

> Hi Pubudu,
>
> What you can do is have the below part of the uri in some property.
>
>   value="file://home/pubudup/data/fileopen/inbound/
> original/"
>scope="default"
>type="STRING"/>
>
> And then have another property to append the file name to the end.
> Something like blew.
>
> 
> expression="fn:concat(get-property('filelocation'),get-property('FILE_NAME'),'
> ')"
>scope="default"
>type="STRING"/>
>
> Then in the connector try something as below,
>
> 
> *{$ctx:completeLocation}*
> sftp://john:@10.100.7.95/www/
>     1
> true
> 1
> false
> no
>  
>
>
>
> On Thu, Nov 24, 2016 at 1:42 PM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> I am using the file connector to copy a file from locationA to locationB.
>> I would like to know how we can identify the file name if it's variable and
>> append it to the file connector source url.
>>
>> for example, let's say I have already captured the file name in a
>> property.
>>
>> eg:-
>>  >expression="get-property('transport', 'FILE_NAME')"
>>scope="default"
>>type="STRING"/>
>>
>> I would like to append the value of the above property instead of having
>> 'test.pdf' in the source location in my file connector below.
>>
>>
>>  
>> file://home/pubudup/data/fileopen/inbound/original/
>> test.pdf
>> sftp://john:@10.100.7.95/www/
>> 1
>> true
>> 1
>> false
>> no
>>  
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB] Appending the file name dynamically in WSO2 file connector

[Pubudu Priyashan]

Hi all,

I am using the file connector to copy a file from locationA to locationB. I
would like to know how we can identify the file name if it's variable and
append it to the file connector source url.

for example, let's say I have already captured the file name in a property.

eg:-
 

I would like to append the value of the above property instead of having
'test.pdf' in the source location in my file connector below.


 

file://home/pubudup/data/fileopen/inbound/original/test.pdf
sftp://john:@10.100.7.95/www/
1
true
1
false
no
 

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB320][EE] Issues when executing a mixed subscriber script on a distributed setup

[Pubudu Priyashan]

+1. Thanks!

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Fri, Sep 30, 2016 at 2:18 PM, Indika Sampath <indi...@wso2.com> wrote:

> Hi Pubudu,
>
> We found that mentioned issue is currently fixed in the master branch [1].
> Our plan is to provide you a SNAPSHOT pack from current master branch after
> cutting a branch. You could continue on testing with it and report bugs
> against ALPHA.
>
> [1] https://github.com/wso2/andes/pull/711
>
> Cheers!
>
> On Fri, Sep 30, 2016 at 10:47 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hi guys,
>>
>> While preparing the long running tests we observed the issue raised at
>> [1]. Basically what happens is when we send mixed subscribers (Queues,
>> Topics, Durable topics, Shared subscriptions) to Node1 and Node2, some of
>> the subscribers are not getting created. We have attached the script used
>> for this in the mentioned JIRA above. Currently, this is a roadblock for us
>> to continue with the long-running tests. Appreciate if we can get this
>> addressed as soon as possible. Thanks!
>>
>> [1] https://wso2.org/jira/browse/MB-1816
>>
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MB320][EE] Issues when executing a mixed subscriber script on a distributed setup

[Pubudu Priyashan]

Hi guys,

While preparing the long running tests we observed the issue raised at [1].
Basically what happens is when we send mixed subscribers (Queues, Topics,
Durable topics, Shared subscriptions) to Node1 and Node2, some of the
subscribers are not getting created. We have attached the script used for
this in the mentioned JIRA above. Currently, this is a roadblock for us to
continue with the long-running tests. Appreciate if we can get this
addressed as soon as possible. Thanks!

[1] https://wso2.org/jira/browse/MB-1816


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB500] Invoking a secure proxy in a clustered set up

[Pubudu Priyashan]

It makes sense when you think in terms of dev cycles. Thanks for the
clarification guys.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Mon, Aug 8, 2016 at 11:19 AM, Rajith Vitharana <raji...@wso2.com> wrote:

> Hi Pubudu,
>
> On 8 August 2016 at 11:14, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> Hi Jagath,
>>
>> So when we do that, it requires the user to restart the server every time
>> they add a new https endpoint to add the keys to client-truststore. In
>> production environments, this is not
>>
> I'm not sure people do such things directly to the production envs, I
> think there are dev cycles before pushing such changes to production. Hence
> will have the chance to add required certs to the product before production.
>
> Thanks,
>
>> convenient and will have to go through a long process to add a key to the
>> truststore since it requires a server restart. Are there any better
>> approaches we can think of to overcome this without having to restart the
>> servers when we add new https endpoints?
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Mon, Aug 8, 2016 at 10:55 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Whenever you access a Https endpoint, you have to import back-end's
>>> certificate to client-truststore. That is the default requirement if you
>>> are using SSL between back-end and ESB.
>>>
>>> Thanks.
>>>
>>> On Mon, Aug 8, 2016 at 10:13 AM, Pubudu Priyashan <pubu...@wso2.com>
>>> wrote:
>>>
>>>> Hi ESB team,
>>>>
>>>> I have observed the following behaviour when invoking a secure proxy in
>>>> a clustered setup which calls an external http endpoint [1] with ESB 5.0.0
>>>> (Tested with RC1). Can you please inform if this behaviour is correct or
>>>> are there any alternative methods?
>>>>
>>>> I have a secure proxy in my ESB cluster where it calls an external
>>>> https endpoint [1]. When I invoked this in a single node in my local
>>>> machine, it returned the response as expected. When I created the same
>>>> secure proxy in a Cluster, I received this error [2]. I was able to get rid
>>>> of this error by adding the certificate of the endpoint
>>>> to client-truststore.jks file of each ESB node of the cluster.
>>>>
>>>> My question is, is this behaviour correct? Should we have to always add
>>>> the https endpoint certificate every time we need to use an external
>>>> endpoint in a secure proxy? Or is there another approach where we don't
>>>> have to do this and not required to add the keys to client-truststore.jks
>>>> and restart ESB nodes? This might not be convenient if we have a lot of
>>>> https endpoints being called via a secure proxy in ESB. Can you please
>>>> advice?
>>>>
>>>> Thanks!
>>>>
>>>> [1] https://demo5224632.mockable.io/test123
>>>>
>>>> [2] Exception in ESB worker node:-
>>>>
>>>> TID: [-1] [] [2016-08-04 05:34:33,682] DEBUG
>>>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>>>> dispatcher-1 >> "GET /services/SecureP1 HTTP/1.1[\r][\n]"
>>>> {org.apache.synapse.transport.http.wire}
>>>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>>>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>>>> dispatcher-1 >> "X-Forwarded-Host: wrk.esb500.wso2.com[\r][\n]"
>>>> {org.apache.synapse.transport.http.wire}
>>>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>>>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>>>> dispatcher-1 >> "X-Forwarded-Server: wrk.esb500.wso2.com[\r][\n]"
>>>> {org.apache.synapse.transport.http.wire}
>>>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>>>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>>>> dispatcher-1 >> "X-Forwarded-For: 10.100.7.95[\r][\n]"
>>>> {org.apache.synapse.transport.http.wire}
>>>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>

Re: [Dev] [DEV][ESB500] Invoking a secure proxy in a clustered set up

[Pubudu Priyashan]

Hi Jagath,

So when we do that, it requires the user to restart the server every time
they add a new https endpoint to add the keys to client-truststore. In
production environments, this is not convenient and will have to go through
a long process to add a key to the truststore since it requires a server
restart. Are there any better approaches we can think of to overcome this
without having to restart the servers when we add new https endpoints?

Cheers,

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Mon, Aug 8, 2016 at 10:55 AM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Pubudu,
>
> Whenever you access a Https endpoint, you have to import back-end's
> certificate to client-truststore. That is the default requirement if you
> are using SSL between back-end and ESB.
>
> Thanks.
>
> On Mon, Aug 8, 2016 at 10:13 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hi ESB team,
>>
>> I have observed the following behaviour when invoking a secure proxy in a
>> clustered setup which calls an external http endpoint [1] with ESB 5.0.0
>> (Tested with RC1). Can you please inform if this behaviour is correct or
>> are there any alternative methods?
>>
>> I have a secure proxy in my ESB cluster where it calls an external https
>> endpoint [1]. When I invoked this in a single node in my local machine, it
>> returned the response as expected. When I created the same secure proxy in
>> a Cluster, I received this error [2]. I was able to get rid of this error
>> by adding the certificate of the endpoint to client-truststore.jks file of
>> each ESB node of the cluster.
>>
>> My question is, is this behaviour correct? Should we have to always add
>> the https endpoint certificate every time we need to use an external
>> endpoint in a secure proxy? Or is there another approach where we don't
>> have to do this and not required to add the keys to client-truststore.jks
>> and restart ESB nodes? This might not be convenient if we have a lot of
>> https endpoints being called via a secure proxy in ESB. Can you please
>> advice?
>>
>> Thanks!
>>
>> [1] https://demo5224632.mockable.io/test123
>>
>> [2] Exception in ESB worker node:-
>>
>> TID: [-1] [] [2016-08-04 05:34:33,682] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "GET /services/SecureP1 HTTP/1.1[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "X-Forwarded-Host: wrk.esb500.wso2.com[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "X-Forwarded-Server: wrk.esb500.wso2.com[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "X-Forwarded-For: 10.100.7.95[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "Connection: upgrade[\r][\n]" {org.apache.synapse.transport.
>> http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "Host: ssl.esb500.com[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "Authorization: Basic 
>> YWRtaW5lc2I1MDA6ZXNiNTAwQERhcw==[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "Cache-Control: no-cache[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O
>> dispatcher-1 >> "User-Agent: Mozilla/5.0 (X11; Linux x86_64)
>> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116
>> Safari/537.36[\r][\n]" {org.apache.synapse.transport.http.wire}
>> TID: [-1] [] [2016-08-

[Dev] [DEV][ESB500] Invoking a secure proxy in a clustered set up

[Pubudu Priyashan]

Hi ESB team,

I have observed the following behaviour when invoking a secure proxy in a
clustered setup which calls an external http endpoint [1] with ESB 5.0.0
(Tested with RC1). Can you please inform if this behaviour is correct or
are there any alternative methods?

I have a secure proxy in my ESB cluster where it calls an external https
endpoint [1]. When I invoked this in a single node in my local machine, it
returned the response as expected. When I created the same secure proxy in
a Cluster, I received this error [2]. I was able to get rid of this error
by adding the certificate of the endpoint to client-truststore.jks file of
each ESB node of the cluster.

My question is, is this behaviour correct? Should we have to always add the
https endpoint certificate every time we need to use an external endpoint
in a secure proxy? Or is there another approach where we don't have to do
this and not required to add the keys to client-truststore.jks and restart
ESB nodes? This might not be convenient if we have a lot of https endpoints
being called via a secure proxy in ESB. Can you please advice?

Thanks!

[1] https://demo5224632.mockable.io/test123

[2] Exception in ESB worker node:-

TID: [-1] [] [2016-08-04 05:34:33,682] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "GET /services/SecureP1 HTTP/1.1[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "X-Forwarded-Host: wrk.esb500.wso2.com[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "X-Forwarded-Server: wrk.esb500.wso2.com[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "X-Forwarded-For: 10.100.7.95[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Connection: upgrade[\r][\n]" {org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Host: ssl.esb500.com[\r][\n]" {org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Authorization: Basic YWRtaW5lc2I1MDA6ZXNiNTAwQERhcw==[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Cache-Control: no-cache[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/48.0.2564.116 Safari/537.36[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Postman-Token: 60dc8ef4-36b0-03bd-5841-7efad2189071[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Accept: */*[\r][\n]" {org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Accept-Encoding: gzip, deflate, sdch[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "Accept-Language: en-US,en;q=0.8[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Listener I/O dispatcher-1
>> "[\r][\n]" {org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,813] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Sender I/O dispatcher-1
<< "CONNECT demo5224632.mockable.io:443 HTTP/1.1[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,814] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Sender I/O dispatcher-1
<< "Host: demo5224632.mockable.io:443[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,814] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Sender I/O dispatcher-1
<< "Proxy-Connection: Keep-Alive[\r][\n]"
{org.apache.synapse.transport.http.wire}
TID: [-1] [] [2016-08-04 05:34:33,814] DEBUG
{org.apache.synapse.transport.http.wire} -  HTTPS-Sender I/O dispatcher-1
<< "Proxy-Authorization: Basic c3F1aWQzdTpzcXVpZDN1[\r][\n]"

Re: [Dev] [ESB] Unable to start ESB 5.0.0 Beta2 on top of IBM JDK

[Pubudu Priyashan]

Hi Rajith and Ayoma,

*@Rajith:* I have checked this [1] with ESB Beta2 pack and it works with
both IBM 7 and 8 JDKs once you set the property as you have mentioned. I
have added this Doc JIRA [2] to include this information in official docs.
Is there a way that we can automatically pick the JDK whether it's IBM or
Oracle without setting this particular property? If so, one less step for
the user. So we may need to look into it if that's possible?

*@Ayoma:* Just looped you in just in case those two issues might be
related. As it turns out these aren't.

[1] https://wso2.org/jira/browse/ESBJAVA-4772
[2] https://wso2.org/jira/browse/DOCUMENTATION-3648

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Tue, Jul 19, 2016 at 11:16 PM, Ayoma Wijethunga <ay...@wso2.com> wrote:

> Hi Pubudu,
>
> I hope you were checking with me about "ESBJAVA-4740" [1]. Was
> "ESBJAVA-4772" mentioned by mistake?  Rajith is correct about
> "ESBJAVA-4772", although "ESBJAVA-4740" has nothing to do with CSRFGuard.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4740
>
> Regards,
> Ayoma
>
> On Tue, Jul 19, 2016 at 10:49 PM, Rajith Roshan <raji...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> Can you try setting the following property[1] in
>> "Owasp.CsrfGuard.Carbon.properties" file
>> (SERVER_HOME/repository/conf/security) which is default set to [2]. We
>> found same issue with G-Reg and overcame it by setting this property.
>>
>> [1] - org.owasp.csrfguard.PRNG.Provider=IBMJCE
>> [2] - org.owasp.csrfguard.PRNG.Provider=SUN
>>
>> Thanks!
>> Rajith
>>
>> On Mon, Jul 18, 2016 at 12:51 PM, Pubudu Priyashan <pubu...@wso2.com>
>> wrote:
>>
>>> Hi Senduran,
>>>
>>> We are currently facing the issue logged at [1] when starting the ESB
>>> pack with IBM JDK. Can we please take a look and get this fixed with the
>>> next release? This blocks us from testing the release on IBM JDK. Do let me
>>> know if you require any further information. Thanks!
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4772
>>>
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Roshan
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ayoma Wijethunga
> Software Engineer
> Platform Security Team
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile : +94 (0) 719428123 <+94+(0)+719428123>
> Blog : http://www.ayomaonline.com
> LinkedIn: https://www.linkedin.com/in/ayoma
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Unable to start ESB 5.0.0 Beta2 on top of IBM JDK

[Pubudu Priyashan]

Hi Senduran,

We are currently facing the issue logged at [1] when starting the ESB pack
with IBM JDK. Can we please take a look and get this fixed with the next
release? This blocks us from testing the release on IBM JDK. Do let me know
if you require any further information. Thanks!

[1] https://wso2.org/jira/browse/ESBJAVA-4772


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Unable to aggregate the XML messages by using Aggregate mediator

[Pubudu Priyashan]

Hi ESB team,

I have a simple proxy service with a clone mediator and within that, I call
three different endpoints where each endpoint returns an XML body [1]. I
would like to aggregate those three XML bodies into one message using
the aggregate mediator.

But in my config, I am getting the error message [2]. Can someone please
advise if something is missing in this config [3]? You can directly add [3]
into an ESB proxy and see the error message.

*[1] XML Message from the endpoint:-*



USD


*[2] Error Message:-*

[2016-07-13 21:53:04,821] ERROR - SequenceMediator Expecting an
implementation of SOAP Envelope as the parent. But received some other
implementation
org.apache.axiom.soap.SOAPProcessingException: Expecting an implementation
of SOAP Envelope as the parent. But received some other implementation
at
org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkParent(SOAPHeaderImpl.java:408)
at
org.apache.axiom.soap.impl.llom.SOAPElement.setParent(SOAPElement.java:81)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
at
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
at org.apache.synapse.mediators.eip.EIPUtils.addChildren(EIPUtils.java:171)
at
org.apache.synapse.mediators.eip.EIPUtils.enrichEnvelope(EIPUtils.java:135)
at
org.apache.synapse.mediators.eip.aggregator.AggregateMediator.getAggregatedMessage(AggregateMediator.java:498)
at
org.apache.synapse.mediators.eip.aggregator.AggregateMediator.completeAggregate(AggregateMediator.java:416)
at
org.apache.synapse.mediators.eip.aggregator.AggregateMediator.mediate(AggregateMediator.java:330)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:95)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:57)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:333)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:255)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)



*[3] ESB  Proxy config:-*


http://ws.apache.org/ns/synapse;
   name="CloneProxy1"
   transports="http,https"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 

 
 

   
  
 
  
  
 
http://www.mocky.io/v2/5786694b0f740aa58487"/>
 
  
   


   
  
 
  
  
 
http://www.mocky.io/v2/578669550f740aa58488"/>
 
  
   


   
  
 
  
  
 
http://www.mocky.io/v2/5786695f0f740aa58489"/>
 
  
   

 
 
  
  
 

 
 

   

http://services.samples/xsd;
xmlns:ser="http://services.samples;
xmlns:soap="http://www.w3.org/2003/05/soap-envelope;
expression="/*">
   

 
  
  
   
   



Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MySql5.7] Concern about MySql 5.7 scripts running with -Dsetup

[Pubudu Priyashan]

+1 to Nuwan's suggestion.

I too have experienced inconsistencies in the past while using the -Dsetup
when configuring the databases where we still have to manually execute the
scripts. Since we are not using this feature in production environments I
think it wouldn't hurt to get rid of this all together. Since we can always
run the relevant scripts manually, if there is no significant advantage of
keeping this feature I think it's a good idea to remove it. Just my
personal opinion.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Wed, Jul 13, 2016 at 11:35 AM, Nuwan Dias <nuw...@wso2.com> wrote:

> Practically the -Dsetup option is never used in production. All "real"
> users of our products have DB admins and all that who carefully evaluate
> and execute our DB scripts on their Database servers. They would never
> allow a product startup process to create tables and indexes at will on
> their database servers.
>
> So I think we should just remove this option all together. I know we've
> done that on C5 but it probably makes sense to remove this option in C4
> products as well. We sometimes even have to make design changes to our
> features to support this option (when two features have their own DB
> scripts). And I think its a complete waste because we're compromising the
> design of our products to support a feature thats never used in the real
> world.
>
> Thanks,
> NuwanD.
>
> On Wed, Jul 13, 2016 at 11:05 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>>
>> Hi all,
>>
>> When we use MySql 5.7 as the DB and start the server with -Dsetup without
>> manually executing the scripts at DB level, we have observed the issue
>> logged at [1] while testing wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. The
>> reason behind this is, by default the pack is picking up mysql.sql script
>> located at [$HOME]/dbscripts directory when started with -Dsetup. A
>> solution was suggested in this comment [2] to rename the mysql5.7.sql
>> scripts as mysql.sql when using MySql 5.7 db and we have verified that this
>> suggestion fixed the issue. We have logged a doc JIRA to include that
>> information at [3] for now.
>>
>> Our concern is since this is going to affect all the products when using
>> MySql5.7 do we have a better solution to automatically select the
>> mysql version without having to rename the script? Is it possible to add a
>> property to define the db version somewhere and then point to the relevant
>> script without renaming the script when starting with -Dsetup? Or any
>> better solution if possible. Appreciate your feedback on this. Thanks!
>>
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4748
>> [2]
>> https://wso2.org/jira/browse/ESBJAVA-4748?focusedCommentId=123463=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-123463
>> [3] https://wso2.org/jira/browse/DOCUMENTATION-3604
>>
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> 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] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Pubudu Priyashan]

Awesome. Thanks!

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando <chana...@wso2.com>
wrote:

> Hi Pubudu,
>
> We have already fixed this in the latest source and will share a pack soon.
>
> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hello Viraj and DevStudio team,
>>
>> We have observed the issue logged at [1] while testing ESB tooling
>> shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists for
>> both p2 repo as well as the pre-packaged Eclipse.
>>
>> Would it be possible for us to get this fix in with the next ESB pack
>> released for testing? Thanks!
>>
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-574
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>
>
> --
> 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] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Pubudu Priyashan]

Hello Viraj and DevStudio team,

We have observed the issue logged at [1] while testing ESB tooling shipped
with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists for both p2
repo as well as the pre-packaged Eclipse.

Would it be possible for us to get this fix in with the next ESB pack
released for testing? Thanks!


[1] https://wso2.org/jira/browse/DEVTOOLESB-574

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MySql5.7] Concern about MySql 5.7 scripts running with -Dsetup

[Pubudu Priyashan]

Hi all,

When we use MySql 5.7 as the DB and start the server with -Dsetup without
manually executing the scripts at DB level, we have observed the issue
logged at [1] while testing wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. The
reason behind this is, by default the pack is picking up mysql.sql script
located at [$HOME]/dbscripts directory when started with -Dsetup. A
solution was suggested in this comment [2] to rename the mysql5.7.sql
scripts as mysql.sql when using MySql 5.7 db and we have verified that this
suggestion fixed the issue. We have logged a doc JIRA to include that
information at [3] for now.

Our concern is since this is going to affect all the products when using
MySql5.7 do we have a better solution to automatically select the
mysql version without having to rename the script? Is it possible to add a
property to define the db version somewhere and then point to the relevant
script without renaming the script when starting with -Dsetup? Or any
better solution if possible. Appreciate your feedback on this. Thanks!


[1] https://wso2.org/jira/browse/ESBJAVA-4748
[2]
https://wso2.org/jira/browse/ESBJAVA-4748?focusedCommentId=123463=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-123463
[3] https://wso2.org/jira/browse/DOCUMENTATION-3604


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

[Pubudu Priyashan]

Thanks Jagath. We will test the fix once it's made available.

Cheers,
Pubudu.

On Friday, 8 July 2016, Jagath Sisirakumara Ariyarathne <jaga...@wso2.com>
wrote:

> Hi Pubudu,
>
> On Fri, Jul 8, 2016 at 5:29 PM, Pubudu Priyashan <pubu...@wso2.com
> <javascript:_e(%7B%7D,'cvml','pubu...@wso2.com');>> wrote:
>
>> [+Senduran]
>>
>> We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack.
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4741
>>
>
> This issue has been fixed by applying required filters in property file.
> We will update the JIRA.
>
> Thanks.
>
> On Fri, Jul 8, 2016 at 6:35 PM, Dulanja Liyanage <dula...@wso2.com
> <javascript:_e(%7B%7D,'cvml','dula...@wso2.com');>> wrote:
>
>>
>>
>> On Thu, Jul 7, 2016 at 4:53 PM, Ayoma Wijethunga <ay...@wso2.com
>> <javascript:_e(%7B%7D,'cvml','ay...@wso2.com');>> wrote:
>>
>>> Hi All,
>>>
>>> Original issue reported by Hasintha is relevant to how we handle session
>>> timeout conditions with CSRFGuard filter. We are working on this and will
>>> update with a resolution.
>>>
>>
>> The reason for this behavior is there's no session-existence check prior
>> to the form POST. Before CSRFGuard this was not a problem, because, upon a
>> failure due to session timeout one of the following would have happened:
>>
>>1. in the case of an ajaxprocessor - Request would be propagated to
>>the respective admin service, and upon its session non-existence 
>> exception,
>>will be redirected to the login page.
>>2. in the case of a non-ajaxprocessor - CarbonSecuredHttpContext will
>>redirect to the login page before hitting the actual jsp/servlet.
>>
>> Since CSRFGuard is a filter, it intercepts before either of the above
>> happen and sends a 403 forbidden - because that's what it's supposed to do.
>>
>> There's a platform level javascript function called sessionAwareFunction
>> (in main.js) that can be used for this. Registry Browser uses that. We have
>> to send the actual operation we want to do as a callback function to
>> sessionAwareFunction. It will initially do a session validity check
>> via /carbon/admin/jsp/session-validate.jsp and then execute what we want to
>> do.
>>
>> We tried to come up with a centralized solution for this, but failed.
>> Therefore, this need to be fixed at product-level.
>>
>> Please let us know if you see a better solution for this.
>>
>>
>>> In general CSRFGuard should work without any per-page modifications,
>>> since we are using JavaScript based attribute injection and header based
>>> protection for AJAX requests. However, there might be special cases in
>>> which these methodologies fail. Such incidences should be handled
>>> case-by-case and we will be adding all the special cases we identified in
>>> to the "Integration Checklist" of [1].
>>>
>>> We had a short offline session with Shavantha on the issue he is facing
>>> and identified that there are methods that use "
>>> *document.createElement('form')*" JavaScript call to build forms
>>> dynamically. Since CSRFGuard JavaScript will not be able to identify such
>>> forms, it is necessary to add CSRF token manually. Please see the
>>> screenshot attached which is the page source of [2]. In such situations it
>>> is required to use JSP Taglib to add CSRF token as an additional parameter.
>>> Please follow [1] for additional details.
>>>
>>> We can of cause arrange quick sessions with teams to check on any
>>> edge-case issues they are facing, relevant to CSRFGuard.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1LV23-hD7q1BjsruUdvM5dO4j7pIuUpzR_EYLmdfOo6k/edit#heading=h.xqvmgi6xtm6f
>>> [2]
>>> https://localhost:9443/t/tenant.com/carbon/user/edit-user-roles.jsp?username=ADDOMAIN%2FAdministrator699=ADDOMAIN%2FAdministrator699
>>>
>>> Best Regards,
>>> Ayoma.
>>>
>>> On Thu, Jul 7, 2016 at 11:35 AM, Shavantha Weerasinghe <
>>> shavan...@wso2.com <javascript:_e(%7B%7D,'cvml','shavan...@wso2.com');>>
>>> wrote:
>>>
>>>> [+Dulanjan]
>>>>
>>>> Hi All
>>>>
>>>> When trying to add multiple roles to a user using a feature such as *Select
>>>> all from page 1 to page 3* or clicking on a pagination number the same
>>>> error comes and throws an error similar to[1]
>>>>
>>>> [1]

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

[Pubudu Priyashan]

Hi Ayoma,

I had a look at "repository/conf/security/Owasp.CsrfGuard.Carbon.properties"
file and I can see the property [1] included in it. Can you please confirm
that this is as expected? Thanks!

[1] org.owasp.csrfguard.unprotected.Services=%servletContext%/services/*

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Fri, Jul 8, 2016 at 5:50 PM, Ayoma Wijethunga <ay...@wso2.com> wrote:

> Hi Pubudu / Senduran,
>
> This is not the exact same. "/carbon/proxyservices/" is one of EBS CSRF
> exclusion patterns (referring to previous filter configuration [1]).
>
> As discussed with Senduran over the call we had, this pattern needs to be
> added to OWASP CSRFGuard as a unprotected URL pattern ([2] section 6).
>
> Was the test performed on a pack with this configuration change? If so,
> lets have a quick remote session to check this out.
>
> [1]
> https://docs.google.com/document/d/16qTgkhOrhgH48ttnIuqEDG531cS1ouMLwqu1CtyfXLI/edit
>
> [2]
> https://docs.google.com/document/d/1A1T-t6IjIaxunjlSyjsGuKSC-x9xl3kilNCTpZVy-EM/edit#
>
> Thank you,
> Ayoma.
>
> On Fri, Jul 8, 2016 at 5:29 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> [+Senduran]
>>
>> We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack.
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4741
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Thu, Jul 7, 2016 at 4:53 PM, Ayoma Wijethunga <ay...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Original issue reported by Hasintha is relevant to how we handle session
>>> timeout conditions with CSRFGuard filter. We are working on this and will
>>> update with a resolution.
>>>
>>> In general CSRFGuard should work without any per-page modifications,
>>> since we are using JavaScript based attribute injection and header based
>>> protection for AJAX requests. However, there might be special cases in
>>> which these methodologies fail. Such incidences should be handled
>>> case-by-case and we will be adding all the special cases we identified in
>>> to the "Integration Checklist" of [1].
>>>
>>> We had a short offline session with Shavantha on the issue he is facing
>>> and identified that there are methods that use "
>>> *document.createElement('form')*" JavaScript call to build forms
>>> dynamically. Since CSRFGuard JavaScript will not be able to identify such
>>> forms, it is necessary to add CSRF token manually. Please see the
>>> screenshot attached which is the page source of [2]. In such situations it
>>> is required to use JSP Taglib to add CSRF token as an additional parameter.
>>> Please follow [1] for additional details.
>>>
>>> We can of cause arrange quick sessions with teams to check on any
>>> edge-case issues they are facing, relevant to CSRFGuard.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1LV23-hD7q1BjsruUdvM5dO4j7pIuUpzR_EYLmdfOo6k/edit#heading=h.xqvmgi6xtm6f
>>> [2]
>>> https://localhost:9443/t/tenant.com/carbon/user/edit-user-roles.jsp?username=ADDOMAIN%2FAdministrator699=ADDOMAIN%2FAdministrator699
>>>
>>> Best Regards,
>>> Ayoma.
>>>
>>> On Thu, Jul 7, 2016 at 11:35 AM, Shavantha Weerasinghe <
>>> shavan...@wso2.com> wrote:
>>>
>>>> [+Dulanjan]
>>>>
>>>> Hi All
>>>>
>>>> When trying to add multiple roles to a user using a feature such as *Select
>>>> all from page 1 to page 3* or clicking on a pagination number the same
>>>> error comes and throws an error similar to[1]
>>>>
>>>> [1]
>>>> [2016-07-07 11:34:37,139]  WARN - JavaLogger potential cross-site
>>>> request forgery (CSRF) attack thwarted (user:, ip:127.0.0.1,
>>>> method:POST, uri:/t/tenant.com/carbon/user/view-roles.jsp,
>>>> error:required token is missing from the request)
>>>>
>>>>
>>>> Regards,
>>>> Shavantha Weerasinghe
>>>> Senior Software Engineer QA
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware.
>>>> http://wso2.com
>>>> http://wso2.org
>>>> Tel :

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

[Pubudu Priyashan]

[+Senduran]

We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack.

[1] https://wso2.org/jira/browse/ESBJAVA-4741

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp


On Thu, Jul 7, 2016 at 4:53 PM, Ayoma Wijethunga  wrote:

> Hi All,
>
> Original issue reported by Hasintha is relevant to how we handle session
> timeout conditions with CSRFGuard filter. We are working on this and will
> update with a resolution.
>
> In general CSRFGuard should work without any per-page modifications, since
> we are using JavaScript based attribute injection and header based
> protection for AJAX requests. However, there might be special cases in
> which these methodologies fail. Such incidences should be handled
> case-by-case and we will be adding all the special cases we identified in
> to the "Integration Checklist" of [1].
>
> We had a short offline session with Shavantha on the issue he is facing
> and identified that there are methods that use "
> *document.createElement('form')*" JavaScript call to build forms
> dynamically. Since CSRFGuard JavaScript will not be able to identify such
> forms, it is necessary to add CSRF token manually. Please see the
> screenshot attached which is the page source of [2]. In such situations it
> is required to use JSP Taglib to add CSRF token as an additional parameter.
> Please follow [1] for additional details.
>
> We can of cause arrange quick sessions with teams to check on any
> edge-case issues they are facing, relevant to CSRFGuard.
>
> [1]
> https://docs.google.com/document/d/1LV23-hD7q1BjsruUdvM5dO4j7pIuUpzR_EYLmdfOo6k/edit#heading=h.xqvmgi6xtm6f
> [2]
> https://localhost:9443/t/tenant.com/carbon/user/edit-user-roles.jsp?username=ADDOMAIN%2FAdministrator699=ADDOMAIN%2FAdministrator699
>
> Best Regards,
> Ayoma.
>
> On Thu, Jul 7, 2016 at 11:35 AM, Shavantha Weerasinghe  > wrote:
>
>> [+Dulanjan]
>>
>> Hi All
>>
>> When trying to add multiple roles to a user using a feature such as *Select
>> all from page 1 to page 3* or clicking on a pagination number the same
>> error comes and throws an error similar to[1]
>>
>> [1]
>> [2016-07-07 11:34:37,139]  WARN - JavaLogger potential cross-site request
>> forgery (CSRF) attack thwarted (user:, ip:127.0.0.1,
>> method:POST, uri:/t/tenant.com/carbon/user/view-roles.jsp,
>> error:required token is missing from the request)
>>
>>
>> Regards,
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Wed, Jul 6, 2016 at 4:10 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi all,
>>>
>>> When trying to perform operations through admin console, once the
>>> session is expired we are getting a 403 from admin console. Seems like this
>>> occurs due to CSRF filter blocking the request since the session is no
>>> longer available at the server side.
>>>
>>> [2016-07-06 15:34:27,576]  WARN {org.owasp.csrfguard.log.JavaLogger} -
>>> potential cross-site request forgery (CSRF) attack thwarted
>>> (user:, ip:127.0.0.1, method:POST,
>>> uri:/carbon/userprofile/set-finish-ajaxprocessor.jsp, error:request token
>>> does not match session token)
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Ayoma Wijethunga
> Software Engineer
> Platform Security Team
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile : +94 (0) 719428123 <+94+(0)+719428123>
> Blog : http://www.ayomaonline.com
> LinkedIn: https://www.linkedin.com/in/ayoma
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg] Support for Regex pattern in store

[Pubudu Priyashan]

Noted. Thanks!

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Feb 29, 2016 at 11:10 AM, Thushara Ranawaka <thusha...@wso2.com>
wrote:

> Hi Pubudu,
>
> Thanks for pointing out this.
> For the recored from the user's perspective we are deprecating the use of
> wildcards in GC.
>
> Thanks,
> Thushara.
>
> On Mon, Feb 29, 2016 at 10:51 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Great, let's do that. Thanks.
>>
>> Cheers,
>> Pubudu.
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Mon, Feb 29, 2016 at 10:48 AM, Thushara Ranawaka <thusha...@wso2.com>
>> wrote:
>>
>>> [+dev][+documentation team]
>>>
>>> Hi Pubudu,
>>>
>>> We don't support regex in GReg 5.2.0 and as per the offline discussion
>>> had with Chathura, Isurwan and Chandana we will not support in the future
>>> as well. * and ? is the only two wild cards that we support ATM. How ever
>>> as per your request we identified that this behaviour can be append as a
>>> note in this[1] documentation.
>>>
>>> [1] -
>>> https://docs.wso2.com/display/Governance510/Searching+for+Assets+Using+Advanced+Search+Operators
>>>
>>> Thanks,
>>> Thushara.
>>>
>>>
>>> On Mon, Feb 29, 2016 at 10:34 AM, Pubudu Priyashan <pubu...@wso2.com>
>>> wrote:
>>>
>>>> Hello G-Reg team,
>>>>
>>>> Can someone please provide any information about the $subject and
>>>> currently expected behavior in 5.2.0 release? I can see some of the
>>>> patterns such as '*','?' are supported but some are not [1]. It might be a
>>>> good idea to include this information in Docs which patterns are supported
>>>> and which patterns are not, with other associated areas [2]. Thanks!
>>>>
>>>> [1] https://wso2.org/jira/browse/REGISTRY-3329
>>>> [2] https://wso2.org/jira/browse/DOCUMENTATION-3072
>>>>
>>>> Cheers,
>>>> Pubudu D.P
>>>> Senior Software Engineer - QA Team | WSO2 inc.
>>>> Mobile : +94775464547
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks,
>>> Thushara Kasun Ranawaka
>>> Software Engineer
>>> WSO2 Inc.; <http://www.wso2.com>
>>> lean.enterprise.middleware
>>> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
>>> *thusha...@wso2.com <thusha...@wso2.com>*
>>>
>>
>>
>
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.; <http://www.wso2.com>
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com <thusha...@wso2.com>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg] Support for Regex pattern in store

[Pubudu Priyashan]

Great, let's do that. Thanks.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Feb 29, 2016 at 10:48 AM, Thushara Ranawaka <thusha...@wso2.com>
wrote:

> [+dev][+documentation team]
>
> Hi Pubudu,
>
> We don't support regex in GReg 5.2.0 and as per the offline discussion had
> with Chathura, Isurwan and Chandana we will not support in the future as
> well. * and ? is the only two wild cards that we support ATM. How ever as
> per your request we identified that this behaviour can be append as a note
> in this[1] documentation.
>
> [1] -
> https://docs.wso2.com/display/Governance510/Searching+for+Assets+Using+Advanced+Search+Operators
>
> Thanks,
> Thushara.
>
>
> On Mon, Feb 29, 2016 at 10:34 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hello G-Reg team,
>>
>> Can someone please provide any information about the $subject and
>> currently expected behavior in 5.2.0 release? I can see some of the
>> patterns such as '*','?' are supported but some are not [1]. It might be a
>> good idea to include this information in Docs which patterns are supported
>> and which patterns are not, with other associated areas [2]. Thanks!
>>
>> [1] https://wso2.org/jira/browse/REGISTRY-3329
>> [2] https://wso2.org/jira/browse/DOCUMENTATION-3072
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>
>
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.; <http://www.wso2.com>
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com <thusha...@wso2.com>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg] Support for Regex pattern in store

[Pubudu Priyashan]

+ dev

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Feb 29, 2016 at 10:34 AM, Pubudu Priyashan <pubu...@wso2.com> wrote:

> Hello G-Reg team,
>
> Can someone please provide any information about the $subject and
> currently expected behavior in 5.2.0 release? I can see some of the
> patterns such as '*','?' are supported but some are not [1]. It might be a
> good idea to include this information in Docs which patterns are supported
> and which patterns are not, with other associated areas [2]. Thanks!
>
> [1] https://wso2.org/jira/browse/REGISTRY-3329
> [2] https://wso2.org/jira/browse/DOCUMENTATION-3072
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [G-Reg] Visibility of policy artifacts

[Pubudu Priyashan]

Hello G-Reg team,

I have a question regarding how to set up the visibility of a certain
artifact type in Store section for logged in and logged out users. The
reason I'm asking is, if you run "Getting Started" sample and the access
the store while being logged out, there are no policy artifacts displayed.
If you do the same while being logged in, you can see there are policy
artifacts available. I would like to know from where we can set up this
visibility for different artifact types. Thanks.


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [QA] Question on API-M gateway node maximum concurrent threads

[Pubudu Priyashan]

Hi Nuwan,

This was indeed very good information. We were able to create a Jmeter
script to simulate the scenario you have explained earlier. Also, we have
configured Java Flight Recorder as advised. Please find the long running
test details for API-M1.10.0 GA pack below.

*Long running test details:-*

- 20 concurrent invocations continuously being run using permanent tokens
(10 each http and https)
- 1000 tokens were generated by using 1000 different apps > subscribed to
an existing API using those apps > tokens expire after 45 minutes > expired
tokens are regenerated after every 45 minutes > invoke the API using newly
generated tokens concurrently with 30 threads (Altogether 50 concurrent
threads being executed continuously.)

We are planning to run these tests for two weeks and then get back to you
with outcomes. Thanks for your feedback on this.

Cheers,
Pubudu.




Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Fri, Jan 8, 2016 at 12:20 PM, Nuwan Dias <nuw...@wso2.com> wrote:

> +1.
>
> Thanks,
> NuwanD.
>
> On Fri, Jan 8, 2016 at 11:19 AM, Aparna Karunarathna <apa...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> Understood your concern Nuwan, I'm the one who proposed to add peak load
>> for few hours( ~ 4 hours) and check the memory growth, GC , exceptions etc
>> in Gateway and KM sides. In here we are not trying to hit the server with
>> max load, just want to check the server behavior. :) If you are not
>> agreeing to this, will do proper long running test for 2 weeks with load
>> that you suggested and will share the results with you. Then 3rd week will
>> do some ad-hoc test like we suggested and check server behavior. WDYT?
>>
>> Regards,
>> Aparna.
>>
>> On Fri, Jan 8, 2016 at 11:01 AM, Nuwan Dias <nuw...@wso2.com> wrote:
>>
>>> Hi Aparna,
>>>
>>> I'm totally +1 for the long running test. But my concern is that Pubudu
>>> is planning for a strange test. It doesn't look like a typical long running
>>> test. See his comment on the last reply "*generate a relatively higher
>>> number of threads lets say for a few hours of the day and stop it on daily
>>> basis*". The idea I get from this is that you're trying to hit the
>>> server at max load and then stop... hit it at max again and stop...
>>> likewise. Maybe I'm getting the wrong message but the information you've
>>> requested is for the max threads count and not the moderate threads count.
>>>
>>> IMO to mimick a real world scenario you should be hitting the sever with
>>> a moderate load (about 50 threads max) for a long time period. Not with a
>>> peak load (250 threads) for several hours. And we should monitor the
>>> servers during this period in order to have insight of any issues that may
>>> occur. The closer we get to the real world occurrence, the more
>>> valuable the outcome of our efforts would be.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Fri, Jan 8, 2016 at 10:47 AM, Aparna Karunarathna <apa...@wso2.com>
>>> wrote:
>>>
>>>> Hi Nuwan,
>>>>
>>>> Objective of doing a long running test after the release is, in the
>>>> release time we won't be able to execute a long running test for couple of
>>>> weeks. Because sometime we have to stop the test to change the packs or
>>>> integrate with other product with setup or to enable some configs to test a
>>>> feature, etc. Most of the time we are getting some cloud issue as
>>>> well(resource issues and set of nodes were getting slow). So most of time
>>>> we were able to run the long running test for day or 2 days.
>>>>
>>>> Therefor we thought of doing a proper long running test against the GA
>>>> pack for 3 weeks. Last year we did long running test after the release for
>>>> couple of releases and then we shared our findings(memory growth,
>>>> exceptions, warnings, etc) with dev teams. So if we can identify a bug at
>>>> this stage then we can prepare a fix.
>>>>
>>>> Regards,
>>>> Aparna.
>>>>
>>>>
>>>>
>>>> On Fri, Jan 8, 2016 at 9:22 AM, Nuwan Dias <nuw...@wso2.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 8, 2016 at 7:03 AM, Pubudu Priyashan <pubu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Nuwan,
>>>>>>
>>>>>> The idea is not to keep the peak level constant t

[Dev] [QA] Question on API-M gateway node maximum concurrent threads

[Pubudu Priyashan]

Hi Nuwan,

We are planning to start a long running test on the API-M 1.10.0 released
pack. As a part of this we need to simulate a peak time in gateway worker
nodes (by sending a large number of concurrent threads) could you please
let us know what is the maximum expected limit of concurrent threads that
we can be served in a single gateway worker node? We will then set up the
long-running tests accordingly. Thanks!

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [QA] Question on API-M gateway node maximum concurrent threads

[Pubudu Priyashan]

Hi Nuwan,

The idea is not to keep the peak level constant throughout the duration of
the long running test but, to generate a relatively higher number of
threads lets say for a few hours of the day and stop it on daily basis.
Appreciate if you could suggest a number for the peak thread count per
single gateway node so we can monitor the behaviour.

Currently we don't have scripts to support the scenario you suggested. We
will start working on this and create relevant scripts and update you once
we have tested the scenario you have mentioned. Thanks.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Thu, Jan 7, 2016 at 4:01 PM, Nuwan Dias <nuw...@wso2.com> wrote:

> Hi Pubudu,
>
> I don't think its useful to do a long running test at peak load because it
> doesn't happen in reality. Any system can hit peaks, but it would be a
> momentary occurrence rather than a long running situation.
>
> What would be more useful is to do the long running test under moderate
> load. This would mimick many real world scenarios. Therefore I would
> recommend to have the concurrency at 50 threads, using about 1000 access
> tokens and run the test in such a way that it renews its access tokens from
> time to time (either when they expire or once every 45 minutes or so).
>
> We should also configure the Java Flight Recorder (remotely, to avoid
> filling up the file system) so that we would have insight into issues if
> any. Also please make sure that the back-end system you front through the
> gateway is stable and can withhold the tests.
>
> Thanks,
> NuwanD.
>
> On Thu, Jan 7, 2016 at 3:18 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>>
>> Hi Nuwan,
>>
>> We are planning to start a long running test on the API-M 1.10.0 released
>> pack. As a part of this we need to simulate a peak time in gateway worker
>> nodes (by sending a large number of concurrent threads) could you please
>> let us know what is the maximum expected limit of concurrent threads that
>> we can be served in a single gateway worker node? We will then set up the
>> long-running tests accordingly. Thanks!
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>
>
>
> --
> 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

[Dev] [DEV][API-M] Question: Starting the API-M Nodes with Product Profiles

[Pubudu Priyashan]

Hi API-M team,

I have a question regarding starting the nodes with
-Dprofile=[profile_name] in a distributed setup. Let's say I have a setup
as explained below.

Setup:-
Publisher/Store
Gateway Manager
Gateway Worker1
Gateway Worker2
Key Manager1
Key Manager2

DB:- DB of your choice
LB:- Single Nginx LB used for all the above nodes


So in above setup, I'm using a single server for both Publisher and Store.
In this case, how would I use profiles to start the server? Can I use..
sh wso2server.sh -Dprofile=api-store -Dprofile=api-publisher
..to start my publisher/store node? Or should I start it without using a
profile at all? Also, how does this affect other nodes if I start this
publisher/store node with or without a profile?

Document:- https://docs.wso2.com/display/AM1100/Product+Profiles

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Bug in authenticationendpoint webapp?

[Pubudu Priyashan]

Hey Nuwan,

Looks like the root cause for this issue [1] is, due to the internal patch
changes we tested with in Alpha2 pack while debugging the LDAP connectivity
issue. Can you please take a look and make the necessary changes? Currently
this blocks us from testing in cluster due to user not being able to
generate keys since gateway cluster is broken.

Please let me know if you require any further information. Thanks.

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

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bug in authenticationendpoint webapp?

[Pubudu Priyashan]

Hi Lakmali,Lakshman,

The above issue is due to the following reason.

authenticationendpoint webapp was updated between Alpha2 and Alpha3. So
when we moved to the Alpha3 pack, we did not clean the SVN location.
Therefore it was looking for the webapp provided with Alpha3 pack on the
startup but it was synched with previous version of the webapp via svn.
Cleaning the SVN resolved this particular issue.

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Dec 7, 2015 at 7:40 PM, Lakmali Baminiwatta <lakm...@wso2.com>
wrote:

>
>
> On 7 December 2015 at 19:06, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> Hey Nuwan,
>>
>> Looks like the root cause for this issue [1] is, due to the internal
>> patch changes we tested with in Alpha2 pack while debugging the LDAP
>> connectivity issue. Can you please take a look and make the necessary
>> changes? Currently this blocks us from testing in cluster due to user not
>> being able to generate keys since gateway cluster is broken.
>>
>> Please let me know if you require any further information. Thanks.
>>
>
> As per the offline discussion had with Pubudu, this looks like due to SVN
> having old authentication web app. As discussed, let's clean the SVN and
> try with the artifacts of the latest pack's deployment directory.
>
> Thanks,
> Lakmali
>
>
>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4358
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakmali Baminiwatta
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bug in authenticationendpoint webapp?

[Pubudu Priyashan]

Hi Nuwan,

Noted. Thanks.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Dec 7, 2015 at 9:44 PM, Nuwan Dias <nuw...@wso2.com> wrote:

> Hi Pubudu,
>
> Please do not apply any patches to the latest pack. Those were given for
> the earlier pack to isolate issues that weren't reproducible on our end.
> And when resolving JiRAs, please update them with the correct state.
>
> Thanks,
> NuwanD.
>
> On Mon, Dec 7, 2015 at 7:06 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> Hey Nuwan,
>>
>> Looks like the root cause for this issue [1] is, due to the internal
>> patch changes we tested with in Alpha2 pack while debugging the LDAP
>> connectivity issue. Can you please take a look and make the necessary
>> changes? Currently this blocks us from testing in cluster due to user not
>> being able to generate keys since gateway cluster is broken.
>>
>> Please let me know if you require any further information. Thanks.
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4358
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>
>
>
> --
> 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

[Dev] Cluster Setup is pointed to API-M 1.10.0 Alpha3

[Pubudu Priyashan]

Hello team,

I have now pointed the API-M QA cluster to the most recent pack released on
the 04-Dec-2015. You may use it for testing when/if needed. Please note
that there is a known issue related to metrics DB, which is logged at [1].
The continuous DB exceptions triggered in back-end are related to this
issue. This doesn't stop us from testing the other areas.The issue is
currently fixed and it will be available with the next API-M pack for us to
test.

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

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] 1.10.0 - 401 Error when publishing an API

[Pubudu Priyashan]

Hi Nuwan,

Thanks for your assistance today debugging this issue. As we have now
identified it is a bug, the fix will be tested with ticket [1].

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

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Tue, Dec 1, 2015 at 9:57 AM, Nuwan Dias <nuw...@wso2.com> wrote:

> Hi Pubudu,
>
> The reason for the publishing failure is an authentication failure. The
> Publisher fails to authenticate with the Gateway to access its admin
> services. Could the admin passwords changed inconsistently?
>
> The Exception on the Gateway is not related to the error on publisher. Its
> an issue related to svn dep-sync. I'm not sure what that is.
>
> Although these have occurred when you tried to move to Oracle from MySQL,
> none of the errors are DB specific. There aren't any SQL related error logs
> in the traces you've attached. My guess is that they have been introduced
> during the migration process from MySQL to Oracle.
>
> If we cannot get this figured out soon can we sit together and have a
> look? It would make things fast.
>
> Thanks,
> NuwanD.
>
> On Mon, Nov 30, 2015 at 11:45 PM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Also, gateway worker nodes have given the attached exception after
>> the server was started.
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Mon, Nov 30, 2015 at 11:35 PM, Pubudu Priyashan <pubu...@wso2.com>
>> wrote:
>>
>>> Hi API-M team,
>>>
>>> We've been experiencing the attached exception in publisher node while
>>> trying to point the dep-sync svn location to a new folder path. We got rid
>>> of the same issue in mysql setup. But for Oracle 12c we are unable fix it
>>> with the same set of steps. Please find the steps we followed below.
>>>
>>> 1. Drop DBs and re-create the same DBs (apim, um, reg, stats)
>>> 2. Delete H2 dbs from all nodes ($home/repository/databases)
>>> 3. Delete $home/repository/deployment/server folder and replace the same
>>> from a fresh pack
>>> 4. Create a new svn folder and point it on carbon.xml in gateway manager
>>> and both gateway worker nodes.
>>> 5. Make sure there are no .svn folders within the file structure of
>>> gateway manager and gateway workers
>>> 6. Start all the nodes with -Dsetup
>>>
>>> This sequence worked for mysql, but for Oracle 12c set up, attached
>>> exception keeps appearing on publisher node when trying to publish an api
>>> from publisher to store. On UI it's giving attached error message. Could
>>> you please point out if we are missing something or could it be an issue
>>> related to Oracle db?
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>
>>
>
>
> --
> 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] 1.10.0 - 401 Error when publishing an API

[Pubudu Priyashan]

Also, gateway worker nodes have given the attached exception after
the server was started.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Mon, Nov 30, 2015 at 11:35 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:

> Hi API-M team,
>
> We've been experiencing the attached exception in publisher node while
> trying to point the dep-sync svn location to a new folder path. We got rid
> of the same issue in mysql setup. But for Oracle 12c we are unable fix it
> with the same set of steps. Please find the steps we followed below.
>
> 1. Drop DBs and re-create the same DBs (apim, um, reg, stats)
> 2. Delete H2 dbs from all nodes ($home/repository/databases)
> 3. Delete $home/repository/deployment/server folder and replace the same
> from a fresh pack
> 4. Create a new svn folder and point it on carbon.xml in gateway manager
> and both gateway worker nodes.
> 5. Make sure there are no .svn folders within the file structure of
> gateway manager and gateway workers
> 6. Start all the nodes with -Dsetup
>
> This sequence worked for mysql, but for Oracle 12c set up, attached
> exception keeps appearing on publisher node when trying to publish an api
> from publisher to store. On UI it's giving attached error message. Could
> you please point out if we are missing something or could it be an issue
> related to Oracle db?
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>


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

Re: [Dev] [APIM] setting up cluster without using -Dprofile - with puppet scripts

[Pubudu Priyashan]

Hey Nuwan.

We've been experiencing some issues when trying to start the cluster nodes
with -Dprofile option in our cluster set up for APIM 1.10.0 Alpha pack. I
have logged a ticket [1] with exceptions attached. Please let us know if
any further details required on this matter.

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

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Wed, Nov 11, 2015 at 2:52 PM, Suhan Dharmasuriya  wrote:

> Hi,
>
> When we try to deploy the cluster with APIM 1.10.x with profiles,
> following error [1] is observed in wso2carbon.log.
> Full log for gateway manager also attached.
>
> We have tried with default configurations as well as cluster
> configurations. In both cases the error occurs when trying with profiles.
>
> It would be great if you can guide us to overcome this issue.
>
> Following is the diff between a APIM 1.10.0-SNAPSHOT build pack
> wso2server.sh and our gateway node wso2server.sh file.
>
> $ diff 110wso2server.sh gwwso2server.sh
> 303a304
> > -Dprofile=gateway-manager \
>
> [1]
> TID: [-1] [] [2015-11-11 09:05:40,614] ERROR
> {org.apache.tomcat.util.digester.Digester} -  Begin event threw exception
> {org.apache.tomcat.util.digester.Digester}
> java.lang.ClassNotFoundException:
> org.wso2.carbon.webapp.mgt.loader.CarbonWebappLoader cannot be found by
> org.wso2.carbon.tomcat_4.4.2
> 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.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:144)
> at
> org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1288)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at
> org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
> at
> org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:649)
> at
> org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:592)
> at org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:850)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:397)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> TID: [-1] [] [2015-11-11 09:05:40,616] ERROR
> {org.apache.catalina.startup.ContextConfig} -  Parse error in context.xml
> for / {org.apache.catalina.startup.ContextConfig}
> org.xml.sax.SAXParseException; systemId: file:/mnt/
> 192.168.57.131/gateway/wso2am-1.10.0-SNAPSHOT/repository/conf/tomcat/context.xml;
> lineNumber: 24; columnNumber: 86; Error at (24, 86) :
> org.wso2.carbon.webapp.mgt.loader.CarbonWebappLoader cannot be found by
> org.wso2.carbon.tomcat_4.4.2
> at
> org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2711)
> at
> org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2743)
> at
> org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1291)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at
> 

Re: [Dev] ApiStoreExecutor compatibility with APIM 1.9.1

[Pubudu Priyashan]

Hi Chamin,

I have logged [1] to address this issue now.

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

Cheers,
Pubudu.

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Thu, Nov 5, 2015 at 4:52 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:

> Hi Chamin,
>
> While checking the APIM/GREG integration, I experienced two different
> behaviors for API 1.9.0 and API 1.9.1 versions tested against GREG 5.1.0.
> Basically what happens is that, the service gets pushed to the APIM
> publisher with given executor [1] but, in APIM 1.9.1 version I'm getting
> the error below. Can you please take a look if there's an incompatibility
> somewhere in service level? Please find the screenshots attached.
>
> Error in APIM Console:-
>
> [2015-11-05 16:23:29,263]  INFO - CarbonAuthenticationUtil
> 'admin@carbon.super [-1234]' logged in at [2015-11-05 16:23:29,263+0530]
> [2015-11-05 16:23:29,508]  INFO - CarbonAuthenticationUtil
> 'admin@carbon.super [-1234]' logged in at [2015-11-05 16:23:29,508+0530]
> [2015-11-05 16:23:30,099] ERROR - APIProviderHostObject Endpoint
> Configuration is missing
> [2015-11-05 16:23:30,103] ERROR - add:jag
> org.wso2.carbon.apimgt.api.APIManagementException: Endpoint Configuration
> is missing
>
>
>
> [1]
> https://docs.wso2.com/display/Governance501/Integrating+with+WSO2+API+Manager
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ApiStoreExecutor compatibility with APIM 1.9.1

[Pubudu Priyashan]

Hi Chamin,

As per my investigations, it was apparent that the APIM 1.9.1 version is
using following mandatory fields in Create API call. This was not the case
for APIM 1.9.0. I'm assuming that this could be the root cause for this
issue.

1. endpoint_type
2. endpoint_config
3. production_endpoints
4. sandbox_endpoints
5. endpointType

Cheers,
Pubudu.


Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Thu, Nov 5, 2015 at 5:36 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:

> Hi Chamin,
>
> I have logged [1] to address this issue now.
>
> [1] https://wso2.org/jira/browse/APIMANAGER-4199
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Thu, Nov 5, 2015 at 4:52 PM, Pubudu Priyashan <pubu...@wso2.com> wrote:
>
>> Hi Chamin,
>>
>> While checking the APIM/GREG integration, I experienced two different
>> behaviors for API 1.9.0 and API 1.9.1 versions tested against GREG 5.1.0.
>> Basically what happens is that, the service gets pushed to the APIM
>> publisher with given executor [1] but, in APIM 1.9.1 version I'm getting
>> the error below. Can you please take a look if there's an incompatibility
>> somewhere in service level? Please find the screenshots attached.
>>
>> Error in APIM Console:-
>>
>> [2015-11-05 16:23:29,263]  INFO - CarbonAuthenticationUtil
>> 'admin@carbon.super [-1234]' logged in at [2015-11-05 16:23:29,263+0530]
>> [2015-11-05 16:23:29,508]  INFO - CarbonAuthenticationUtil
>> 'admin@carbon.super [-1234]' logged in at [2015-11-05 16:23:29,508+0530]
>> [2015-11-05 16:23:30,099] ERROR - APIProviderHostObject Endpoint
>> Configuration is missing
>> [2015-11-05 16:23:30,103] ERROR - add:jag
>> org.wso2.carbon.apimgt.api.APIManagementException: Endpoint Configuration
>> is missing
>>
>>
>>
>> [1]
>> https://docs.wso2.com/display/Governance501/Integrating+with+WSO2+API+Manager
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Clarification: Should users be allowed to create a new API version using a deprecated API version?

[Pubudu Priyashan]

Hello APIM team,

I have come across $subject while going through APIM functionality (1.9.1).
Currently, it is possible to create a new API version using a deprecated
API version. Shouldn't this be restricted? If not why?

The reason I'm asking this question is because, once users create the most
recent version of the API, shouldn't it be used to create later versions of
the same API rather than using older/deprecated versions?

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Pubudu Priyashan]

Hi Nirdesha,

Can we please point the current context sensitive help pages to relevant
product documentation of GReg 5.0.0 release?

Cheers,

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana  wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri 
> wrote:
>
>> Ack!
>>
>> @Chalitha/Thaya/Pubudu. Please note.
>>
>
> And all the context sensitive help pages  are outdated .
>
> -Ajith
>
>
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead  - Quality Assurance
>> Mobile: +94773125935
>> Blog: evanthika.blogspot.com
>>
>> wso2.com lean.enterprise.middleware
>>
>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>>
>>> Hi All
>>>
>>> This is non a bug but please fix the about page if possible because this
>>> is a major release. (find the attached image)
>>>
>>> -Ajith
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>>> wrote:
>>>
 Hi All,

 *This is the RC 2 release candidate of G-Reg 5.0.0 *

 This release fixes the following issues:

 https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
 https://wso2.org/jira/browse/REGISTRY-2908

 Please download, test and vote. Please refer the release verification
 guide for detailed information on verifying this release.

 *Source & binary distribution files:*


 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/

 *Maven staging repo:*

 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/

 *The tag to be voted upon:*

 https://github.com/wso2/product-greg/tree/v5.0.0-rc2



 [*+*] Stable - go ahead and release

 [*-*]  Broken - do not release (explain why)

 Thanks and Regards
 G-Reg team

 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 718 11 27 51
 twitter: @prasa77

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


>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Pubudu Priyashan]

Hi Chandana,

Since the Help page, context specific pages are out-dated we need to update
those to reflect most recent information. Can you please address this issue
as required? Please find the relevant ticket below. Thanks.

https://wso2.org/jira/browse/REGISTRY-2910

Cheers,

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <nirde...@wso2.com>
wrote:

> The context sensitive help links are in the product UIs. AFAIK, these
> links are component-based rather than product based? Please correct me if I
> am wrong.
>
> If they are component-based, we cannot link to the wiki of a specific
> product from there as many other products might also be using the same
> component.
>
> Maybe we should simply disable these help links until we find a better way
> to maintain them.
>
> Thanks,
> -Nirdesha
>
> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan <pubu...@wso2.com>
> wrote:
>
>> Hi Nirdesha,
>>
>> Can we please point the current context sensitive help pages to relevant
>> product documentation of GReg 5.0.0 release?
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana <aji...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <evanth...@wso2.com
>>> > wrote:
>>>
>>>> Ack!
>>>>
>>>> @Chalitha/Thaya/Pubudu. Please note.
>>>>
>>>
>>> And all the context sensitive help pages  are outdated .
>>>
>>> -Ajith
>>>
>>>
>>>>
>>>> Regards,
>>>> Evanthika Amarasiri
>>>> Senior Technical Lead  - Quality Assurance
>>>> Mobile: +94773125935
>>>> Blog: evanthika.blogspot.com
>>>>
>>>> wso2.com lean.enterprise.middleware
>>>>
>>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana <aji...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi All
>>>>>
>>>>> This is non a bug but please fix the about page if possible because
>>>>> this is a major release. (find the attached image)
>>>>>
>>>>> -Ajith
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <prasa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>>>>>
>>>>>> This release fixes the following issues:
>>>>>>
>>>>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>>>>> https://wso2.org/jira/browse/REGISTRY-2908
>>>>>>
>>>>>> Please download, test and vote. Please refer the release verification
>>>>>> guide for detailed information on verifying this release.
>>>>>>
>>>>>> *Source & binary distribution files:*
>>>>>>
>>>>>>
>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>>>>>
>>>>>> *Maven staging repo:*
>>>>>>
>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>>>>>
>>>>>> *The tag to be voted upon:*
>>>>>>
>>>>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>>>>>
>>>>>>
>>>>>>
>>>>>> [*+*] Stable - go ahead and release
>>>>>>
>>>>>> [*-*]  Broken - do not release (explain why)
>>>>>>
>>>>>> Thanks and Regards
>>>>>> G-Reg team
>>>>>>
>>>>>> Prasanna Dangalla
>>>>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> cell: +94 718 11 27 51
>>>>>> twitter: @prasa77
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ajith Vitharana.
>>>>>
>>>>> WSO2 Inc. - http://wso2.com
>>>>> Email  : aji...@wso2.com
>>>>> Blog: http://vitharana.org
>>>>> Mobile : +1-812-360-5335
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>
>
> --
>
> Thanks,
>
> Nirdesha Munasinghe,
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 776321920
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Pubudu Priyashan]

Noted. I have created following ticket in JIRA to address the About page
now.

https://wso2.org/jira/browse/REGISTRY-2909

Cheers,

Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

On Wed, Sep 2, 2015 at 9:38 AM, Evanthika Amarasiri 
wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>
>> Hi All
>>
>> This is non a bug but please fix the about page if possible because this
>> is a major release. (find the attached image)
>>
>> -Ajith
>>
>>
>>
>>
>>
>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi All,
>>>
>>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>>
>>> This release fixes the following issues:
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>> https://wso2.org/jira/browse/REGISTRY-2908
>>>
>>> Please download, test and vote. Please refer the release verification
>>> guide for detailed information on verifying this release.
>>>
>>> *Source & binary distribution files:*
>>>
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>>
>>> *Maven staging repo:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>>
>>> *The tag to be voted upon:*
>>>
>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>>
>>>
>>>
>>> [*+*] Stable - go ahead and release
>>>
>>> [*-*]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards
>>> G-Reg team
>>>
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Clarification on GREG Clustering Setup for 5.0.0

[Pubudu Priyashan]

Hi All,

We are currently testing the GREG clustering setup for 5.0.0.

1. Previously in 4.6 GREG version the recommended setup was with three GREG
instances with one dummy node and the registry mount.
But in 5.0.0 we've been told to test the clustering set up with two GREG
manager nodes using one IS instance as the external IDP with user store and
registry mount.

Can you please confirm what is the recommended set up for GREG 5.0.0 and
the document link?


2. Also in GREG clustering tutorial with nginx[1], it requires user to
access '$GREG_HOME/dbscripts/apimgt/mysql.sql' location. But apimgt
directory is not available in GREG 5.0.0 version by default. Do we need to
update the document [1] to reflect most recent clustering setup?

Appreciate your advise on above two questions. Thanks.

[1]
https://docs.wso2.com/display/CLUSTER420/Clustering+Governance+Registry+with+Nginx#ClusteringGovernanceRegistrywithNginx-Environment


Best Regards,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GREG Reporting Sample Error (Maven dependencies)

[Pubudu Priyashan]

Hi there,

I was trying to run the GREG sample for reporting section [1]. When I did
'mvn clean install' It's giving me the error provided below. Also I found a
similar issue logged in JIRA[2], although I'm not 100% sure if these two
issues are related. Can someone please look into this please? Thanks!

[1] https://docs.wso2.com/display/Governance460/Custom+Report+Sample
[2] https://wso2.org/jira/browse/REGISTRY-2118

*Error Log:*

[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) jasperreports:jasperreports:jar:3.7.1

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=jasperreports
-DartifactId=jasperreports -Dversion=3.7.1 -Dpackaging=jar
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=jasperreports
-DartifactId=jasperreports -Dversion=3.7.1 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
   1)
org.wso2.governance:org.wso2.carbon.registry.samples.handler:bundle:4.6.0
   2) org.wso2.carbon:org.wso2.carbon.reporting.api:jar:4.2.0
   3) jasperreports.wso2:jasperreports:jar:3.7.1.wso2v1
   4) jasperreports:jasperreports:jar:3.7.1

--
1 required artifact is missing.

for artifact:
  org.wso2.governance:org.wso2.carbon.registry.samples.handler:bundle:4.6.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)



[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 8 seconds
[INFO] Finished at: Fri Jul 17 16:43:14 IST 2015
[INFO] Final Memory: 43M/333M
[INFO]


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev