Re: [Dev] Regarding the OIDC openid scope in WSO2 IS

2017-08-10 Thread Farasath Ahamed 
On Friday, August 11, 2017, Omindu Rathnaweera  wrote:

>
>
> On Thu, Aug 10, 2017 at 5:15 PM, Hasini Witharana  > wrote:
>
>> Hi,
>>
>> Currently I am working on making WSO2 IS OpenID Connect certified. I ran
>> a test on requesting essential claims from OP, when the scope is openid. It
>> gave an error saying unexpected claims returned.
>>
>
> This is not an error, but a warning correct ?
>
>
>> Then I inquired about this issue through the mailing list of OIDC
>> specifications [1]. I got some information from that as openid scope
>> should only return subject and issuer.
>>
>> IS 5.4.0 is supporting many claims for scope openid. They are :
>>   sub,email,email_verified,name,
>> family_name,given_name,middle_name,nickname,
>>   preferred_username,profile,pic
>> ture,website,gender,birthdate,zoneinfo,locale,
>>   phone_number,phone_number_veri
>> fied,address,street,updated_at
>>
>> I couldn't find In the OIDC specification where it mention that, openid
>> scope should only return subject and issuer.
>>
>
> AFAIK, the spec has not specifically mentioned about what we should return
> for the openid scope and it only mentions about the what should be returned
> for the default 4 scopes. However it is understandable that the test client
> expects a minimum set of claims when having only the openid scope. If an RP
> needs additional claims, it should request them with specifying additional
> scopes and/or essential claims. So I think the correct behavior would be to
> return only a minimal set of claims for the openid scope.
>

Since the spec hasn't specifed this minimal set of claims one can argue
that it is something specific to an RP. This is how our current
implementation works as well. Although we could define a set of claim bound
to the 'openid' scope, the service provider could control what it needs
from the claims bound to openid scope by using requested claims
configuration.

Changing 'openid' scope to return issuer and sub claims only will be a
breaking change for many existing providers who rely on the additional
claims (some of them could be mandatory in PoV of the RP)

IMO, if the spec doesn't mandate what should be returned for openid scope
then we can keep our existing implementation as it is.


>
>> Can you please help me on this issue?
>>
>> Thank you.
>>
>>
>> [1] - http://lists.openid.net/pipermail/openid-specs/2017-August/
>> subject.html
>>
>> --
>>
>> *Hasini Witharana*
>> Software Engineering Intern | WSO2
>>
>>
>> *Email : hasi...@wso2.com
>> *
>>
>> *Mobile : +94713850143 <+94%2071%20385%200143>[image:
>> http://wso2.com/signature] *
>>
>
>
> Regards,
> Omindu.
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>


-- 
Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 

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

Re: [Dev] Please review and merge the PR

2017-08-10 Thread Dilan Udara Ariyaratne 
Hi Ashen,

Added Few more suggestions. Please go through and verify.

Thanks,
Dilan.

*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Thu, Aug 10, 2017 at 7:23 PM, Ashen Weerathunga  wrote:

> Hi Dilan,
>
> I have done the requested changes and updated the PR.
>
> Thanks,
> Ashen
>
> On Thu, Aug 10, 2017 at 6:23 AM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Ashen,
>>
>> Went through the code and added few comments, Please go through and
>> verify.
>>
>> Thanks,
>> Dilan.
>>
>> *Dilan U. Ariyaratne*
>> Senior Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> On Wed, Aug 9, 2017 at 1:44 PM, Ashen Weerathunga  wrote:
>>
>>> Hi,
>>>
>>> Can you please review and merge the PR [1]. This is regarding the Issue
>>> [2].
>>>
>>> [1] https://github.com/wso2/carbon-kernel/pull/1464
>>> [2] https://github.com/wso2/carbon-kernel/issues/1467
>>>
>>>
>>> Thanks,
>>> Ashen
>>> --
>>> *Ashen Weerathunga*
>>> Software Engineer
>>> WSO2 Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Email: as...@wso2.com
>>> Mobile: +94716042995 <94716042995>
>>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
>>> *
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94716042995 <94716042995>
> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
> *
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Regarding the OIDC openid scope in WSO2 IS

2017-08-10 Thread Omindu Rathnaweera 
On Thu, Aug 10, 2017 at 5:15 PM, Hasini Witharana  wrote:

> Hi,
>
> Currently I am working on making WSO2 IS OpenID Connect certified. I ran a
> test on requesting essential claims from OP, when the scope is openid. It
> gave an error saying unexpected claims returned.
>

This is not an error, but a warning correct ?


> Then I inquired about this issue through the mailing list of OIDC
> specifications [1]. I got some information from that as openid scope
> should only return subject and issuer.
>
> IS 5.4.0 is supporting many claims for scope openid. They are :
>   sub,email,email_verified,name,family_name,given_name,middle_
> name,nickname,
>   
> preferred_username,profile,picture,website,gender,birthdate,zoneinfo,locale,
>
>   phone_number,phone_number_verified,address,street,updated_at
>
> I couldn't find In the OIDC specification where it mention that, openid
> scope should only return subject and issuer.
>

AFAIK, the spec has not specifically mentioned about what we should return
for the openid scope and it only mentions about the what should be returned
for the default 4 scopes. However it is understandable that the test client
expects a minimum set of claims when having only the openid scope. If an RP
needs additional claims, it should request them with specifying additional
scopes and/or essential claims. So I think the correct behavior would be to
return only a minimal set of claims for the openid scope.


> Can you please help me on this issue?
>
> Thank you.
>
>
> [1] - http://lists.openid.net/pipermail/openid-specs/2017-
> August/subject.html
>
> --
>
> *Hasini Witharana*
> Software Engineering Intern | WSO2
>
>
> *Email : hasi...@wso2.com *
>
> *Mobile : +94713850143 <+94%2071%20385%200143>[image:
> http://wso2.com/signature] *
>


Regards,
Omindu.

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

Re: [Dev] [GSOC-2017] [IS] [OAuth DCRM] Integration Test for the implementation of OAuth 2.0 DCRM protocol

2017-08-10 Thread Dimuthu De Lanerolle 
Hi Abilashini,

I have added a few review comments for PR's. Please have a look and fix.

Regards
DimuthuD

On Thu, Aug 10, 2017 at 8:07 PM, Ishara Karunarathna 
wrote:

> Hi,
>
> Thanks Abilashini, will review the PR
>
> -Ishara
>
> On Wed, Aug 9, 2017 at 1:05 PM, Abilashini Thiyagarajah <
> abilashini...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> Please find the PR of the integration test cases [1] for the
>> implementation of OAuth DCRM protocol [2].
>>
>> Covered test cases in this PR as follow,
>>
>>1. Successful Read service provider
>>2. Read request with invalid client ID in the endpoint URL
>>3. Successful update service provider
>>4. Update request with invalid client ID in the endpoint URL
>>5. Update request with invalid client ID
>>6. Update request with invalid client secret
>>7. Update request without grant type
>>8. Update request with invalid grant type
>>9. Successful Delete service provider
>>10. Delete request with invalid client ID in the endpoint URL
>>
>> Please share your feedback to improve further
>>
>> [1] https://github.com/wso2/product-is/pull/1293
>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/pull/396
>>
>> Best Regards,
>> Abilashini
>>
>> *Thiyagarajah Abilashini*
>> Student
>> Department of Computer Science and Engineering
>> University of Moratuwa, Sri Lanka
>>
>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <071%20799%206791>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Stream Processor 4.0.0-M9 Released !

2017-08-10 Thread Minudika Malshan 
Hi All,

The WSO2 Analytics team is pleased to announce the release of *WSO2 Stream
Processor Version 4.0.0 Milestone 9*.

WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time, incremental & intelligent data processing
capabilities.

WSO2 Stream Processor can:


   - Receive events from various data sources
   - Process & correlate them in real-time with the sate of the art
   high-performance real-time Siddhi Complex Event Processing Engine that
   works with easy to learn the SQL-Like query language.
   - Process analysis that spans for longer time duration with its
   incremental processing capability by achieving high performance with low
   infrastructure cost.
   - Uses Machine Learning and other models to drive intelligent
   insights from the data
   - Notifications interesting event occurrences as alerts via multiple
   types of transport & let users visualize the results via customizable
   dashboards.
   - WSO2 SP is released under Apache Software License Version 2.0, one
   of the most business-friendly licenses available today.


You can find the product at
https://github.com/wso2/product-sp/releases/download/v4.0.0-M9/wso2sp-4.0.0-M9.zip
Documentation at https://docs.wso2.com/display/SP400/
Source code at https://github.com/wso2/product-sp/releases/tag/v4.0.0-M9

*WSO2 SP 4.0.0-M9 includes following*

*Improvements*

   -  Feed simulator UI fixes.

*Reporting Issues*

Issues can be reported using the github issue tracker available at
https://github.com/wso2/product-sp/issues


*Contact us*
WSO2 Stream Processor developers can be contacted via the mailing lists:
Developer List : dev@wso2.org | Subscribe
 | Mail Archive


Alternatively, questions can also be raised in the stackoverflow:

Forum http://stackoverflow.com/questions/tagged/wso2/


*Support *

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support/.

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .


*~ The WSO2 Analytics Team ~*

-- 
*Minudika Gammanpila*
Software Engineer - WSO2

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

[Dev] [Architecture] WSO2 API Manager 3.0.0-M5 Released!

2017-08-10 Thread Harsha Kumara 
The WSO2 API Manager team is pleased to announce the release of API Manager
 3.0.0-M5. It's now available to download.
Distribution


   - 
*https://github.com/wso2/product-apim/releases/download/v3.0.0-m5/wso2apim-3.0.0-m5.zip
   
*
   -
*https://github.com/wso2/product-apim/releases/download/v3.0.0-m5/wso2apim-das-3.0.0-m5.zip
   

   *
   -
*https://github.com/wso2/product-apim/releases/download/v3.0.0-m5/wso2apim-gateway-3.0.0-m5.zip
   

   *

Documentation


   - https://docs.wso2.com/display/AM300/

Following list contains all the features, improvements and bug fixes
available with this milestone.
New Feature


   -
   
*https://github.com/wso2/product-apim/issues?q=is%3Aissue+label%3A%22new+feature%22+is%3Aclosed*

   

   -
*https://github.com/wso2/carbon-apimgt/issues?q=label%3Anew-feature+is%3Aclosed
   

   *

Tasks/Bug Fixes and Improvements


   - *https://github.com/wso2/carbon-apimgt/milestone/2?closed=1
   *
   
   - https://github.com/wso2/product-apim/milestone/2?closed=1

List of Open Issues


   - https://github.com/wso2/carbon-apimgt/labels/3.0.0
   

   -
*https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aopen+label%3A3.0.0
   

   *

How To Contribute

Your feedback is most welcome!
Mailing Lists
Join our mailing list and correspond with the developers directly.

   -

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

   User Forum : StackOverflow
   


Reporting Issues

We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
.

~ The WSO2 API Manager Team ~


-- 
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] [GSOC-2017] [IS] [OAuth DCRM] Integration Test for the implementation of OAuth 2.0 DCRM protocol

2017-08-10 Thread Ishara Karunarathna 
Hi,

Thanks Abilashini, will review the PR

-Ishara

On Wed, Aug 9, 2017 at 1:05 PM, Abilashini Thiyagarajah <
abilashini...@cse.mrt.ac.lk> wrote:

> Hi,
>
> Please find the PR of the integration test cases [1] for the
> implementation of OAuth DCRM protocol [2].
>
> Covered test cases in this PR as follow,
>
>1. Successful Read service provider
>2. Read request with invalid client ID in the endpoint URL
>3. Successful update service provider
>4. Update request with invalid client ID in the endpoint URL
>5. Update request with invalid client ID
>6. Update request with invalid client secret
>7. Update request without grant type
>8. Update request with invalid grant type
>9. Successful Delete service provider
>10. Delete request with invalid client ID in the endpoint URL
>
> Please share your feedback to improve further
>
> [1] https://github.com/wso2/product-is/pull/1293
> [2] https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/pull/396
>
> Best Regards,
> Abilashini
>
> *Thiyagarajah Abilashini*
> Student
> Department of Computer Science and Engineering
> University of Moratuwa, Sri Lanka
>



-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Enterprise Integrator 6.2.0-M2 Released!

2017-08-10 Thread Vinod Kavinda 
The WSO2 Integration team is pleased to announce the release of Enterprise
Integrator 6.2.0-M2. It is available for download now from following
location.

https://github.com/wso2/product-ei/releases/tag/v6.2.0-m2
*Tasks/Bug Fixes and Improvements*

WSO2 Jira - Fixed Issues 
Product EI - Github fixed issues

*List of Open Issues*

WSO2 Jira - Open Issues 
WSO2 EI Github - Open Issues


*Mailing Lists*
Join our mailing list and correspond with the developers directly.
Developer List : dev@wso2.org | Subscribe | Mail Archive
User Forum : StackOverflow

*Reporting Issues*

We encourage you to report issues, improvements and feature requests
regarding WSO2 Integrator through WSO2 EI GIT Issues.

~ The WSO2 Integration Team ~

-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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

Re: [Dev] Please review and merge the PR

2017-08-10 Thread Ashen Weerathunga 
Hi Dilan,

I have done the requested changes and updated the PR.

Thanks,
Ashen

On Thu, Aug 10, 2017 at 6:23 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Ashen,
>
> Went through the code and added few comments, Please go through and verify.
>
> Thanks,
> Dilan.
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Wed, Aug 9, 2017 at 1:44 PM, Ashen Weerathunga  wrote:
>
>> Hi,
>>
>> Can you please review and merge the PR [1]. This is regarding the Issue
>> [2].
>>
>> [1] https://github.com/wso2/carbon-kernel/pull/1464
>> [2] https://github.com/wso2/carbon-kernel/issues/1467
>>
>>
>> Thanks,
>> Ashen
>> --
>> *Ashen Weerathunga*
>> Software Engineer
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: as...@wso2.com
>> Mobile: +94716042995 <94716042995>
>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
>> *
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


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

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

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

[Dev] Regarding the OIDC openid scope in WSO2 IS

2017-08-10 Thread Hasini Witharana 
Hi,

Currently I am working on making WSO2 IS OpenID Connect certified. I ran a
test on requesting essential claims from OP, when the scope is openid. It
gave an error saying unexpected claims returned.

Then I inquired about this issue through the mailing list of OIDC
specifications [1]. I got some information from that as openid scope should
only return subject and issuer.

IS 5.4.0 is supporting many claims for scope openid. They are :
  sub,email,email_verified,name,family_name,given_name,middle_
name,nickname,
  
preferred_username,profile,picture,website,gender,birthdate,zoneinfo,locale,

  phone_number,phone_number_verified,address,street,updated_at

I couldn't find In the OIDC specification where it mention that, openid
scope should only return subject and issuer.

Can you please help me on this issue?

Thank you.


[1] -
http://lists.openid.net/pipermail/openid-specs/2017-August/subject.html

-- 

*Hasini Witharana*
Software Engineering Intern | WSO2


*Email : hasi...@wso2.com *

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

[Dev] [Kubernetes] [EI] EI Analytics Dashboard not loading on Containers

2017-08-10 Thread Dilan Udara Ariyaratne 
Hi All,

I am currently testing an EI Integrator cluster with one analytics node
inside a kubernetes cluster of containers.
Analytics node runs on a docker container and when I try to access the EI
dashboard, following exception becomes visible on container logs.

[2017-08-10 06:48:20,887] [EI-Analytics] ERROR
{org.jaggeryjs.jaggery.core.manager.WebAppManager}
-  org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.apache.axis2.AxisFault: connect timed out (/portal/modules/api.js#28)
(/portal/routers/apis.jag#40) (/portal/routers/tenant.jag#89)
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.apache.axis2.AxisFault: connect timed out (/portal/modules/api.js#28)
(/portal/routers/apis.jag#40) (/portal/routers/tenant.jag#89)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(
RhinoEngine.java:571)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(
RhinoEngine.java:273)
at org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(
WebAppManager.java:588)
at org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(
WebAppManager.java:508)
at org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(
JaggeryServlet.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:208)
at org.apache.catalina.core.ApplicationDispatcher.invoke(
ApplicationDispatcher.java:747)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(
ApplicationDispatcher.java:485)
at org.apache.catalina.core.ApplicationDispatcher.doForward(
ApplicationDispatcher.java:377)
at org.apache.catalina.core.ApplicationDispatcher.forward(
ApplicationDispatcher.java:337)
at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(
JaggeryFilter.java:21)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(
WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:208)
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(
HttpHeaderSecurityFilter.java:120)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(
StandardWrapperValve.java:218)
at org.apache.catalina.core.StandardContextValve.invoke(
StandardContextValve.java:110)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
AuthenticatorBase.java:506)
at org.apache.catalina.core.StandardHostValve.invoke(
StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(
ErrorReportValve.java:103)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(
CompositeValve.java:99)
at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.
invoke(CarbonTomcatValve.java:47)
at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(
TenantLazyLoaderValve.java:57)
at org.wso2.carbon.event.receiver.core.internal.tenantmgt.
TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(
TomcatValveContainer.java:47)
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(
CompositeValve.java:62)
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValv
e.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(
AccessLogValve.java:962)
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(
CarbonContextCreatorValve.java:57)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:452)
at org.apache.coyote.http11.AbstractHttp11Processor.process(
AbstractHttp11Processor.java:1087)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.
process(AbstractProtocol.java:637)
at