[Dev] Error with latest kubernates artifacts in GCE

[Ayeshmantha Perera]

Hi All

I'm deploying the latest wso2 apim kubernatres artifacts[1] in GCE. For
current deployment I used pattern 1 [2] and I removed wso2am analytics from
the docker image by disablingconf/apimanager.xml in both worker and
manager. But when the deployment is done the worker and manager still give
an Error I 'm attaching the error log text with this mail.And the
containers are getting failed due to this issue.
Can anyone please  help me on this?

Regards,
Ayeshmantha


[1]
 https://github.com/isurulucky/kubernetes-apim/tree/new-deployment-patterns

[2] https://github.com/isurulucky/docker-apim/tree/new-deployment-patterns

2017-07-19T05:36:49.414343643Z [2017-07-19 05:36:49,414]  INFO - 
KafkaEventAdapterServiceHolder Kafka input event adaptor waiting for dependent 
configurations to load
2017-07-19T05:36:49.501116034Z [2017-07-19 05:36:49,484] ERROR - 
MessageTracerServiceComponent Unable to create stream: Cannot create directory 
to add tenant specific Event Stream : DAS_MESSAGE_TRACE:1.0.0
2017-07-19T05:36:49.501160242Z 
org.wso2.carbon.event.stream.core.exception.EventStreamConfigurationException: 
Cannot create directory to add tenant specific Event Stream : 
DAS_MESSAGE_TRACE:1.0.0
2017-07-19T05:36:49.501177226Z  at 
org.wso2.carbon.event.stream.core.internal.CarbonEventStreamService.addEventStreamDefinition(CarbonEventStreamService.java:224)
2017-07-19T05:36:49.501184722Z  at 
org.wso2.carbon.analytics.message.tracer.handler.internal.MessageTracerServiceComponent.activate(MessageTracerServiceComponent.java:84)
2017-07-19T05:36:49.501196012Z  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2017-07-19T05:36:49.501201437Z  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2017-07-19T05:36:49.501206782Z  at 
java.lang.reflect.Method.invoke(Method.java:498)
2017-07-19T05:36:49.501211712Z  at 
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
2017-07-19T05:36:49.501217504Z  at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
2017-07-19T05:36:49.501223239Z  at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
2017-07-19T05:36:49.50122854Z   at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
2017-07-19T05:36:49.501234009Z  at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
2017-07-19T05:36:49.501239334Z  at 
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
2017-07-19T05:36:49.501244402Z  at 
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
2017-07-19T05:36:49.501250472Z  at 
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
2017-07-19T05:36:49.501256124Z  at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
2017-07-19T05:36:49.501261577Z  at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
2017-07-19T05:36:49.50126667Z   at 
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
2017-07-19T05:36:49.501271989Z  at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
2017-07-19T05:36:49.501277332Z  at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
2017-07-19T05:36:49.501282712Z  at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
2017-07-19T05:36:49.50128793Z   at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
2017-07-19T05:36:49.501305729Z  at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
2017-07-19T05:36:49.501311779Z  at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
2017-07-19T05:36:49.501317424Z  at 
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:514)
2017-07-19T05:36:49.501322574Z  at 
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
2017-07-19T05:36:49.501327742Z  at 
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:94)
2017-07-19T05:36:49.501332932Z  at 
sun.reflect.NativeMethodAcc2017-07-19T05:36:49.530424097Zat 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2017-07-19T05:36:49.530429447Z  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
2017-07-19T05:36:49.530434837Z  at 

[Dev] [Documentation][IS-Analytics] IS 5.3.0 Configuring Email alerts for IS-analytics

[Himasha Guruge]

Hi Samuel/Sherene,

In [1] and [2] we are missing information on configuring alerts as email.
We need to update the documentation with relevant steps and screenshots.
Please refer Hasintha's blog [3].


[1] https://docs.wso2.com/display/IS530/Configuring+Alerts
[2] https://docs.wso2.com/display/IS530/Receiving+Alerts
[3]
https://medium.com/@hasinthaindrajee/real-time-email-alerts-for-abnormal-user-behaviors-with-wso2-identity-server-analytics-2dbf0cfdeeb6

Thanks,
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB - Keep the processing even if a service call goes wrong

[Himasha Guruge]

Hi,

You could use the  SET_ROLLBACK_ONLY property in a fault sequence, so that
when a failure occurs the transaction will be rolled back. Please refer [1]
for more information.

[1] https://docs.wso2.com/display/ESB500/JMS+Transactions

Thanks,
Himasha

On Wed, Jul 19, 2017 at 1:45 AM, Júnior  wrote:

> Hello,
>
> I have a proxy and inside the proxy we have some calls to a  template for
> auditing that just post a message to a queue.
>
> I'd like that even if there is a problem when sending the message to
> queue, the processing proceed in the Proxy.
>
> Is there any way of doing that?
>
> Any ideas are very welcome.
>
> Thanks,
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DSS with a very huge ammount of data

[Madhawa Gunasekara]

Hi Junior,

You can enable streaming to reduce the time that taken to build the whole
XML. and also you can increase the fetch size in the query [1], then the
number of rows fetched with each database round trip for a query will be
increased, so this will also reduce the time significantly.

[1] https://docs.wso2.com/display/DSS322/Advanced+Query+Properties

Thanks,
Madhawa

On Wed, Jul 19, 2017 at 6:45 AM, Júnior  wrote:

> Hi,
>
> We have a query that is being exposed using DSS.
>
> The query by itself take a lot of time, because it brings a lot of data,
> but we noticed that it is taking a lot of time to build the XML that is
> returned by the service.
>
> Is there any config that we could make to improve the XML creation
> performance?
>
> Any tips for this kind of scenario?
>
> Thanks
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhawa Gunasekara*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] DSS with a very huge ammount of data

[Júnior]

Hi,

We have a query that is being exposed using DSS.

The query by itself take a lot of time, because it brings a lot of data,
but we noticed that it is taking a lot of time to build the XML that is
returned by the service.

Is there any config that we could make to improve the XML creation
performance?

Any tips for this kind of scenario?

Thanks
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JWT Token Generation

[Vazquez-Hidalgo, Javier]

Hi Harsha,

Thanks for quick response and yes,  I would like to generate JWT token only if 
some header is present.

Let me give you more context on what I’m trying to accomplish:

Setup:


1)  APIM 2.1 + Identity Server 5.3 acting as the Key Manager.

2)  OpenID Connect is used for authentication.

3)  User roles and permissions are retrieved from an internal service, not 
from Identity Server. So, when a token (scope=openid) is requested the id_token 
is generated with our internal roles and permissions + other attributes.


The problem:


1)  Some of the services behind the Gateway have protected endpoints by our 
internal roles or permissions, so we send the signed id_token  as a http header 
and the service validates the token, builds a profile from the token and 
authorizes the user.

2)  Another use case is when we want to hit the endpoint from APIM Store 
(Swagger UI). The swager definition has the id_token http header mandatory but 
I would like to make it optional and have the APIM generate the id_token only 
if the header is not present (my initial question).


What are your thoughts on this, can we approach this problem in a better way?

Thanks,
Javier

From: Harsha Kumara [mailto:hars...@wso2.com]
Sent: Tuesday, July 18, 2017 7:20 PM
To: Vazquez-Hidalgo, Javier
Cc: dev@wso2.org
Subject: Re: [Dev] JWT Token Generation

Hey Javier,

Do you want to generate JWT token only if some header present in the request? 
For the current implementation, we can't control it as it will generate in the 
KM. But you can manipulate headers in gateway so you can decide which token you 
should send to the backend either APIM generated on or newly created JWT token.


Thanks,
Harsha

2017-07-19 0:41 GMT+02:00 Vazquez-Hidalgo, Javier 
>:
Hello,

What is the best approach to have APIM generate a JWT Token only if a header is 
passed to the request?

Thanks,
Javier


If you wish to unsubscribe from receiving commercial electronic messages from 
TD Bank Group, please click here or go to the 
following web address: www.td.com/tdoptout
Si vous souhaitez vous désabonner des messages électroniques de nature 
commerciale envoyés par Groupe Banque TD veuillez cliquer 
ici ou vous rendre à l'adresse 
www.td.com/tddesab

NOTICE: Confidential message which may be privileged. Unauthorized 
use/disclosure prohibited. If received in error, please go to 
www.td.com/legal for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. 
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière 
d'aller au 
www.td.com/francais/avis_juridique 
pour des instructions.

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



--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JWT Token Generation

[Harsha Kumara]

Hey Javier,

Do you want to generate JWT token only if some header present in the
request? For the current implementation, we can't control it as it will
generate in the KM. But you can manipulate headers in gateway so you can
decide which token you should send to the backend either APIM generated on
or newly created JWT token.


Thanks,
Harsha

2017-07-19 0:41 GMT+02:00 Vazquez-Hidalgo, Javier <
javier.vazquez-hida...@tdsecurities.com>:

> Hello,
>
>
>
> What is the best approach to have APIM generate a JWT Token only if a
> header is passed to the request?
>
>
>
> Thanks,
>
> Javier
>
>
>
> If you wish to unsubscribe from receiving commercial electronic messages
> from TD Bank Group, please click here  or go
> to the following web address: www.td.com/tdoptout
> Si vous souhaitez vous désabonner des messages électroniques de nature
> commerciale envoyés par Groupe Banque TD veuillez cliquer ici
>  ou vous rendre à l'adresse www.td.com/tddesab
>
>
> NOTICE: Confidential message which may be privileged. Unauthorized
> use/disclosure prohibited. If received in error, please go to
> www.td.com/legal for instructions.
> AVIS : Message confidentiel dont le contenu peut être privilégié.
> Utilisation/divulgation interdites sans permission. Si reçu par erreur,
> prière d'aller au www.td.com/francais/avis_juridique pour des
> instructions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] JWT Token Generation

[Vazquez-Hidalgo, Javier]

Hello,

What is the best approach to have APIM generate a JWT Token only if a header is 
passed to the request?

Thanks,
Javier

If you wish to unsubscribe from receiving commercial electronic messages from 
TD Bank Group, please click here or go to the following web address: 
www.td.com/tdoptout
Si vous souhaitez vous désabonner des messages électroniques de nature 
commerciale envoyés par Groupe Banque TD veuillez cliquer ici ou vous rendre à 
l'adresse td.com/tddesab

NOTICE: Confidential message which may be privileged. Unauthorized 
use/disclosure prohibited. If received in error, please go to www.td.com/legal 
for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. 
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière 
d'aller au www.td.com/francais/avis_juridique pour des instructions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB - Keep the processing even if a service call goes wrong

[Júnior]

Hello,

I have a proxy and inside the proxy we have some calls to a  template for
auditing that just post a message to a queue.

I'd like that even if there is a problem when sending the message to queue,
the processing proceed in the Proxy.

Is there any way of doing that?

Any ideas are very welcome.

Thanks,
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIs for Local and Outbound Authenticators

[Harsha Thirimanna]

https://wso2.org/jira/browse/DOCUMENTATION-4598

On 18 Jul 2017 4:30 pm, "Harsha Thirimanna"  wrote:

Hi Johan,

This was raised earier as well and it was missed because of some other
priorities.

We will create a doc Jira for this and will address.


On 18 Jul 2017 12:41 pm, "Johann Nallathamby"  wrote:

Hi,

I was trying to find proper documentation for extending the Basic Auth
authenticator and implementing conditional step up authentication with
TOTP. However I couldn't find proper documentation for extending local
authenticators. The only documentation I found for customizing
authenticators in IS 5.3.0 is [1]. However that mostly talks about
federated authenticators. [2] was a better reference for me. I think we
have to improve the categorization of local authenticators, federated
authenticators and request-path authenticators, explain in which scenario
to use what in our official documentation.

[1] https://docs.wso2.com/display/IS530/Writing+a+Custom+Federat
ed+Authenticator
[2] https://dzone.com/articles/custom-authenticator-for-
wso2-identity-server-wso2

Thanks & Regards,
Johann.

-- 

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *

-- 
You received this message because you are subscribed to the Google Groups
"WSO2 Documentation Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to documentation+unsubscr...@wso2.com.
For more options, visit https://groups.google.com/a/wso2.com/d/optout.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIs for Local and Outbound Authenticators

[Harsha Thirimanna]

Hi Johan,

This was raised earier as well and it was missed because of some other
priorities.

We will create a doc Jira for this and will address.

On 18 Jul 2017 12:41 pm, "Johann Nallathamby"  wrote:

Hi,

I was trying to find proper documentation for extending the Basic Auth
authenticator and implementing conditional step up authentication with
TOTP. However I couldn't find proper documentation for extending local
authenticators. The only documentation I found for customizing
authenticators in IS 5.3.0 is [1]. However that mostly talks about
federated authenticators. [2] was a better reference for me. I think we
have to improve the categorization of local authenticators, federated
authenticators and request-path authenticators, explain in which scenario
to use what in our official documentation.

[1] https://docs.wso2.com/display/IS530/Writing+a+Custom+
Federated+Authenticator
[2] https://dzone.com/articles/custom-authenticator-
for-wso2-identity-server-wso2

Thanks & Regards,
Johann.

-- 

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *

-- 
You received this message because you are subscribed to the Google Groups
"WSO2 Documentation Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to documentation+unsubscr...@wso2.com.
For more options, visit https://groups.google.com/a/wso2.com/d/optout.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 IoT Server 3.1.0 RC

[Pubudu D.P]

Guys,

Found another blocker. Please fix this[1] as well.

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

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 18, 2017 at 12:21 PM, Geeth Munasinghe  wrote:

> Hi all,
>
> We are closing this vote for RC1, We will proceed with new RC soon.
>
> Thanks
> Geeth
>
> On Tue, Jul 18, 2017 at 12:20 PM, Geeth Munasinghe  wrote:
>
>> -1,
>>
>>  Due to packing old registry versions which are having some security
>> issues.
>>
>> Thanks
>> Geeth
>>
>> On Mon, Jul 17, 2017 at 8:20 AM, Madhawa Perera 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> We are pleased to announce the release candidate of WSO2 IoT Server
>>> 3.1.0.
>>>
>>> This is the Release Candidate version 1 of the WSO2  IoT Server 3 .1.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> Known issues : https://github.com/wso2/produc
>>> t-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-beta2
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-iots/tree/v3.1.0-RC
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thank you
>>> Best Regards,
>>> *WSO2 IoT Team*
>>>
>>> --
>>> Madhawa Perera
>>> *Software Engineer*
>>> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
>>> <%2B94%20%280%29%20773%20451194>
>>> madha...@wso2.com
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 IoT Team Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to iot-group+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>
>>
>>
>> --
>> *Geeth Munasinghe*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226 <+94%2077%20791%201226>
>>
>> 
>>
>
>
>
> --
> *Geeth Munasinghe*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226 <+94%2077%20791%201226>
>
> 
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.17 RC2

[Lahiru Manohara]

The provided public certificate in the default keystore is expired. It is
issued only for 3 months and it is already expired. Please update the
certificate with a longer duration.

[x] Broken - Do not release

Best Regards,

On Fri, Jul 14, 2017 at 11:40 PM, Rushmin Fernando  wrote:

> Built IS 5.x.x branch with the integrations tests.
>
> Manually tested user management.
>   1) In tenants
>   2) Using the embedded LDAP primary user store
>   3) Using a JDBC secondary user store
>
>
> Found no issues.
>
> [ x] Stable  - Go ahead and release
>
> On Fri, Jul 14, 2017 at 2:04 PM, Chandana Napagoda 
> wrote:
>
>> Hi All,
>>
>> This is the 2nd release candidate of WSO2 Carbon Kernel 4.4.17.
>>
>> This release fixes the following issues
>> https://github.com/wso2/carbon-kernel/milestone/15?closed=1
>>
>> Please download and test your products with kernel 4.4.17 RC2 and vote.
>> The vote will be open for 72 hours or as long as needed.
>>
>> Maven staging repository:
>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1184/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.17-rc2
>>
>> [ ] Broken - Do not release (explain why)
>> [ ] Stable  - Go ahead and release
>>
>> Thank you
>> Platform Team
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <+94%2071%20816%209299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com 
>> | http://chandana.napagoda.com *
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> *
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lahiru Manohara*
*Software Engineer*
Mobile: +94716561576
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enrich Json with new elements not working for me .Please guide.

[Rajjaz Mohammed]

Hi Aditya,

You have to add the response back to body

http://ws.apache.org/ns/synapse; name="eg1" context="/eg1">
   
  
 
 

 
 

   Home


 
 

 
 


 
 
 
  
  
  
   


I have tried this API

*Request*

 {
"id" : "1",
"make" : "NAHB"
}

*Response*

{
   "id": 1,
   "make": "NAHB",
   "name": "Home"
}




On Tue, Jul 18, 2017 at 1:41 PM, Vijitha Ekanayake 
wrote:

> Hi Aditya,
>
> I could try with the following configurations which worked for me.
>
> 
> http://ws.apache.org/ns/synapse;
>  name="EnrichAPI"
>  context="/test">
>
>   
>  
>  expression="fn:concat('name',$ctx:name,
> '/name')"
>type="OM"/>
>   type="OM"/>
>  
> 
> 
>  
>  
> 
> 
>  
>  
>   
>   
>
> 
>
>
> Thanks.
>
> On Tue, Jul 18, 2017 at 12:41 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Hi,
>>
>> Forgot to mention .
>> I cannot use payload factory here because this is just an example I
>> created. and my actual data to be enriched is a huge json response from a
>> backend service.
>>
>> With Regards,
>> Aditya
>>
>>
>>
>>
>> -- Forwarded message --
>> From: aditya shivankar 
>> Date: Tue, Jul 18, 2017 at 12:35 PM
>> Subject: Enrich Json with new elements not working for me .Please guide.
>> To: dev@wso2.org
>>
>>
>> Hi,
>>
>> Enrich Json with new elements not working for me .Please guide.
>>
>> Input request :
>>
>> {
>> "id" : "1",
>> "make" : "NAHB"
>> }
>> I the wso2 flow named eg1.xml . I am trying to enrich the incoming json
>> request with new element "name"
>>
>> processing xml: (eg1.xml)
>>
>> 
>> http://ws.apache.org/ns/synapse;>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Home
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>> current output :
>> {
>> "id" : "1",
>> "make" : "NAHB"
>> }
>>
>> Desired output :
>>
>> {
>> "id" : "1",
>> "make" : "NAHB"
>> "name" : "Home"
>> }
>>
>> logger output :
>>
>> Logger1 output(log level full) :
>> LogMediator To: /eg1/hi, MessageID: 
>> urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
>> Direction: request, Payload:
>> {
>> "id": "1",
>> "make": "NAHB"
>> }
>>
>> Logger2 output :
>> LogMediator msg1 =
>> 
>> 1
>> NAHB
>> 
>>
>> Logger3 output :
>> LogMediator msg2 =
>> 
>> 1
>> NAHB
>> Home
>> 
>>
>> Logger4 output(log level full) :
>> LogMediator To: /eg1/hi, MessageID: 
>> urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
>> Direction: request, Payload:
>> {
>> "id": "1",
>> "make": "NAHB"
>> }
>>
>> Postman output :
>> {
>> "id": "1",
>> "make": "NAHB"
>> }
>>
>> Regards,
>> Aditya
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thank you
Best Regards

*Rajjaz HM*
Software Engineer
Platform Extension Team
WSO2 Inc. 
lean | enterprise | middleware
Mobile | +94752833834|+94777226874
Email   | raj...@wso2.com
LinkedIn  | Blogger
 | WSO2 Profile

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enrich Json with new elements not working for me .Please guide.

[Vijitha Ekanayake]

Hi Aditya,

I could try with the following configurations which worked for me.


http://ws.apache.org/ns/synapse;
 name="EnrichAPI"
 context="/test">
   
  
 
 
 
 


 
 


 
 
  
  
   



Thanks.

On Tue, Jul 18, 2017 at 12:41 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Hi,
>
> Forgot to mention .
> I cannot use payload factory here because this is just an example I
> created. and my actual data to be enriched is a huge json response from a
> backend service.
>
> With Regards,
> Aditya
>
>
>
>
> -- Forwarded message --
> From: aditya shivankar 
> Date: Tue, Jul 18, 2017 at 12:35 PM
> Subject: Enrich Json with new elements not working for me .Please guide.
> To: dev@wso2.org
>
>
> Hi,
>
> Enrich Json with new elements not working for me .Please guide.
>
> Input request :
>
> {
> "id" : "1",
> "make" : "NAHB"
> }
> I the wso2 flow named eg1.xml . I am trying to enrich the incoming json
> request with new element "name"
>
> processing xml: (eg1.xml)
>
> 
> http://ws.apache.org/ns/synapse;>
> 
> 
> 
> 
> 
> 
> 
> 
> Home
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
> current output :
> {
> "id" : "1",
> "make" : "NAHB"
> }
>
> Desired output :
>
> {
> "id" : "1",
> "make" : "NAHB"
> "name" : "Home"
> }
>
> logger output :
>
> Logger1 output(log level full) :
> LogMediator To: /eg1/hi, MessageID: 
> urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
> Direction: request, Payload:
> {
> "id": "1",
> "make": "NAHB"
> }
>
> Logger2 output :
> LogMediator msg1 =
> 
> 1
> NAHB
> 
>
> Logger3 output :
> LogMediator msg2 =
> 
> 1
> NAHB
> Home
> 
>
> Logger4 output(log level full) :
> LogMediator To: /eg1/hi, MessageID: 
> urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
> Direction: request, Payload:
> {
> "id": "1",
> "make": "NAHB"
> }
>
> Postman output :
> {
> "id": "1",
> "make": "NAHB"
> }
>
> Regards,
> Aditya
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vijitha Ekanayake
Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] APIs for Local and Outbound Authenticators

[Johann Nallathamby]

Hi,

I was trying to find proper documentation for extending the Basic Auth
authenticator and implementing conditional step up authentication with
TOTP. However I couldn't find proper documentation for extending local
authenticators. The only documentation I found for customizing
authenticators in IS 5.3.0 is [1]. However that mostly talks about
federated authenticators. [2] was a better reference for me. I think we
have to improve the categorization of local authenticators, federated
authenticators and request-path authenticators, explain in which scenario
to use what in our official documentation.

[1]
https://docs.wso2.com/display/IS530/Writing+a+Custom+Federated+Authenticator
[2]
https://dzone.com/articles/custom-authenticator-for-wso2-identity-server-wso2

Thanks & Regards,
Johann.

-- 

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enrich Json with new elements not working for me .Please guide.

[aditya shivankar]

Hi,

Forgot to mention .
I cannot use payload factory here because this is just an example I
created. and my actual data to be enriched is a huge json response from a
backend service.

With Regards,
Aditya




-- Forwarded message --
From: aditya shivankar 
Date: Tue, Jul 18, 2017 at 12:35 PM
Subject: Enrich Json with new elements not working for me .Please guide.
To: dev@wso2.org


Hi,

Enrich Json with new elements not working for me .Please guide.

Input request :

{
"id" : "1",
"make" : "NAHB"
}
I the wso2 flow named eg1.xml . I am trying to enrich the incoming json
request with new element "name"

processing xml: (eg1.xml)


http://ws.apache.org/ns/synapse;>








Home















current output :
{
"id" : "1",
"make" : "NAHB"
}

Desired output :

{
"id" : "1",
"make" : "NAHB"
"name" : "Home"
}

logger output :

Logger1 output(log level full) :
LogMediator To: /eg1/hi, MessageID:
urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
Direction: request, Payload:
{
"id": "1",
"make": "NAHB"
}

Logger2 output :
LogMediator msg1 =

1
NAHB


Logger3 output :
LogMediator msg2 =

1
NAHB
Home


Logger4 output(log level full) :
LogMediator To: /eg1/hi, MessageID:
urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8,
Direction: request, Payload:
{
"id": "1",
"make": "NAHB"
}

Postman output :
{
"id": "1",
"make": "NAHB"
}

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

[Dev] Enrich Json with new elements not working for me .Please guide.

[aditya shivankar]

Hi,

Enrich Json with new elements not working for me .Please guide.

Input request :

{
"id" : "1",
"make" : "NAHB"
}
I the wso2 flow named eg1.xml . I am trying to enrich the incoming json
request with new element "name"

processing xml: (eg1.xml)


http://ws.apache.org/ns/synapse;>








Home















current output :
{
"id" : "1",
"make" : "NAHB"
}

Desired output :

{
"id" : "1",
"make" : "NAHB"
"name" : "Home"
}

logger output :

Logger1 output(log level full) :
LogMediator To: /eg1/hi, MessageID:
urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8, Direction: request, Payload:
{
"id": "1",
"make": "NAHB"
}

Logger2 output :
LogMediator msg1 =

1
NAHB


Logger3 output :
LogMediator msg2 =

1
NAHB
Home


Logger4 output(log level full) :
LogMediator To: /eg1/hi, MessageID:
urn:uuid:2f627daf-ac9c-4492-84ea-2736670724e8, Direction: request, Payload:
{
"id": "1",
"make": "NAHB"
}

Postman output :
{
"id": "1",
"make": "NAHB"
}

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

Re: [Dev] [VOTE] Release WSO2 IoT Server 3.1.0 RC

[Geeth Munasinghe]

Hi all,

We are closing this vote for RC1, We will proceed with new RC soon.

Thanks
Geeth

On Tue, Jul 18, 2017 at 12:20 PM, Geeth Munasinghe  wrote:

> -1,
>
>  Due to packing old registry versions which are having some security
> issues.
>
> Thanks
> Geeth
>
> On Mon, Jul 17, 2017 at 8:20 AM, Madhawa Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate of WSO2 IoT Server 3.1.0.
>>
>> This is the Release Candidate version 1 of the WSO2  IoT Server 3 .1.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Known issues : https://github.com/wso2/produc
>> t-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-beta2
>>
>> Source and binary distribution files:
>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-iots/tree/v3.1.0-RC
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thank you
>> Best Regards,
>> *WSO2 IoT Team*
>>
>> --
>> Madhawa Perera
>> *Software Engineer*
>> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
>> <%2B94%20%280%29%20773%20451194>
>> madha...@wso2.com
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> *Geeth Munasinghe*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226 <+94%2077%20791%201226>
>
> 
>



-- 
*Geeth Munasinghe*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226


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

Re: [Dev] [VOTE] Release WSO2 IoT Server 3.1.0 RC

[Geeth Munasinghe]

-1,

 Due to packing old registry versions which are having some security
issues.

Thanks
Geeth

On Mon, Jul 17, 2017 at 8:20 AM, Madhawa Perera  wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate of WSO2 IoT Server 3.1.0.
>
> This is the Release Candidate version 1 of the WSO2  IoT Server 3 .1.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> Known issues : https://github.com/wso2/product-iots/issues?q=is%
> 3Aopen+is%3Aissue+label%3A3.1.0-beta2
>
> Source and binary distribution files:
> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC
>
> The tag to be voted upon:
> https://github.com/wso2/product-iots/tree/v3.1.0-RC
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thank you
> Best Regards,
> *WSO2 IoT Team*
>
> --
> Madhawa Perera
> *Software Engineer*
> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
> <%2B94%20%280%29%20773%20451194>
> madha...@wso2.com
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 IoT Team Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iot-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
*Geeth Munasinghe*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226


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