[Dev] [AF] Fixing (APPFAC-3217) - Support APIM group subscription in App Factory

2016-01-12 Thread Amalka Subasinghe
Hi,

Currently only the app owner allows to subscribed to an API, generate keys
and see subscribed APIs, where other users are not allowed as showed in the
below table.


Subscribe to API Generate Keys View subscribed APIs in AF side View Prod
keys in AF side View Sandbox keys in AF side App owner Y Y Y Y Y Developer



Y QA



Y DevOps


Y Y
We want to improve the AF - APIM integration as follows. So we need
implement $subject.
1. making both app owner and developer can subscribe to an API and generate
keys
2. making all users to see subscribed API per application


Subscribe to API Generate Keys View subscribed APIs in AF side View Prod
keys in AF side View Sandbox keys in AF side App owner Y Y Y Y Y Developer Y
Y Y
Y QA

Y
Y DevOps

Y Y Y
*Things to do:*

1. All the users of a particular app we need to maintain as a group.

In APIM side they uses http://wso2.org/claims/organization claim to group
the users. We have to set this claim (eg: app key as the value of the
claim) when appowner or developer try to click on 'Go to API Manager'
button.
Currently we use a role app_appName to group the users of a particular
application in AF. If we use this we have to implement a custom grouping
extractor to get the users of a particular group.


*Issues: *a. Since we don't set the claim for QA and DevOps users, they
can't view subscribed APIs in AF side, and If we add the claim they also
will be able to subscribe to APIs and generate keys. So we need to find a
way to view subscribed api for a particular application by QA and Devops
users.
b. With this implementation Developer can see prod keys also.


2. Make Go to API Manager and Sync Keys buttons enabled only to appowner
and developer.
For this we can use resource permissions we already have.


3. Need to improve/test all the rest calls we do with APIM to work with
groups and fix if there's any issue.

   - Login - When user clicks on 'Go to API Manager' button of a particular
   app, it should login to APIM and show the subscribed APIs, listed under
   selected application.
   - Create application
   - Remove application
   - Get published APIs by application
   - List subscription
   - Get applications

[1] https://wso2.org/jira/browse/APPFAC-3217

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


[Dev] WSO2 Committers += Samiyuru Senarathne

2016-01-12 Thread Afkham Azeez
Hi folks,
It's my pleasure to welcome Samiyuru to the WSO2 committers group. As a
member of the Carbon kernel team, Samiyuru is the main contributor to the
WSO2 Microservices Server product & has made many valuable contributions to
MSS as well as the Carbon Kernel.

Samiyuru,
Thanks for all your valuable contributions. I am relieved that now you can
directly commit yourself & I no longer have to review and merge your PRs :)
Congratulations & keep up the good work.

Thanks
Azeez

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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


[Dev] Class Not Found error when shutting down the Dashboard Server

2016-01-12 Thread Lalanke Athauda
Hi,
When I shut down the Dashboard Server we get following error in console.

[2016-01-12 14:16:06,333]  INFO {org.wso2.carbon.core.ServerManagement} -
All deployment tasks have been completed.
[2016-01-12 14:16:06,334]  INFO {org.wso2.carbon.core.ServerManagement} -
Waiting for server task completion...
Exception in thread "Thread-12" java.lang.NoClassDefFoundError: Could not
initialize class org.wso2.carbon.registry.indexing.RegistryConfigLoader
at
org.wso2.carbon.registry.indexing.IndexingManager.(IndexingManager.java:60)
at
org.wso2.carbon.registry.indexing.IndexingManager.getInstance(IndexingManager.java:71)
at
org.wso2.carbon.registry.indexing.internal.IndexingServiceComponent$1.startingShutdown(IndexingServiceComponent.java:84)
at
org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)
at
org.wso2.carbon.core.ServerManagement.startMaintenanceForShutDown(ServerManagement.java:97)
at
org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:878)
at
org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:901)

I checked is the respective jar file in plugins directory, and it was there.
Then I checked is the corresponding bundle active using osgi console and it
was also in ACTIVE state.
Any idea to solve this problem. Highly appreciate your suggestions.
Thanks.

-- 
Lalanke Athauda
Software Engineer
WSO2 Inc.
Mobile: 0772264301
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Class Not Found error when shutting down the Dashboard Server

2016-01-12 Thread Rajith Vitharana
Hi Lalanke,

NoClassDefFoundError not necessarily means class file is not found. it can
be initialization error as well. In that case there may be Exceptions
occurred prior to this. If you see such exception, try to resolve that
first, and then this will be resolved then, Reference -
http://stackoverflow.com/questions/34413/why-am-i-getting-a-noclassdeffounderror-in-java

Thanks,

On Tue, Jan 12, 2016 at 2:41 PM, Lalanke Athauda  wrote:

> Hi,
> When I shut down the Dashboard Server we get following error in console.
>
> [2016-01-12 14:16:06,333]  INFO {org.wso2.carbon.core.ServerManagement} -
> All deployment tasks have been completed.
> [2016-01-12 14:16:06,334]  INFO {org.wso2.carbon.core.ServerManagement} -
> Waiting for server task completion...
> Exception in thread "Thread-12" java.lang.NoClassDefFoundError: Could not
> initialize class org.wso2.carbon.registry.indexing.RegistryConfigLoader
> at
> org.wso2.carbon.registry.indexing.IndexingManager.(IndexingManager.java:60)
> at
> org.wso2.carbon.registry.indexing.IndexingManager.getInstance(IndexingManager.java:71)
> at
> org.wso2.carbon.registry.indexing.internal.IndexingServiceComponent$1.startingShutdown(IndexingServiceComponent.java:84)
> at
> org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)
> at
> org.wso2.carbon.core.ServerManagement.startMaintenanceForShutDown(ServerManagement.java:97)
> at
> org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:878)
> at
> org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:901)
>
> I checked is the respective jar file in plugins directory, and it was
> there.
> Then I checked is the corresponding bundle active using osgi console and
> it was also in ACTIVE state.
> Any idea to solve this problem. Highly appreciate your suggestions.
> Thanks.
>
> --
> Lalanke Athauda
> Software Engineer
> WSO2 Inc.
> Mobile: 0772264301
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Vitharana

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


[Dev] Exception when adding registry attribute which have long string value

2016-01-12 Thread Rukshan Premathunga
Hi all,

When APIM adding API, which contain the long description, console get print
following error.
It seems length of the attribute get exceeded.

So what would be the proper way to handle this?
Should this handle at the registry side or at the client side?

error log:

[2016-01-12 13:53:44,505]  INFO - CarbonAuthenticationUtil
'admin@carbon.super [-1234]' logged in at [2016-01-12 13:53:44,504+0530]
[2016-01-12 13:53:49,007] ERROR - SolrCore
org.apache.solr.common.SolrException: Exception writing document id
/_system/governance/apimgt/applicationdata/provider/admin/17/17/apitenantId-1234
to the index; possible analysis error.
at
org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:167)
at
org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69)
at
org.apache.solr.update.processor.UpdateRequestProcessor.processAdd(UpdateRequestProcessor.java:51)
at
org.apache.solr.update.processor.DistributedUpdateProcessor.doLocalAdd(DistributedUpdateProcessor.java:955)
at
org.apache.solr.update.processor.DistributedUpdateProcessor.versionAdd(DistributedUpdateProcessor.java:1110)
at
org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:706)
at
org.apache.solr.handler.loader.XMLLoader.processUpdate(XMLLoader.java:250)
at org.apache.solr.handler.loader.XMLLoader.load(XMLLoader.java:177)
at
org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:98)
at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
at
org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.request(EmbeddedSolrServer.java:179)
at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:135)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:174)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:139)
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:153)
at
org.wso2.carbon.registry.indexing.solr.SolrClient.addDocument(SolrClient.java:292)
at
org.wso2.carbon.registry.indexing.indexer.IndexDocumentCreator.createIndexDocument(IndexDocumentCreator.java:123)
at
org.wso2.carbon.registry.indexing.AsyncIndexer$IndexingTask.createIndexDocument(AsyncIndexer.java:212)
at
org.wso2.carbon.registry.indexing.AsyncIndexer$IndexingTask.run(AsyncIndexer.java:196)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
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)
Caused by: java.lang.IllegalArgumentException: Document contains at least
one immense term in field="overview_description_s" (whose UTF8 encoding is
longer than the max length 32766), all of which were skipped.  Please
correct the analyzer to not produce such terms.  The prefix of the first
immense term is: '[38, 108, 116, 59, 63, 120, 109, 108, 32, 118, 101, 114,
115, 105, 111, 110, 61, 38, 113, 117, 111, 116, 59, 49, 46, 48, 38, 113,
117, 111]...', original message: bytes can be at most 32766 in length; got
33092
at
org.apache.lucene.index.DefaultIndexingChain$PerField.invert(DefaultIndexingChain.java:670)
at
org.apache.lucene.index.DefaultIndexingChain.processField(DefaultIndexingChain.java:344)
at
org.apache.lucene.index.DefaultIndexingChain.processDocument(DefaultIndexingChain.java:300)
at
org.apache.lucene.index.DocumentsWriterPerThread.updateDocument(DocumentsWriterPerThread.java:232)
at
org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:458)
at org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1363)
at
org.apache.solr.update.DirectUpdateHandler2.addDoc0(DirectUpdateHandler2.java:239)
at
org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:163)
... 25 more
Caused by:
org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes
can be at most 32766 in length; got 33092
at org.apache.lucene.util.BytesRefHash.add(BytesRefHash.java:284)
at org.apache.lucene.index.TermsHashPerField.add(TermsHashPerField.java:154)
at
org.apache.lucene.index.DefaultIndexingChain$PerField.invert(DefaultIndexingChain.java:660)
... 32 more


Thanks and Regards.

-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Invitation: Review - Packaging for Puppet Modules @ Tue Jan 12, 2016 3:30pm - 4pm (isu...@wso2.com)

2016-01-12 Thread Isuru Haththotuwa
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20160112T10Z
DTEND:20160112T103000Z
DTSTAMP:20160112T094217Z
ORGANIZER;CN=Isuru Haththotuwa:mailto:isu...@wso2.com
UID:eakrum706vrgsvkb5u0qpm1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sajith Kariyawasam;X-NUM-GUESTS=0:mailto:saj...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Imesh Gunaratne;X-NUM-GUESTS=0:mailto:im...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=mal...@wso2.com;X-NUM-GUESTS=0:mailto:mal...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Isuru Haththotuwa;X-NUM-GUESTS=0:mailto:isu...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;C
 N="LK 5th Floor Meeting Room - Garage Ext:1005550";X-NUM-GUESTS=0:mailto:ws
 o2.com_2d3431383635313232393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Pubudu Gunatilaka;X-NUM-GUESTS=0:mailto:pubu...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Akila Ravihansa Perera;X-NUM-GUESTS=0:mailto:raviha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Chamila De Alwis;X-NUM-GUESTS=0:mailto:chami...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Vishanth Balasubramaniam;X-NUM-GUESTS=0:mailto:vishan...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Nishadi Kirielle;X-NUM-GUESTS=0:mailto:nish...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
CREATED:20160112T094104Z
DESCRIPTION:This event has a Google Hangouts video call.\nJoin: https://plu
 s.google.com/hangouts/_/wso2.com/review?hceid=aXN1cnVoQHdzbzIuY29t.eakrum70
 6vrgsvkb5u0qpm1294&hs=121\n\nView your event at https://www.google.com/cale
 ndar/event?action=VIEW&eid=ZWFrcnVtNzA2dnJnc3ZrYjV1MHFwbTEyOTQgZGV2QHdzbzIu
 b3Jn&tok=MTUjaXN1cnVoQHdzbzIuY29tOGUzYTlhMmM2YWRhOGMyODE2NTAyYTQyYzllZjBkZT
 g0ZjQwYmQ0OQ&ctz=Asia/Colombo&hl=en.
LAST-MODIFIED:20160112T094217Z
LOCATION:LK 5th Floor Meeting Room - Garage Ext:1005550
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Review - Packaging for Puppet Modules
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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


Re: [Dev] Class Not Found error when shutting down the Dashboard Server

2016-01-12 Thread Lalanke Athauda
Hi Rajith,
Thanks for your quick reply. I checked the logs and there are no other
errors or exceptions. This is my complete log.

[2016-01-12 15:01:05,189]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...
[2016-01-12 15:01:05,189]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Linux 3.13.0-74-generic, amd64
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/usr/lib/jvm/java-7-oracle/jre
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.7.0_80
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 24.80-b11,Oracle Corporation
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
/home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
/home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT/tmp
[2016-01-12 15:01:05,190]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
lalanke, en-US, Asia/Colombo
[2016-01-12 15:01:05,261]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
Carbon is configured to use the default keystore (wso2carbon.jks). To
maximize security when deploying to a production environment, configure a
new keystore with a unique password in the production server profile.
[2016-01-12 15:01:05,311]  WARN
{org.wso2.carbon.identity.notification.mgt.NotificationMgtConfigBuilder} -
Secret Resolver is not present. Will not resolve encryptions in config file
[2016-01-12 15:01:06,108]  WARN
{org.wso2.carbon.registry.core.config.RegistryConfigurationProcessor} -
Could not find the handler class
org.wso2.jaggery.scxml.registry.handlers.JaggeryExecutorHandler. This
handler will not be registered. All handler and filter classes should be in
the class path of the Registry.
[2016-01-12 15:01:06,141]  INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
Registry in 31ms
[2016-01-12 15:01:06,200]  INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Registry Mode: READ-WRITE
[2016-01-12 15:01:06,758]  INFO
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon
UserStoreMgtDSComponent activated successfully.
[2016-01-12 15:01:09,784]  INFO {org.apache.catalina.startup.TaglibUriRule}
-  TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined
[2016-01-12 15:01:10,290]  INFO
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
-  User Store Configuration Deployer initiated.
[2016-01-12 15:01:10,291]  INFO
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
-  User Store Configuration Deployer initiated.
[2016-01-12 15:01:10,870]  INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
service: UserInformationRecoveryService {super-tenant}
[2016-01-12 15:01:11,553]  INFO
{org.wso2.carbon.core.init.CarbonServerManager} -  Repository   :
/home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT/repository/deployment/server/
[2016-01-12 15:01:11,608]  INFO
{org.wso2.carbon.core.multitenancy.eager.TenantLoadingConfig} -  Switching
to default mode : Tenant lazy loading mechanism has been activated...
[2016-01-12 15:01:11,621]  INFO
{org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
Permission cache updated for tenant -1234
[2016-01-12 15:01:11,721]  INFO
{org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore}
-  Thread pool size for session persistent consumer : 100
[2016-01-12 15:01:11,729]  INFO
{org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore}
-  Session Data Operations CleanUp Task of Authentication framework is not
enabled.
[2016-01-12 15:01:11,813]  INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS
port   : 9443
[2016-01-12 15:01:11,813]  INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP
port: 9763
[2016-01-12 15:01:11,847]  INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
service: echo {super-tenant}
[2016-01-12 15:01:11,919]  INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
service: Version {super-tenant}
[2016-01-12 15:01:12,260]  INFO
{org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager}
-  TenantConfig.properties file loaded from authentication endpoint webapp
[2016-01-12 15:01:12,381]  INFO
{org.apache.jasper.compiler.TldLocationsCache} -  At least one JAR was
scanned for TLDs yet contained no TLDs. Enable debug logging for this
l

[Dev] Subscription issue of new REST API in API Manager 1.10.0

2016-01-12 Thread Malintha Amarasinghe
Hi All,

We have identified an issue in new Store REST API in API Manager 1.10.0 as
follows.

   1. A new user is created using the admin console and added subscriber
   permission ( OR a user is signed up using Store web app)
   2. Now without logging in to store at least once, the user invokes the
   Store REST API. (say, to to create an Application)
   3. We can see that the request is failed.

If the user try invoking the REST API after logging in to the Store at
least once, the request will be successful.

The reason for the issue is that, the user (subscriber) is added to
AM_SUBSCRIBER table in login flow. When the user invoke the REST API
without logging in to Store at lease once, the request fails as the
subscriber is not yet added to AM_SUBSCRIBER table.

To solve the above issue we are looking into following choices.

   1. At the point the user is authenticated in REST API, we create a JWT
   and add it to CXF message context with additional information (including
   whether the subscriber is already added to AM_SUBSCRIBER or not). Then we
   use a separate CXF interceptor (say PostAuthenticationInterceptor) to
   retrieve the JWT from the message context, read required parameters from it
   and add the user to the AM_SUBSCRIBER if he is not added already.
   2. Similar approach to the above method without using JWT. We set the
   authenticated user to the carbon context. It is read by a separate
   CXF Interceptor, and the user is added to AM_SUBSCRIBER if he is not yet
   already added.

Both choices are based on using a separate Interceptor so we have
following advantages.

   1. We use a common set of Authentication interceptors for both Publisher
   and Store REST APIs but we don't need to execute this flow for Publisher
   REST API. We can easily do it by removing
   the PostAuthenticationInterceptor from beans.xml in Publisher REST API web
   app and keep it only in Store beans.xml.
   2. For any authenticated mechanism (Basic or OAuth or any new
   authentication mechanism) we need this flow to be executed in Store REST
   API. This can be easily achieved using an Interceptor.

Appreciate your thoughts on this.

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

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


[Dev] Updated Invitation: Review - Packaging for Puppet Modules @ Tue Jan 12, 2016 4:15pm - 4:45pm (isu...@wso2.com)

2016-01-12 Thread isuruh
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20160112T104500Z
DTEND:20160112T111500Z
DTSTAMP:20160112T100648Z
ORGANIZER;CN=Isuru Haththotuwa:mailto:isu...@wso2.com
UID:eakrum706vrgsvkb5u0qpm1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sajith Kariyawasam;X-NUM-GUESTS=0:mailto:saj...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Imesh Gunaratne;X-NUM-GUESTS=0:mailto:im...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=mal...@wso2.com;X-NUM-GUESTS=0:mailto:mal...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Isuru Haththotuwa;X-NUM-GUESTS=0:mailto:isu...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE;CN="LK 5th Floor Meeting Room - Garage Ext:1005550";X-NUM-GUESTS=0:mailt
 o:wso2.com_2d3431383635313232393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Pubudu Gunatilaka;X-NUM-GUESTS=0:mailto:pubu...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Akila Ravihansa Perera;X-NUM-GUESTS=0:mailto:raviha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Chamila De Alwis;X-NUM-GUESTS=0:mailto:chami...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Vishanth Balasubramaniam;X-NUM-GUESTS=0:mailto:vishan...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Nishadi Kirielle;X-NUM-GUESTS=0:mailto:nish...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
CREATED:20160112T094104Z
DESCRIPTION:This event has a Google Hangouts video call.\nJoin: https://plu
 s.google.com/hangouts/_/wso2.com/review?hceid=aXN1cnVoQHdzbzIuY29t.eakrum70
 6vrgsvkb5u0qpm1294&hs=121\n\nView your event at https://www.google.com/cale
 ndar/event?action=VIEW&eid=ZWFrcnVtNzA2dnJnc3ZrYjV1MHFwbTEyOTQgZGV2QHdzbzIu
 b3Jn&tok=MTUjaXN1cnVoQHdzbzIuY29tOGUzYTlhMmM2YWRhOGMyODE2NTAyYTQyYzllZjBkZT
 g0ZjQwYmQ0OQ&ctz=Asia/Colombo&hl=en.
LAST-MODIFIED:20160112T100648Z
LOCATION:LK 5th Floor Meeting Room - Garage Ext:1005550
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Review - Packaging for Puppet Modules
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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


[Dev] Canceled Event: Review - Packaging for Puppet Modules @ Tue Jan 12, 2016 4:15pm - 4:45pm (isu...@wso2.com)

2016-01-12 Thread isuruh
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VEVENT
DTSTART:20160112T104500Z
DTEND:20160112T111500Z
DTSTAMP:20160112T101007Z
ORGANIZER;CN=Isuru Haththotuwa:mailto:isu...@wso2.com
UID:eakrum706vrgsvkb5u0qpm1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;CN=dev@ws
 o2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
CREATED:20160112T094104Z
DESCRIPTION:This event has a Google Hangouts video call.\nJoin: https://plu
 s.google.com/hangouts/_/wso2.com/review?hceid=aXN1cnVoQHdzbzIuY29t.eakrum70
 6vrgsvkb5u0qpm1294&hs=121\n
LAST-MODIFIED:20160112T101006Z
LOCATION:LK 5th Floor Meeting Room - Garage Ext:1005550
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Review - Packaging for Puppet Modules
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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


Re: [Dev] Subscription issue of new REST API in API Manager 1.10.0

2016-01-12 Thread Thilini Cooray
Hi Malintha,

Can you please explain me the following?

In the API Manager store UI or jaggery APIs, users required to login prior
to create applications or subscribe to APIs etc.
In the store REST API we are passing an authentication header for invoking
APIs.
Have we eliminated from user login in this approach?

Thanks.


On Tue, Jan 12, 2016 at 3:15 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> We have identified an issue in new Store REST API in API Manager 1.10.0 as
> follows.
>
>1. A new user is created using the admin console and added subscriber
>permission ( OR a user is signed up using Store web app)
>2. Now without logging in to store at least once, the user invokes the
>Store REST API. (say, to to create an Application)
>3. We can see that the request is failed.
>
> If the user try invoking the REST API after logging in to the Store at
> least once, the request will be successful.
>
> The reason for the issue is that, the user (subscriber) is added to
> AM_SUBSCRIBER table in login flow. When the user invoke the REST API
> without logging in to Store at lease once, the request fails as the
> subscriber is not yet added to AM_SUBSCRIBER table.
>
> To solve the above issue we are looking into following choices.
>
>1. At the point the user is authenticated in REST API, we create a JWT
>and add it to CXF message context with additional information (including
>whether the subscriber is already added to AM_SUBSCRIBER or not). Then we
>use a separate CXF interceptor (say PostAuthenticationInterceptor) to
>retrieve the JWT from the message context, read required parameters from it
>and add the user to the AM_SUBSCRIBER if he is not added already.
>2. Similar approach to the above method without using JWT. We set the
>authenticated user to the carbon context. It is read by a separate
>CXF Interceptor, and the user is added to AM_SUBSCRIBER if he is not yet
>already added.
>
> Both choices are based on using a separate Interceptor so we have
> following advantages.
>
>1. We use a common set of Authentication interceptors for both
>Publisher and Store REST APIs but we don't need to execute this flow for
>Publisher REST API. We can easily do it by removing
>the PostAuthenticationInterceptor from beans.xml in Publisher REST API web
>app and keep it only in Store beans.xml.
>2. For any authenticated mechanism (Basic or OAuth or any new
>authentication mechanism) we need this flow to be executed in Store REST
>API. This can be easily achieved using an Interceptor.
>
> Appreciate your thoughts on this.
>
> Thanks,
> Malintha
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

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

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


[Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Nirmal Fernando
Hi All,

It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He has
been a key contributor to the *WSO2 Machine Learner *Product and in
recognition of his work, he had been voted as a WSO2 Committer.

Congratulations Fazlan and keep up the good work!

-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Malintha Adikari
Congratulations..!!!

On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando  wrote:

> Hi All,
>
> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He
> has been a key contributor to the *WSO2 Machine Learner *Product and in
> recognition of his work, he had been voted as a WSO2 Committer.
>
> Congratulations Fazlan and keep up the good work!
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Mobile: +94 71 2312958
Blog:http://malinthas.blogspot.com
Page:   http://about.me/malintha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Ashen Weerathunga
Congratulations Fazlan!!! :)

On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari  wrote:

> Congratulations..!!!
>
> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He
>> has been a key contributor to the *WSO2 Machine Learner *Product and in
>> recognition of his work, he had been voted as a WSO2 Committer.
>>
>> Congratulations Fazlan and keep up the good work!
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile: +94 71 2312958
> Blog:http://malinthas.blogspot.com
> Page:   http://about.me/malintha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn:
*http://lk.linkedin.com/in/ashenweerathunga
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] I am getting the following error in the console and unable to get resource

2016-01-12 Thread Pramod Thakur
Hi All,

Can i get the source code location for wso2 api manager.


I have created a tenant xyz.com and a user excha...@abc.com.

To get the access token i am passing the following
 username:  excha...@abc.com
 password: password.


I have also created a Customhandler in the api manager which will add a
tenantdomain in the header from the url by splitting the url
https://10.104.204.110:8243/t/xyz.com/sdp/v1/groups
and set the domain as xyz.com which will be used during authentication as
we are appening the tenantdomain to identify the user of that domain like
below.

username: excha...@abc.com.xyz.com
password: password.

Its working fine but once i got the token during validation of token i am
getting as null instead of token in x-jwt-token.

The error in the console is as follows.



[2016-01-12 09:21:54,850]  INFO - APIKeyValidator Token
90e0516d4c3b5e8b825746aef1a19 expired.
[2016-01-12 09:21:54,851]  WARN - APIAuthenticationHandler API
authentication failure due to Invalid Credentials
[2016-01-12 09:22:02,476]  INFO - PermissionUpdater Permission cache
updated for tenant -1234
[2016-01-12 09:22:02,490]  INFO - CarbonAuthenticationUtil
'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,490+0530]
[2016-01-12 09:22:02,567]  INFO - CarbonAuthenticationUtil
'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,567+0530]
[2016-01-12 09:22:02,622]  INFO - PermissionUpdater Permission cache
updated for tenant -1234
[2016-01-12 09:22:02,633]  INFO - CarbonAuthenticationUtil
'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,633+0530]
[2016-01-12 09:22:11,443] ERROR - KeyStoreManager Error when retrieving the
system governance registry
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to
obtain the user realm for tenant: -1.
at
org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:304)
at
org.wso2.carbon.registry.core.session.UserRegistry.access$100(UserRegistry.java:61)
at
org.wso2.carbon.registry.core.session.UserRegistry$2.run(UserRegistry.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:246)
at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:225)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getGovernanceSystemRegistry(EmbeddedRegistryService.java:517)
at
org.wso2.carbon.core.util.KeyStoreManager.(KeyStoreManager.java:77)
at
org.wso2.carbon.core.util.KeyStoreManager.getInstance(KeyStoreManager.java:112)
at
org.wso2.carbon.core.util.KeyStoreManager.getInstance(KeyStoreManager.java:102)
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.addCertToHeader(AbstractJWTGenerator.java:325)
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.buildHeader(AbstractJWTGenerator.java:178)
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.generateToken(AbstractJWTGenerator.java:131)
at
org.wso2.carbon.apimgt.keymgt.handlers.AbstractKeyValidationHandler.generateConsumerToken(AbstractKeyValidationHandler.java:146)
at
org.wso2.carbon.apimgt.keymgt.service.APIKeyValidationService.validateKey(APIKeyValidationService.java:169)
at
org.wso2.carbon.apimgt.keymgt.service.thrift.APIKeyValidationServiceImpl.validateKey(APIKeyValidationServiceImpl.java:131)
at
org.wso2.carbon.apimgt.impl.generated.thrift.APIKeyValidationService$Processor$validateKey.getResult(APIKeyValidationService.java:278)
at
org.wso2.carbon.apimgt.impl.generated.thrift.APIKeyValidationService$Processor$validateKey.getResult(APIKeyValidationService.java:266)
at
org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176)
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:744)
[2016-01-12 09:22:11,445] ERROR - AbstractKeyValidationHandler Error
occurred while generating JWT.
org.wso2.carbon.apimgt.api.APIManagementException: Error in obtaining
tenant's keystore
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.addCertToHeader(AbstractJWTGenerator.java:386)
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.buildHeader(AbstractJWTGenerator.java:178)
at
org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.generateToken(AbstractJWTGenerator.java:131)
at
org.wso2.ca

Re: [Dev] Subscription issue of new REST API in API Manager 1.10.0

2016-01-12 Thread Malintha Amarasinghe
Hi Thilini,

As we know, to authenticate the user we are validating the Authorization
header instead of asking the user to invoke a separate API resource for
login like the Jaggery API. Here we cannot use the existing login
implementation as it is written using Jaggery/HostObject basis. So we have
to implement the subscriber adding flow in new REST API.

Thanks.

On Tue, Jan 12, 2016 at 3:46 PM, Thilini Cooray  wrote:

> Hi Malintha,
>
> Can you please explain me the following?
>
> In the API Manager store UI or jaggery APIs, users required to login prior
> to create applications or subscribe to APIs etc.
> In the store REST API we are passing an authentication header for invoking
> APIs.
> Have we eliminated from user login in this approach?
>
> Thanks.
>
>
> On Tue, Jan 12, 2016 at 3:15 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi All,
>>
>> We have identified an issue in new Store REST API in API Manager 1.10.0
>> as follows.
>>
>>1. A new user is created using the admin console and added subscriber
>>permission ( OR a user is signed up using Store web app)
>>2. Now without logging in to store at least once, the user invokes
>>the Store REST API. (say, to to create an Application)
>>3. We can see that the request is failed.
>>
>> If the user try invoking the REST API after logging in to the Store at
>> least once, the request will be successful.
>>
>> The reason for the issue is that, the user (subscriber) is added to
>> AM_SUBSCRIBER table in login flow. When the user invoke the REST API
>> without logging in to Store at lease once, the request fails as the
>> subscriber is not yet added to AM_SUBSCRIBER table.
>>
>> To solve the above issue we are looking into following choices.
>>
>>1. At the point the user is authenticated in REST API, we create a
>>JWT and add it to CXF message context with additional information
>>(including whether the subscriber is already added to AM_SUBSCRIBER or
>>not). Then we use a separate CXF interceptor (say
>>PostAuthenticationInterceptor) to retrieve the JWT from the message
>>context, read required parameters from it and add the user to the
>>AM_SUBSCRIBER if he is not added already.
>>2. Similar approach to the above method without using JWT. We set the
>>authenticated user to the carbon context. It is read by a separate
>>CXF Interceptor, and the user is added to AM_SUBSCRIBER if he is not yet
>>already added.
>>
>> Both choices are based on using a separate Interceptor so we have
>> following advantages.
>>
>>1. We use a common set of Authentication interceptors for both
>>Publisher and Store REST APIs but we don't need to execute this flow for
>>Publisher REST API. We can easily do it by removing
>>the PostAuthenticationInterceptor from beans.xml in Publisher REST API web
>>app and keep it only in Store beans.xml.
>>2. For any authenticated mechanism (Basic or OAuth or any new
>>authentication mechanism) we need this flow to be executed in Store REST
>>API. This can be easily achieved using an Interceptor.
>>
>> Appreciate your thoughts on this.
>>
>> Thanks,
>> Malintha
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



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

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


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Nipuna Chandradasa
Congratulations Fazlan .. :D

On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga  wrote:

> Congratulations Fazlan!!! :)
>
> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
> wrote:
>
>> Congratulations..!!!
>>
>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando  wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He
>>> has been a key contributor to the *WSO2 Machine Learner *Product and in
>>> recognition of his work, he had been voted as a WSO2 Committer.
>>>
>>> Congratulations Fazlan and keep up the good work!
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94 716042995 <94716042995>
> LinkedIn:
> *http://lk.linkedin.com/in/ashenweerathunga
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] WSO2 Private PaaS 4.1.1 Released!

2016-01-12 Thread Gayan Gunarathne
WSO2 Private PaaS team is pleased to announce the release of WSO2 Private
PaaS 4.1.1.

WSO2 Private PaaS is a complete, enterprise-grade solution, offering an
open Platform as a Service (PaaS) built on top of Apache Stratos. It is
released under Apache Software License Version 2.0. Mostly enterprise
software solutions are built on heterogeneous software systems with diverse
dependencies & requirements. Moving an equivalent system to the cloud with
automated deployment, dependency management, artifact distribution,
autoscaling, dynamic load balancing, multi-region, multi-IaaS & cloud
bursting features is be a tedious task. Moreover automating advanced
middleware configurations such as cluster discovery & single sign on is
bound to add more complexity.

WSO2 provides a complete solution to meet these requirements, with WSO2
Private PaaS. WSO2 Private PaaS is an enterprise grade Platform as a
Service (PaaS) that delivers standard, on-premise, application,
integration, data, identity, governance, and analytics PaaS solutions for
IT projects.

Architecture

https://docs.wso2.com/display/PP411/Architecture

Cartridges

WSO2 ships cartridges separately, currently following cartridges are
available for WSO2 Private PaaS 4.1.1:


   -

WSO2 API Manager 1.9.1 cartridge
   -

WSO2 Enterprise Service Bus 4.8.1 cartridge
   -

WSO2 Enterprise Service Bus 4.9.0 cartridge
   -

WSO2 Identity Server 5.0.0 cartridge
   -

WSO2 Application Server 5.2.1 cartridge
   -

WSO2 Application Server 5.3.0 cartridge
   -

WSO2 Business Process Server 3.5.0 cartridge
   -

WSO2 Business Rules Server 2.1.0 cartridge
   -

WSO2 Governance Registry 5.0.0 cartridge
   -

WSO2 Governance Registry 5.1.0 cartridge
   -

WSO2 Data Services Server 3.2.2 cartridge
   -

WSO2 Message Broker 3.0.0 cartridge
   -

WSO2 Complex Event Processor 4.0.0 cartridge

Bug Fixes

   -

   [PAAS-306 ] - Auth token
   generation admin user name should be in configuration
   -

   [PAAS-307 ] - Error in logic when
   sending the artifact update event
   -

   [PAAS-309 ] - Security group
   validation error when creating the new security group for the LB.
   -

   [PAAS-314 ] - IaaS provider type
   is displayed incorrectly in PPaaS UI when there is only one IaaS provider
   available at cloud-controller.xml.
   -

   [PAAS-316 ] - Repo notification
   rest API not working for the GIT hook
   -

   [PAAS-318 ] - NPE is thrown when
   executing export.sh script in subscription-manager tool
   -

   [PAAS-321 ] - Integration test
   failure with Stratos 4.1.5 artifacts
   -

   [PAAS-322 ] - Remove the CEP and
   DAS extension from PPaaS

Improvements

   -

   [PAAS-299 ] - Moving 'Show Usage'
   button from application instance tooltip to application tooltip to view
   application level metering data.
   -

   [PAAS-300 ] - Moving
   authentication logic to separate jag file to avoid duplication of same code
   -

   [PAAS-301 ] - Updating metering
   and monitoring dashboard artifacts to support carbon-dashboard version 1.0.7
   -

   [PAAS-304 ] - Reading
   dasStatsPublisherEabled value and metering and monitoring dashboard Urls at
   web application startup time and set those as application variables.
   -

   [PAAS-313 ] - Message Broker HA
   support for the Python Cartridge Agent

Tasks

   -

   [PAAS-305 ] - UI changes in ppaas
   to integrate DAS monitoring dashboard
   -

   [PAAS-320 ] - Update the PPaaS
   with the Stratos 4.1.5 release artifacts



Release Notes

https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10501&version=11888

Documentation

https://docs.wso2.com/display/PP411

Downloads

http://wso2.com/cloud/private-paas

Known Issues

https://wso2.org/jira/issues/?filter=12621

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : dev@wso2.org | Subscribe | Mail Archive


Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 Private PaaS through the public JIRA
. You can use the Carbon JIRA
 to report any issues related to the
Carbon base framework or associated Carbon components.

Support

We are committed to ensuring that your enterprise middleware deployment is
completely sup

Re: [Dev] Subscription issue of new REST API in API Manager 1.10.0

2016-01-12 Thread Sanjeewa Malalgoda
I think we can call get subscriber by access token method in AbstractAPI
Manager class.
Then if that return subscriber details we can assume subscriber is there in
DB(first need to check it ruturns user or entry in subscriber table).
Or we may use get subscriber for same.
If subscriber is not there we may simply call add subscriber method.

Anyway we set authenticated user to current carbon context from
authentication interceptor. So we don't need JWT to store that information.
So we may have another interceptor after that as you suggested.
And from that we can check subscriber and add new one if its missed.

Thanks,
sanjeewa.

On Tue, Jan 12, 2016 at 5:11 PM, Malintha Amarasinghe 
wrote:

> Hi Thilini,
>
> As we know, to authenticate the user we are validating the Authorization
> header instead of asking the user to invoke a separate API resource for
> login like the Jaggery API. Here we cannot use the existing login
> implementation as it is written using Jaggery/HostObject basis. So we have
> to implement the subscriber adding flow in new REST API.
>
> Thanks.
>
> On Tue, Jan 12, 2016 at 3:46 PM, Thilini Cooray  wrote:
>
>> Hi Malintha,
>>
>> Can you please explain me the following?
>>
>> In the API Manager store UI or jaggery APIs, users required to login
>> prior to create applications or subscribe to APIs etc.
>> In the store REST API we are passing an authentication header for
>> invoking APIs.
>> Have we eliminated from user login in this approach?
>>
>> Thanks.
>>
>>
>> On Tue, Jan 12, 2016 at 3:15 PM, Malintha Amarasinghe > > wrote:
>>
>>> Hi All,
>>>
>>> We have identified an issue in new Store REST API in API Manager 1.10.0
>>> as follows.
>>>
>>>1. A new user is created using the admin console and added
>>>subscriber permission ( OR a user is signed up using Store web app)
>>>2. Now without logging in to store at least once, the user invokes
>>>the Store REST API. (say, to to create an Application)
>>>3. We can see that the request is failed.
>>>
>>> If the user try invoking the REST API after logging in to the Store at
>>> least once, the request will be successful.
>>>
>>> The reason for the issue is that, the user (subscriber) is added to
>>> AM_SUBSCRIBER table in login flow. When the user invoke the REST API
>>> without logging in to Store at lease once, the request fails as the
>>> subscriber is not yet added to AM_SUBSCRIBER table.
>>>
>>> To solve the above issue we are looking into following choices.
>>>
>>>1. At the point the user is authenticated in REST API, we create a
>>>JWT and add it to CXF message context with additional information
>>>(including whether the subscriber is already added to AM_SUBSCRIBER or
>>>not). Then we use a separate CXF interceptor (say
>>>PostAuthenticationInterceptor) to retrieve the JWT from the message
>>>context, read required parameters from it and add the user to the
>>>AM_SUBSCRIBER if he is not added already.
>>>2. Similar approach to the above method without using JWT. We set
>>>the authenticated user to the carbon context. It is read by a separate
>>>CXF Interceptor, and the user is added to AM_SUBSCRIBER if he is not yet
>>>already added.
>>>
>>> Both choices are based on using a separate Interceptor so we have
>>> following advantages.
>>>
>>>1. We use a common set of Authentication interceptors for both
>>>Publisher and Store REST APIs but we don't need to execute this flow for
>>>Publisher REST API. We can easily do it by removing
>>>the PostAuthenticationInterceptor from beans.xml in Publisher REST API 
>>> web
>>>app and keep it only in Store beans.xml.
>>>2. For any authenticated mechanism (Basic or OAuth or any new
>>>authentication mechanism) we need this flow to be executed in Store REST
>>>API. This can be easily achieved using an Interceptor.
>>>
>>> Appreciate your thoughts on this.
>>>
>>> Thanks,
>>> Malintha
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

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

__

Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Mohamed ZAJITH
Congratulations Fazlan.  
On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa"  wrote:

> Congratulations Fazlan .. :D
>
> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga  wrote:
>
>> Congratulations Fazlan!!! :)
>>
>> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
>> wrote:
>>
>>> Congratulations..!!!
>>>
>>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
>>> wrote:
>>>
 Hi All,

 It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*. He
 has been a key contributor to the *WSO2 Machine Learner *Product and
 in recognition of his work, he had been voted as a WSO2 Committer.

 Congratulations Fazlan and keep up the good work!

 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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


>>>
>>>
>>> --
>>> *Malintha Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 71 2312958
>>> Blog:http://malinthas.blogspot.com
>>> Page:   http://about.me/malintha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ashen Weerathunga*
>> Software Engineer - Intern
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: as...@wso2.com
>> Mobile: +94 716042995 <94716042995>
>> LinkedIn:
>> *http://lk.linkedin.com/in/ashenweerathunga
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nipuna Marcus
> *Software Engineer*
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
> Mobile : +94 (0) 713 667906
> nipu...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread NIFRAS ISMAIL
Great Keep up Fazlan!

Regards.
*M. Nifras Ismail*
[image: LinkedIn] 



On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH 
wrote:

> Congratulations Fazlan.  
> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa"  wrote:
>
>> Congratulations Fazlan .. :D
>>
>> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
>> wrote:
>>
>>> Congratulations Fazlan!!! :)
>>>
>>> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
>>> wrote:
>>>
 Congratulations..!!!

 On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
 wrote:

> Hi All,
>
> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
> He has been a key contributor to the *WSO2 Machine Learner *Product
> and in recognition of his work, he had been voted as a WSO2 Committer
> .
>
> Congratulations Fazlan and keep up the good work!
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Mobile: +94 71 2312958
 Blog:http://malinthas.blogspot.com
 Page:   http://about.me/malintha

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


>>>
>>>
>>> --
>>> *Ashen Weerathunga*
>>> Software Engineer - Intern
>>> WSO2 Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Email: as...@wso2.com
>>> Mobile: +94 716042995 <94716042995>
>>> LinkedIn:
>>> *http://lk.linkedin.com/in/ashenweerathunga
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nipuna Marcus
>> *Software Engineer*
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>> Mobile : +94 (0) 713 667906
>> nipu...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Menaka Jayawardena
Congratulations Fazlan.

On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL 
wrote:

> Great Keep up Fazlan!
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] 
>
>
>
> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH 
> wrote:
>
>> Congratulations Fazlan.  
>> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa"  wrote:
>>
>>> Congratulations Fazlan .. :D
>>>
>>> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
>>> wrote:
>>>
 Congratulations Fazlan!!! :)

 On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
 wrote:

> Congratulations..!!!
>
> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
>> He has been a key contributor to the *WSO2 Machine Learner *Product
>> and in recognition of his work, he had been voted as a WSO2 Committer
>> .
>>
>> Congratulations Fazlan and keep up the good work!
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile: +94 71 2312958
> Blog:http://malinthas.blogspot.com
> Page:   http://about.me/malintha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Ashen Weerathunga*
 Software Engineer - Intern
 WSO2 Inc.: http://wso2.com
 lean.enterprise.middleware

 Email: as...@wso2.com
 Mobile: +94 716042995 <94716042995>
 LinkedIn:
 *http://lk.linkedin.com/in/ashenweerathunga
 *

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


>>>
>>>
>>> --
>>> Nipuna Marcus
>>> *Software Engineer*
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>> Mobile : +94 (0) 713 667906
>>> nipu...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Sajith Dimal
Congratulations Fazlan!!! :)

On Tue, Jan 12, 2016 at 9:10 PM, Menaka Jayawardena  wrote:

> Congratulations Fazlan.
>
> On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL 
> wrote:
>
>> Great Keep up Fazlan!
>>
>> Regards.
>> *M. Nifras Ismail*
>> [image: LinkedIn] 
>>
>>
>>
>> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH 
>> wrote:
>>
>>> Congratulations Fazlan.  
>>> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa"  wrote:
>>>
 Congratulations Fazlan .. :D

 On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
 wrote:

> Congratulations Fazlan!!! :)
>
> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
> wrote:
>
>> Congratulations..!!!
>>
>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
>>> He has been a key contributor to the *WSO2 Machine Learner *Product
>>> and in recognition of his work, he had been voted as a WSO2
>>> Committer.
>>>
>>> Congratulations Fazlan and keep up the good work!
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94 716042995 <94716042995>
> LinkedIn:
> *http://lk.linkedin.com/in/ashenweerathunga
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Nipuna Marcus
 *Software Engineer*
 WSO2 Inc.
 http://wso2.com/ - "lean . enterprise . middleware"
 Mobile : +94 (0) 713 667906
 nipu...@wso2.com

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


>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Menaka Madushanka Jayawardena
> Software Engineering Intern
> men...@wso2.com
> Mobile:- +94 71 8851183/ +94 71 3505470
> LinkedIn - Menaka Jayawardena
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards

*Sajith Dimal*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: saji...@wso2.com
Mobile: +94 783101496 <94783101496>
LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b

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


Re: [Dev] Random errors from UUF

2016-01-12 Thread Sajith Ariyarathna
Hi Sumedha,

Seems like this is a concurrency problem. That's why the issue appears
randomly. According to this [1] email thread, issue is in the Handlebars
library (in UUF we use handlebars-v2.0.0.js library). Seems like
handlebars.js library is not thread-safe [2].

In UUF, a separate Handlebars environment is created from a shared root
Handlebars environment [3] for each HTTP request. Hence, the root
Handlebars environment is shared between threads (HTTP requests). However
the 'Handlebars.compile()' function is not thread-safe. That is the reason
behind  this issue.

I have fixed this problem by eliminating the shared root Handlebars
environment. See PR [4].

[1] http://mail.openjdk.java.net/pipermail/nashorn-dev/2015-May/004482.html
[2] https://github.com/wycats/handlebars.js/issues/1031
[3]
https://github.com/wso2-incubator/uuf-template-app/blob/IoTS-1.0.0-M1/base-ui/org.wso2.carbon.uuf.ui.feature/src/main/resources/jaggeryapps/uuf-app/lib/modules/handlebars/handlebars.js#L658-L665
[4] https://github.com/wso2-incubator/uuf-template-app/pull/17

Thanks.

On Tue, Jan 12, 2016 at 11:46 AM, Sajith Ariyarathna 
wrote:

> will look into this
>
> On Tue, Jan 12, 2016 at 11:29 AM, Sumedha Rubasinghe 
> wrote:
>
>> Sajith/Manu,
>> Experiencing some random UI errors from UUF/template App.
>> Attached some screenshots @ https://wso2.org/jira/browse/IOTS-13.
>>
>> Could you please check?
>>
>>
>>
>> --
>> /sumedha
>>
>>
>
>
> --
> Sajith Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> mobile: +94 77 6602284, +94 71 3951048
>



-- 
Sajith Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
mobile: +94 77 6602284, +94 71 3951048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Custom Mediator

2016-01-12 Thread John Q
Hello,
Can any body tell me how can I create a custom payload and invoke a
sequence from a custom mediator?

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


[Dev] Fwd: custom mediator

2016-01-12 Thread John Q
Hi, I need to write a custom mediator that receive a list of items and
create a message for each one of them, after that I want to inject each
message inside the sequence mediation, just as foreach does, can any body
provide me an example?

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


Re: [Dev] Fwd: custom mediator

2016-01-12 Thread Harsha Kumara
Hey John,

Please find [1], [2] and [3] as useful resources. You can build the XML
content with axiom interfaces and set  to the message body.

[1] - https://docs.wso2.com/display/ESB481/Class+Mediator
[2] -
https://docs.wso2.com/display/ESB481/Sample+380:+Writing+your+own+Custom+Mediation+in+Java
[3] - http://blog.lasindu.com/2014/05/creating-simple-class-mediator.html

Thanks,
Harsha

On Wed, Jan 13, 2016 at 1:27 AM, John Q  wrote:

> Hi, I need to write a custom mediator that receive a list of items and
> create a message for each one of them, after that I want to inject each
> message inside the sequence mediation, just as foreach does, can any body
> provide me an example?
>
> thanks,
> john
>
> ___
> 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] I am getting the following error in the console and unable to get resource

2016-01-12 Thread Abimaran Kugathasan
HI Pramod,

On Tue, Jan 12, 2016 at 3:30 AM, Pramod Thakur  wrote:

> Hi All,
>
> Can i get the source code location for wso2 api manager.
>

You can find the source code for API Manager here [1] and here [2]. [1]
having all the components and [2] having testcases and UI components.


[1] : https://github.com/wso2/carbon-apimgt
[2] : https://github.com/wso2/product-apim


>
>
> I have created a tenant xyz.com and a user excha...@abc.com.
>
> To get the access token i am passing the following
>  username:  excha...@abc.com
>  password: password.
>
>
> I have also created a Customhandler in the api manager which will add a
> tenantdomain in the header from the url by splitting the url
> https://10.104.204.110:8243/t/xyz.com/sdp/v1/groups
> and set the domain as xyz.com which will be used during authentication as
> we are appening the tenantdomain to identify the user of that domain like
> below.
>
> username: excha...@abc.com.xyz.com
> password: password.
>
> Its working fine but once i got the token during validation of token i am
> getting as null instead of token in x-jwt-token.
>
> The error in the console is as follows.
>
>
>
> [2016-01-12 09:21:54,850]  INFO - APIKeyValidator Token
> 90e0516d4c3b5e8b825746aef1a19 expired.
> [2016-01-12 09:21:54,851]  WARN - APIAuthenticationHandler API
> authentication failure due to Invalid Credentials
> [2016-01-12 09:22:02,476]  INFO - PermissionUpdater Permission cache
> updated for tenant -1234
> [2016-01-12 09:22:02,490]  INFO - CarbonAuthenticationUtil
> 'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,490+0530]
> [2016-01-12 09:22:02,567]  INFO - CarbonAuthenticationUtil
> 'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,567+0530]
> [2016-01-12 09:22:02,622]  INFO - PermissionUpdater Permission cache
> updated for tenant -1234
> [2016-01-12 09:22:02,633]  INFO - CarbonAuthenticationUtil
> 'admin@carbon.super [-1234]' logged in at [2016-01-12 09:22:02,633+0530]
> [2016-01-12 09:22:11,443] ERROR - KeyStoreManager Error when retrieving
> the system governance registry
> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to
> obtain the user realm for tenant: -1.
> at
> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:304)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.access$100(UserRegistry.java:61)
> at
> org.wso2.carbon.registry.core.session.UserRegistry$2.run(UserRegistry.java:249)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:246)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:225)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getGovernanceSystemRegistry(EmbeddedRegistryService.java:517)
> at
> org.wso2.carbon.core.util.KeyStoreManager.(KeyStoreManager.java:77)
> at
> org.wso2.carbon.core.util.KeyStoreManager.getInstance(KeyStoreManager.java:112)
> at
> org.wso2.carbon.core.util.KeyStoreManager.getInstance(KeyStoreManager.java:102)
> at
> org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.addCertToHeader(AbstractJWTGenerator.java:325)
> at
> org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.buildHeader(AbstractJWTGenerator.java:178)
> at
> org.wso2.carbon.apimgt.impl.token.AbstractJWTGenerator.generateToken(AbstractJWTGenerator.java:131)
> at
> org.wso2.carbon.apimgt.keymgt.handlers.AbstractKeyValidationHandler.generateConsumerToken(AbstractKeyValidationHandler.java:146)
> at
> org.wso2.carbon.apimgt.keymgt.service.APIKeyValidationService.validateKey(APIKeyValidationService.java:169)
> at
> org.wso2.carbon.apimgt.keymgt.service.thrift.APIKeyValidationServiceImpl.validateKey(APIKeyValidationServiceImpl.java:131)
> at
> org.wso2.carbon.apimgt.impl.generated.thrift.APIKeyValidationService$Processor$validateKey.getResult(APIKeyValidationService.java:278)
> at
> org.wso2.carbon.apimgt.impl.generated.thrift.APIKeyValidationService$Processor$validateKey.getResult(APIKeyValidationService.java:266)
> at
> org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176)
> 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:744)
> [2016-01-12 09:22:11,445] ERROR - AbstractKeyValidationHa

Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Geesara Prathap
Congratulations Fazlan!!! :)

On Tue, Jan 12, 2016 at 9:24 PM, Sajith Dimal  wrote:

> Congratulations Fazlan!!! :)
>
> On Tue, Jan 12, 2016 at 9:10 PM, Menaka Jayawardena 
> wrote:
>
>> Congratulations Fazlan.
>>
>> On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL 
>> wrote:
>>
>>> Great Keep up Fazlan!
>>>
>>> Regards.
>>> *M. Nifras Ismail*
>>> [image: LinkedIn] 
>>>
>>>
>>>
>>> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH >> > wrote:
>>>
 Congratulations Fazlan.  
 On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa"  wrote:

> Congratulations Fazlan .. :D
>
> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
> wrote:
>
>> Congratulations Fazlan!!! :)
>>
>> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari 
>> wrote:
>>
>>> Congratulations..!!!
>>>
>>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
>>> wrote:
>>>
 Hi All,

 It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
 He has been a key contributor to the *WSO2 Machine Learner *Product
 and in recognition of his work, he had been voted as a WSO2
 Committer.

 Congratulations Fazlan and keep up the good work!

 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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


>>>
>>>
>>> --
>>> *Malintha Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 71 2312958
>>> Blog:http://malinthas.blogspot.com
>>> Page:   http://about.me/malintha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ashen Weerathunga*
>> Software Engineer - Intern
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: as...@wso2.com
>> Mobile: +94 716042995 <94716042995>
>> LinkedIn:
>> *http://lk.linkedin.com/in/ashenweerathunga
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nipuna Marcus
> *Software Engineer*
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
> Mobile : +94 (0) 713 667906
> nipu...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards
>
> *Sajith Dimal*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: saji...@wso2.com
> Mobile: +94 783101496 <94783101496>
> LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Geesara Prathap Kulathunga
Software Engineer
WSO2 Inc; http://wso2.com
Mobile : +940772684174
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Natasha Wijesekara
Congratulations Fazlan!!! :)

On Wed, Jan 13, 2016 at 7:51 AM, Geesara Prathap  wrote:

> Congratulations Fazlan!!! :)
>
> On Tue, Jan 12, 2016 at 9:24 PM, Sajith Dimal  wrote:
>
>> Congratulations Fazlan!!! :)
>>
>> On Tue, Jan 12, 2016 at 9:10 PM, Menaka Jayawardena 
>> wrote:
>>
>>> Congratulations Fazlan.
>>>
>>> On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL 
>>> wrote:
>>>
 Great Keep up Fazlan!

 Regards.
 *M. Nifras Ismail*
 [image: LinkedIn] 



 On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH <
 mohamedzaj...@gmail.com> wrote:

> Congratulations Fazlan.  
> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa" 
> wrote:
>
>> Congratulations Fazlan .. :D
>>
>> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
>> wrote:
>>
>>> Congratulations Fazlan!!! :)
>>>
>>> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari >> > wrote:
>>>
 Congratulations..!!!

 On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
 wrote:

> Hi All,
>
> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
> He has been a key contributor to the *WSO2 Machine Learner *Product
> and in recognition of his work, he had been voted as a WSO2
> Committer.
>
> Congratulations Fazlan and keep up the good work!
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Mobile: +94 71 2312958
 Blog:http://malinthas.blogspot.com
 Page:   http://about.me/malintha

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


>>>
>>>
>>> --
>>> *Ashen Weerathunga*
>>> Software Engineer - Intern
>>> WSO2 Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Email: as...@wso2.com
>>> Mobile: +94 716042995 <94716042995>
>>> LinkedIn:
>>> *http://lk.linkedin.com/in/ashenweerathunga
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nipuna Marcus
>> *Software Engineer*
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>> Mobile : +94 (0) 713 667906
>> nipu...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

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


>>>
>>>
>>> --
>>> Menaka Madushanka Jayawardena
>>> Software Engineering Intern
>>> men...@wso2.com
>>> Mobile:- +94 71 8851183/ +94 71 3505470
>>> LinkedIn - Menaka Jayawardena
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards
>>
>> *Sajith Dimal*
>> Software Engineer - Intern
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: saji...@wso2.com
>> Mobile: +94 783101496 <94783101496>
>> LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Geesara Prathap Kulathunga
> Software Engineer
> WSO2 Inc; http://wso2.com
> Mobile : +940772684174
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Natasha Wijesekare*

*Software Engineering Intern, WSO2  Inc:  http://wso2.com
*
*email  : nata...@wso2.com *
*mobile: +94 771358651*
___
D

Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Praminda Jayawardana
Congratulations Fazlan!!!

On Wed, Jan 13, 2016 at 8:32 AM, Natasha Wijesekara 
wrote:

> Congratulations Fazlan!!! :)
>
> On Wed, Jan 13, 2016 at 7:51 AM, Geesara Prathap  wrote:
>
>> Congratulations Fazlan!!! :)
>>
>> On Tue, Jan 12, 2016 at 9:24 PM, Sajith Dimal  wrote:
>>
>>> Congratulations Fazlan!!! :)
>>>
>>> On Tue, Jan 12, 2016 at 9:10 PM, Menaka Jayawardena 
>>> wrote:
>>>
 Congratulations Fazlan.

 On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL 
 wrote:

> Great Keep up Fazlan!
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn]
> 
>
>
>
> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH <
> mohamedzaj...@gmail.com> wrote:
>
>> Congratulations Fazlan.  
>> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa" 
>> wrote:
>>
>>> Congratulations Fazlan .. :D
>>>
>>> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
>>> wrote:
>>>
 Congratulations Fazlan!!! :)

 On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari <
 malin...@wso2.com> wrote:

> Congratulations..!!!
>
> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce *Fazlan Nazeem* as a
>> *WSO2 Committer*. He has been a key contributor to the *WSO2
>> Machine Learner *Product and in recognition of his work, he had
>> been voted as a WSO2 Committer.
>>
>> Congratulations Fazlan and keep up the good work!
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile: +94 71 2312958
> Blog:http://malinthas.blogspot.com
> Page:   http://about.me/malintha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Ashen Weerathunga*
 Software Engineer - Intern
 WSO2 Inc.: http://wso2.com
 lean.enterprise.middleware

 Email: as...@wso2.com
 Mobile: +94 716042995 <94716042995>
 LinkedIn:
 *http://lk.linkedin.com/in/ashenweerathunga
 *

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


>>>
>>>
>>> --
>>> Nipuna Marcus
>>> *Software Engineer*
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>> Mobile : +94 (0) 713 667906
>>> nipu...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Menaka Madushanka Jayawardena
 Software Engineering Intern
 men...@wso2.com
 Mobile:- +94 71 8851183/ +94 71 3505470
 LinkedIn - Menaka Jayawardena
 

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


>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> *Sajith Dimal*
>>> Software Engineer - Intern
>>> WSO2 Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Email: saji...@wso2.com
>>> Mobile: +94 783101496 <94783101496>
>>> LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Geesara Prathap Kulathunga
>> Software Engineer
>> WSO2 Inc; http://wso2.com
>> Mobile : +940772684174
>>
>>
>> ___

Re: [Dev] [Need Small Support] Safarifoneict

2016-01-12 Thread Jayanga Kaushalya
Hi Zakaria,

It seems you have an answer in the Stackoverflow for this issue and if you
have any followup questions, please feel free to ask on Stackoverflow or in
this mail thread.

Thanks!


*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware

On Tue, Jan 12, 2016 at 2:59 PM,  wrote:

>
>
> HI wso2 Developers.
>
>
>
> I am Software Engineer in Safarfoneict , and
> their sent me to build their Central Authentication and Authorization
> System using Open source Projects.
>
>
>
> I founded the Wso2 Is and then Wso2 Am, they was fascinating Products and
> agree to give it my time to see how it works.
>
> I told the VP of this company to buy Wso2 support credit, and he agree in
> one condition to show him in real working example how it will benefit us.
>
> I decided to implement It to our current working application.
>
> Every thing was going good until this issue stopped me see this
> Stackoverflow link [ http://stackoverflow.com/questions/34738716 ]
>
> I attached the important configuration page and some configuration files.
> The First five config file is for API Manager and other five is Identity
> Server config files
>
> So  I thing you gonna help me this issue to solve and get your credit
> Support.
>
>
>
> Best Regards
>
> Zakaria.Ali
>
>
>
>
>
> ___
> 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] Class Not Found error when shutting down the Dashboard Server

2016-01-12 Thread Charitha Goonetilleke
Hi Lalanke,

Did you tried to start server with OSGi console? If not try to start server
with OSGi console by "*sh wso2server.sh -DosgiConsole*". Then try to figure
out *org.wso2.carbon.registry.indexing* package is exported by one or more
bundles. You can check this by issuing "
*p org.wso2.carbon.registry.indexing*" in OSGi console. Probably this issue
might happen if above package is exported by multiple bundles. So please
make sure it is not.

Also please read the first answer in this [1] for additional work around.

[1]
http://stackoverflow.com/questions/7475195/osgi-how-to-ensure-classpath-consistency

Thanks & Regards,
/charithag

On Tue, Jan 12, 2016 at 3:13 PM, Lalanke Athauda  wrote:

> Hi Rajith,
> Thanks for your quick reply. I checked the logs and there are no other
> errors or exceptions. This is my complete log.
>
> [2016-01-12 15:01:05,189]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2016-01-12 15:01:05,189]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 3.13.0-74-generic, amd64
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /usr/lib/jvm/java-7-oracle/jre
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.7.0_80
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 24.80-b11,Oracle Corporation
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT/tmp
> [2016-01-12 15:01:05,190]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> lalanke, en-US, Asia/Colombo
> [2016-01-12 15:01:05,261]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
> Carbon is configured to use the default keystore (wso2carbon.jks). To
> maximize security when deploying to a production environment, configure a
> new keystore with a unique password in the production server profile.
> [2016-01-12 15:01:05,311]  WARN
> {org.wso2.carbon.identity.notification.mgt.NotificationMgtConfigBuilder} -
> Secret Resolver is not present. Will not resolve encryptions in config file
> [2016-01-12 15:01:06,108]  WARN
> {org.wso2.carbon.registry.core.config.RegistryConfigurationProcessor} -
> Could not find the handler class
> org.wso2.jaggery.scxml.registry.handlers.JaggeryExecutorHandler. This
> handler will not be registered. All handler and filter classes should be in
> the class path of the Registry.
> [2016-01-12 15:01:06,141]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
> Registry in 31ms
> [2016-01-12 15:01:06,200]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
> Registry Mode: READ-WRITE
> [2016-01-12 15:01:06,758]  INFO
> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon
> UserStoreMgtDSComponent activated successfully.
> [2016-01-12 15:01:09,784]  INFO
> {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
> http://tiles.apache.org/tags-tiles is already defined
> [2016-01-12 15:01:10,290]  INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
> -  User Store Configuration Deployer initiated.
> [2016-01-12 15:01:10,291]  INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
> -  User Store Configuration Deployer initiated.
> [2016-01-12 15:01:10,870]  INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
> service: UserInformationRecoveryService {super-tenant}
> [2016-01-12 15:01:11,553]  INFO
> {org.wso2.carbon.core.init.CarbonServerManager} -  Repository   :
> /home/lalanke/sources/product-ues/modules/distribution/target/wso2ds-2.0.0-SNAPSHOT/repository/deployment/server/
> [2016-01-12 15:01:11,608]  INFO
> {org.wso2.carbon.core.multitenancy.eager.TenantLoadingConfig} -  Switching
> to default mode : Tenant lazy loading mechanism has been activated...
> [2016-01-12 15:01:11,621]  INFO
> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
> Permission cache updated for tenant -1234
> [2016-01-12 15:01:11,721]  INFO
> {org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore}
> -  Thread pool size for session persistent consumer : 100
> [2016-01-12 15:01:11,729]  INFO
> {org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore}
> -  Session Data Operations CleanUp Task of Authentication framework is not
> enabled.
> [2016-01-12 15:01:11

Re: [Dev] WSO2 Committers += Fazlan Nazeem

2016-01-12 Thread Nethaji Chandrasiri
Congratulations Fazlan

On Wed, Jan 13, 2016 at 9:17 AM, Praminda Jayawardana 
wrote:

> Congratulations Fazlan!!!
>
> On Wed, Jan 13, 2016 at 8:32 AM, Natasha Wijesekara 
> wrote:
>
>> Congratulations Fazlan!!! :)
>>
>> On Wed, Jan 13, 2016 at 7:51 AM, Geesara Prathap 
>> wrote:
>>
>>> Congratulations Fazlan!!! :)
>>>
>>> On Tue, Jan 12, 2016 at 9:24 PM, Sajith Dimal  wrote:
>>>
 Congratulations Fazlan!!! :)

 On Tue, Jan 12, 2016 at 9:10 PM, Menaka Jayawardena 
 wrote:

> Congratulations Fazlan.
>
> On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL  > wrote:
>
>> Great Keep up Fazlan!
>>
>> Regards.
>> *M. Nifras Ismail*
>> [image: LinkedIn]
>> 
>>
>>
>>
>> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH <
>> mohamedzaj...@gmail.com> wrote:
>>
>>> Congratulations Fazlan.  
>>> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa" 
>>> wrote:
>>>
 Congratulations Fazlan .. :D

 On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga 
 wrote:

> Congratulations Fazlan!!! :)
>
> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari <
> malin...@wso2.com> wrote:
>
>> Congratulations..!!!
>>
>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando > > wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce *Fazlan Nazeem* as a
>>> *WSO2 Committer*. He has been a key contributor to the *WSO2
>>> Machine Learner *Product and in recognition of his work, he had
>>> been voted as a WSO2 Committer.
>>>
>>> Congratulations Fazlan and keep up the good work!
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94 716042995 <94716042995>
> LinkedIn:
> *http://lk.linkedin.com/in/ashenweerathunga
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Nipuna Marcus
 *Software Engineer*
 WSO2 Inc.
 http://wso2.com/ - "lean . enterprise . middleware"
 Mobile : +94 (0) 713 667906
 nipu...@wso2.com

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


>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Menaka Madushanka Jayawardena
> Software Engineering Intern
> men...@wso2.com
> Mobile:- +94 71 8851183/ +94 71 3505470
> LinkedIn - Menaka Jayawardena
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thanks & Regards

 *Sajith Dimal*
 Software Engineer - Intern
 WSO2 Inc.: http://wso2.com
 lean.enterprise.middleware

 Email: saji...@wso2.com
 Mobile: +94 783101496 <94783101496>
 LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
 


 ___

Re: [Dev] Custom Mediator

2016-01-12 Thread Harshan Liyanage
Hi John,

The easiest way to achieve this would be to write a class mediator [1] and
then using it in the synapse configuration. You can use a PayloadFactory
Mediator [2] to create the custom payload. So there will be no need for
creating the custom payload and invoking a sequence from inside the custom
mediator.

[1]. https://docs.wso2.com/display/ESB490/Class+Mediator
[2]. https://docs.wso2.com/display/ESB490/PayloadFactory+Mediator

Thanks,
Harshan

Harshan Liyanage
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.

On Wed, Jan 13, 2016 at 1:26 AM, John Q  wrote:

> Hello,
> Can any body tell me how can I create a custom payload and invoke a
> sequence from a custom mediator?
>
> thanks,
> john
>
> ___
> 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


[Dev] PPaaS Artifact Migration Tool- Naming Convention for Application ID

2016-01-12 Thread Malmee Weerasinghe
Hi All,

In the tool that is being developed to convert artifact JSON files of PPaaS
4.0.0 to PPaaS 4.1.x, the conversion has to be done as such one application
has to be created for one subscription. In this conversion what should be
the naming convention of the application ID? One approach is to use 'alias'
in subscription data as an ID for a particular application.

Thanks
-- 
Malmee Weerasinghe
WSO2 Intern
mobile : (+94)* 71 7601905* |   email :   
mal...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] WSO2 Committers += Asanthi Kulasinghe

2016-01-12 Thread Aparna Karunarathna
Hi All,

It's my pleasure to announce Asanthi Kulasinghe as a WSO2 Committer. Asanthi is
an active member of QA team and has given a great contribution to API
Manager, App Manager,  ESB product releases and API Manager, ESB service
packs.

Congratulations Asanthi and keep up the good work...!

-- 
*Regards,*

*Aparna Karunarathna.*


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


Re: [Dev] WSO2 Committers += Asanthi Kulasinghe

2016-01-12 Thread Dilini Gunatilake
Congrats Kaushi!!!

On Wed, Jan 13, 2016 at 12:20 PM, Aparna Karunarathna 
wrote:

> Hi All,
>
> It's my pleasure to announce Asanthi Kulasinghe as a WSO2 Committer.
> Asanthi is an active member of QA team and has given a great contribution
> to API Manager, App Manager,  ESB product releases and API Manager, ESB
> service packs.
>
> Congratulations Asanthi and keep up the good work...!
>
> --
> *Regards,*
>
> *Aparna Karunarathna.*
>
>
> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Dilini GunatilakeSoftware Engineer - QA Team*
Mobile : +94 (0) 771 162518
dili...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Creating a Dashboard for Web Application Statistics Monitoring for Application Server 6.0.0

2016-01-12 Thread Lochana Ranaweera
Hi all,

I'm currently working on a project on adding web application statistics
monitoring feature to the upcoming Application Server 6.0.0. The data
collected from the web applications will be published to the Data Analytics
Server through a custom Tomcat valve, the development of which has been
carried out separately.

Once the data has been published, web application statistics should be
displayed to the users via a Dashboard. For this, what will be the best
suited option out of the following?

[1] Utilizing the gadget generation wizard of the DAS

[2] Utilizing the Dashboard Server

Any suggestions and feedback are highly appreciated.

Thanks.

-- 
Lochana Ranaweera
Intern Software Engineer
WSO2 Inc: http://wso2.com
Blog: https://lochanaranaweera.wordpress.com/
Mobile: +94716487055 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [AF] Fixing (APPFAC-3217) - Support APIM group subscription in App Factory

2016-01-12 Thread Amalka Subasinghe
Hi Nuwan,

We need APIM support to show subscribed API, when there's 1 user assigned
to 2 user groups.

*Our current AF APIM integration flow works as follows.*

let's say we have a tenant foo.com and users - appowner1 and developer1
App owner1 creates an AF application 'AFapp1' and assign devloper1 as a
developer of that application.
according to the current implementation only the appowner1 can subscribe to
the APIM API.
[When appowner1 login to the APIM, we create an application 'AFapp1' in
APIM side and selecting that application appowner1 can subscribe to an API]
Then appowner1 can see subscribed APIs in AF side, where developers can't
see that API.

So we need to implement APIM group subscriptions in AF.
to implement it we have to set the organization claim (as eg:
'foo.com_AFapp1') for appowner1 and developer1.
Then both users can see the subscribed API.

*We have another use case;*
basically our user grouping happens per AF application and 1 user can be in
2 groups

Let's say appowner1 creates an another application AFapp2
then appowner1 is belongs to 2 user groups. So we need to assign two values
for the organization claim. (foo.com_AFapp1, foo.com_AFapp2)
appowner1 want to see subscribed API in APIM side based on that 2
organizations.

As I know, APIM does not support this when there's a more than 1 group
assigned for the organization claim.
But this is a required use case for the AF/cloud, and we can't customize
the GroupingExtractor due to maintainability issues in cloud.

Can this improvement provide by APIM?

Thanks
Amalka






On Tue, Jan 12, 2016 at 1:42 PM, Amalka Subasinghe  wrote:

> Hi,
>
> Currently only the app owner allows to subscribed to an API, generate keys
> and see subscribed APIs, where other users are not allowed as showed in the
> below table.
>
>
> Subscribe to API Generate Keys View subscribed APIs in AF side View Prod
> keys in AF side View Sandbox keys in AF side App owner Y Y Y Y Y Developer
>
>
>
> Y QA
>
>
>
> Y DevOps
>
>
> Y Y
> We want to improve the AF - APIM integration as follows. So we need
> implement $subject.
> 1. making both app owner and developer can subscribe to an API and
> generate keys
> 2. making all users to see subscribed API per application
>
>
> Subscribe to API Generate Keys View subscribed APIs in AF side View Prod
> keys in AF side View Sandbox keys in AF side App owner Y Y Y Y Y Developer
> Y Y Y
> Y QA
>
> Y
> Y DevOps
>
> Y Y Y
> *Things to do:*
>
> 1. All the users of a particular app we need to maintain as a group.
>
> In APIM side they uses http://wso2.org/claims/organization claim to group
> the users. We have to set this claim (eg: app key as the value of the
> claim) when appowner or developer try to click on 'Go to API Manager'
> button.
> Currently we use a role app_appName to group the users of a particular
> application in AF. If we use this we have to implement a custom grouping
> extractor to get the users of a particular group.
>
>
> *Issues: *a. Since we don't set the claim for QA and DevOps users, they
> can't view subscribed APIs in AF side, and If we add the claim they also
> will be able to subscribe to APIs and generate keys. So we need to find a
> way to view subscribed api for a particular application by QA and Devops
> users.
> b. With this implementation Developer can see prod keys also.
>
>
> 2. Make Go to API Manager and Sync Keys buttons enabled only to appowner
> and developer.
> For this we can use resource permissions we already have.
>
>
> 3. Need to improve/test all the rest calls we do with APIM to work with
> groups and fix if there's any issue.
>
>- Login - When user clicks on 'Go to API Manager' button of a
>particular app, it should login to APIM and show the subscribed APIs,
>listed under selected application.
>- Create application
>- Remove application
>- Get published APIs by application
>- List subscription
>- Get applications
>
> [1] https://wso2.org/jira/browse/APPFAC-3217
>
> Thanks
> Amalka
>
>


-- 
Amalka Subasinghe
Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Subscription issue of new REST API in API Manager 1.10.0

2016-01-12 Thread Malintha Amarasinghe
Thanks Sanjeewa for the response.

Also had an offline discussion with Sanjeewa and identified that we cannot
use get subscriber by access token method. It uses AM_* tables to map the
token with the subscriber.  When we create an Application using Dynamic
Client Registration module, we do not add app registration information to
AM_* tables, so get subscriber by access token method always return null.
As an alternative method we can use getSubscriber(username) method.

Thank you.
Malintha

On Tue, Jan 12, 2016 at 6:53 PM, Sanjeewa Malalgoda 
wrote:

> I think we can call get subscriber by access token method in AbstractAPI
> Manager class.
> Then if that return subscriber details we can assume subscriber is there
> in DB(first need to check it ruturns user or entry in subscriber table).
> Or we may use get subscriber for same.
> If subscriber is not there we may simply call add subscriber method.
>
> Anyway we set authenticated user to current carbon context from
> authentication interceptor. So we don't need JWT to store that information.
> So we may have another interceptor after that as you suggested.
> And from that we can check subscriber and add new one if its missed.
>
> Thanks,
> sanjeewa.
>
> On Tue, Jan 12, 2016 at 5:11 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi Thilini,
>>
>> As we know, to authenticate the user we are validating the Authorization
>> header instead of asking the user to invoke a separate API resource for
>> login like the Jaggery API. Here we cannot use the existing login
>> implementation as it is written using Jaggery/HostObject basis. So we have
>> to implement the subscriber adding flow in new REST API.
>>
>> Thanks.
>>
>> On Tue, Jan 12, 2016 at 3:46 PM, Thilini Cooray 
>> wrote:
>>
>>> Hi Malintha,
>>>
>>> Can you please explain me the following?
>>>
>>> In the API Manager store UI or jaggery APIs, users required to login
>>> prior to create applications or subscribe to APIs etc.
>>> In the store REST API we are passing an authentication header for
>>> invoking APIs.
>>> Have we eliminated from user login in this approach?
>>>
>>> Thanks.
>>>
>>>
>>> On Tue, Jan 12, 2016 at 3:15 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Hi All,

 We have identified an issue in new Store REST API in API Manager 1.10.0
 as follows.

1. A new user is created using the admin console and added
subscriber permission ( OR a user is signed up using Store web app)
2. Now without logging in to store at least once, the user invokes
the Store REST API. (say, to to create an Application)
3. We can see that the request is failed.

 If the user try invoking the REST API after logging in to the Store at
 least once, the request will be successful.

 The reason for the issue is that, the user (subscriber) is added to
 AM_SUBSCRIBER table in login flow. When the user invoke the REST API
 without logging in to Store at lease once, the request fails as the
 subscriber is not yet added to AM_SUBSCRIBER table.

 To solve the above issue we are looking into following choices.

1. At the point the user is authenticated in REST API, we create a
JWT and add it to CXF message context with additional information
(including whether the subscriber is already added to AM_SUBSCRIBER or
not). Then we use a separate CXF interceptor (say
PostAuthenticationInterceptor) to retrieve the JWT from the message
context, read required parameters from it and add the user to the
AM_SUBSCRIBER if he is not added already.
2. Similar approach to the above method without using JWT. We set
the authenticated user to the carbon context. It is read by a separate
CXF Interceptor, and the user is added to AM_SUBSCRIBER if he is not yet
already added.

 Both choices are based on using a separate Interceptor so we have
 following advantages.

1. We use a common set of Authentication interceptors for both
Publisher and Store REST APIs but we don't need to execute this flow for
Publisher REST API. We can easily do it by removing
the PostAuthenticationInterceptor from beans.xml in Publisher REST API 
 web
app and keep it only in Store beans.xml.
2. For any authenticated mechanism (Basic or OAuth or any new
authentication mechanism) we need this flow to be executed in Store REST
API. This can be easily achieved using an Interceptor.

 Appreciate your thoughts on this.

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

 Mobile : +94 712383306

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


>>>
>>>
>>> --
>>> Best Regards,
>>>