date:20180215

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Malintha Amarasinghe

On Fri, Feb 16, 2018 at 12:28 PM, Malintha Amarasinghe 
wrote:

> Hi Sivaramya,
>
> On Fri, Feb 16, 2018 at 12:13 PM, Sivaramya Sivanathan  > wrote:
>
>> Hi All,
>>
>> I followed the following steps,
>>
>> 1) Download the fresh package *wso2am-2.1.0*
>>
> This API is not included in the fresh pack. This is available in the
> latest WUM update pack or one of the released updates (2.1.0-updateX). Take
> the latest one if possible.
>
> On a seperate note, this doc need to be updated mentioning those
> information.
>
> Thanks!
>
>
>>
>> 2) Obtain the *clientId* and *clientSecret* from the token endpoint and
>>  then get the *access_token. * (*access_token* : 3abb5d89-ddea
>> -39ae-aca4-c94ec3b4c1d1)
>> 3) Send that access token as a header in the API call.
>> 4) When I get the details of the application using the curl command as
>> below.
>> curl -k -H "Authorization: Bearer 
>> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
>> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
>> 9825-8a75-42d5-b1d9-4987612ea8f5"
>>
>> I got the response as follows,
>>
>> {
>>"applicationId":"a2dc9825-8a75-42d5-b1d9-4987612ea8f5",
>>"name":"sampleapp",
>>"subscriber":"admin",
>>"throttlingTier":"Unlimited",
>>"callbackUrl":"http://my.server.com/callback;,
>>"description":"sample app description",
>>"status":"APPROVED",
>>"groupId":null,
>> "keys":[{
>>"consumerKey":"RhKMetERTwVWOd
>> 9UvEU0v14Sflka","consumerSecret":"XWiufquXgT7MfEadNRDdtF_
>> v1Qga","supportedGrantTypes":null,"keyState":"COMPLETED","
>> keyType":"PRODUCTION",
>>"token":{"accessToken":"58c1d
>> 49f-7710-342e-85a9-b288f10ba323","tokenScopes":["am_
>> application_scope","default"],"validityTime":3600}
>> }]
>> }
>>
>> 5) But when I used the following curl command to get the key details of
>> a given type I didn't get any response messages as I mentioned above.
>>curl -k -H "Authorization: Bearer 
>> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
>> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
>> 9825-8a75-42d5-b1d9-4987612ea8f5/keys/PRODUCTION"
>>
>> Regards,
>>
>> Sivaramya Sivanathan
>> Associate Software Engineer | WSO2
>> Tel: 0770874960
>> WSO2 Inc : http://wso2.org
>> 
>> LinkedIn | www.linkedin.com/in/sivaramya
>>
>> On Fri, Feb 16, 2018 at 10:40 AM, Menaka Jayawardena 
>> wrote:
>>
>>> Hi Sivaramya,
>>>
>>> The basic information related to getting authorization code generation
>>> is in the Getting Started section of the documentation. For every request
>>> in the documentation, you have to follow the proper request format as
>>> Viduranga has mentioned.
>>>
>>> @Documenatation Team
>>> It's not clear in the API documentation because in Request section it
>>> just says,
>>>
>>> GET https://localhost:9443/api/am/store/v0.11/apis
>>>
>>> There is no indication about the authorization header or the correct
>>> curl. IMO it's better if we could restructure this documentation because it
>>> will also be used by the other users as well. As this is an autogenerated
>>> doc by the swagger file, we have to modify the swagger file with proper
>>> information.
>>>
>>> Thanks and Regards,
>>> Menaka
>>>
>>> On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne <
>>> vidura...@wso2.com> wrote:
>>>
 Hi Sivaramya,

 I checked the store REST API and the specific resource to get the key
 details of an individual application that you have mentioned and couldn't
 replicate the issue that you stated.

 These are the steps that I followed.

 1) Obtain the *clientId * and *clientSecret *from the token endpoint
 [1] and then get the *accessToken *[1]
 2) Send that access token as a header in the API call
 3) This is the request path that I used

 *https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
 *


 Can you please state the exact steps that you followed?

 [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide

 Thanks,
 Viduranga.

 On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan <
 sivara...@wso2.com> wrote:

> Hi all,
>
> I'm trying to use store REST API to do  the following operations using
> the curl command. But for these operations I'm unable to get the response
> (I'm getting empty response). But in APIM 2.1.0  console I'm getting the
> error as [5]. What could be the reason for this?
>
>- Get key details of a given type as in [1]
>- Get scopes associated with a particular application based on
>subscribed APIs as in [2]
>- Update grant types and callback url of

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Malintha Amarasinghe

Hi Sivaramya,

On Fri, Feb 16, 2018 at 12:13 PM, Sivaramya Sivanathan 
wrote:

> Hi All,
>
> I followed the following steps,
>
> 1) Download the fresh package *wso2am-2.1.0*
>
This API is not included in the fresh pack. This is available in the latest
WUM update pack or one of the released updates (2.1.0-updateX). Take the
latest one if possible.

On a seperate note, this doc need to be updated mentioning those
information.

Thanks!


>
> 2) Obtain the *clientId* and *clientSecret* from the token endpoint and
>  then get the *access_token. * (*access_token* : 3abb5d89-ddea
> -39ae-aca4-c94ec3b4c1d1)
> 3) Send that access token as a header in the API call.
> 4) When I get the details of the application using the curl command as
> below.
> curl -k -H "Authorization: Bearer 
> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
> 9825-8a75-42d5-b1d9-4987612ea8f5"
>
> I got the response as follows,
>
> {
>"applicationId":"a2dc9825-8a75-42d5-b1d9-4987612ea8f5",
>"name":"sampleapp",
>"subscriber":"admin",
>"throttlingTier":"Unlimited",
>"callbackUrl":"http://my.server.com/callback;,
>"description":"sample app description",
>"status":"APPROVED",
>"groupId":null,
> "keys":[{
>"consumerKey":"RhKMetERTwVWOd9UvEU0v14Sflka","
> consumerSecret":"XWiufquXgT7MfEadNRDdtF_v1Qga","
> supportedGrantTypes":null,"keyState":"COMPLETED","keyType":"PRODUCTION",
>"token":{"accessToken":"58c1d49f-7710-342e-85a9-
> b288f10ba323","tokenScopes":["am_application_scope","
> default"],"validityTime":3600}
> }]
> }
>
> 5) But when I used the following curl command to get the key details of a
> given type I didn't get any response messages as I mentioned above.
>curl -k -H "Authorization: Bearer 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
> 9825-8a75-42d5-b1d9-4987612ea8f5/keys/PRODUCTION"
>
> Regards,
>
> Sivaramya Sivanathan
> Associate Software Engineer | WSO2
> Tel: 0770874960
> WSO2 Inc : http://wso2.org
> 
> LinkedIn | www.linkedin.com/in/sivaramya
>
> On Fri, Feb 16, 2018 at 10:40 AM, Menaka Jayawardena 
> wrote:
>
>> Hi Sivaramya,
>>
>> The basic information related to getting authorization code generation is
>> in the Getting Started section of the documentation. For every request in
>> the documentation, you have to follow the proper request format as
>> Viduranga has mentioned.
>>
>> @Documenatation Team
>> It's not clear in the API documentation because in Request section it
>> just says,
>>
>> GET https://localhost:9443/api/am/store/v0.11/apis
>>
>> There is no indication about the authorization header or the correct
>> curl. IMO it's better if we could restructure this documentation because it
>> will also be used by the other users as well. As this is an autogenerated
>> doc by the swagger file, we have to modify the swagger file with proper
>> information.
>>
>> Thanks and Regards,
>> Menaka
>>
>> On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne <
>> vidura...@wso2.com> wrote:
>>
>>> Hi Sivaramya,
>>>
>>> I checked the store REST API and the specific resource to get the key
>>> details of an individual application that you have mentioned and couldn't
>>> replicate the issue that you stated.
>>>
>>> These are the steps that I followed.
>>>
>>> 1) Obtain the *clientId * and *clientSecret *from the token endpoint
>>> [1] and then get the *accessToken *[1]
>>> 2) Send that access token as a header in the API call
>>> 3) This is the request path that I used
>>>
>>> *https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
>>> *
>>>
>>>
>>> Can you please state the exact steps that you followed?
>>>
>>> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide
>>>
>>> Thanks,
>>> Viduranga.
>>>
>>> On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan <
>>> sivara...@wso2.com> wrote:
>>>
 Hi all,

 I'm trying to use store REST API to do  the following operations using
 the curl command. But for these operations I'm unable to get the response
 (I'm getting empty response). But in APIM 2.1.0  console I'm getting the
 error as [5]. What could be the reason for this?

- Get key details of a given type as in [1]
- Get scopes associated with a particular application based on
subscribed APIs as in [2]
- Update grant types and callback url of an application as in [3]
- Add new subscriptions (multiple) as in [4]


 [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
 html#!/operations#ApplicationIndividual#applicationsApplicat

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Chamin Dias

Hi,

Please follow the below steps. This flow is common for any operation in the
REST API.

Step 01 - User credential selection.
---

We are using : admin/admin

Concat it. Eg - admin:admin

Encode using base 64 and get the value.

YWRtaW46YWRtaW4=


Step 02 - DCR registration.
---

curl -X POST -H "Authorization: Basic YWRtaW46YWRtaW4=" -H "Content-Type:
application/json" -d @payload_store.json
http://localhost:9763/client-registration/v0.11/register

payload_store.json is attached.

Response will be like -

{
   "clientId":"LsjarDhkaUX8Dhhdf20iY9adSZca",
   "clientName":"admin_rest_api_store",
   "callBackURL":"www.google.lk",
   "clientSecret":"a49QTAYHpyQfT1oWHIdXay7Xubga",
   "isSaasApplication":true,
   "appOwner":"admin",
   "jsonString":"{\"grant_types\":\"password
refresh_token\",\"redirect_uris\":\"www.google.lk
\",\"client_name\":\"admin_rest_api_store\"}"
}

Get the clientId and clientSecret.

"clientId":"LsjarDhkaUX8Dhhdf20iY9adSZca"
"clientSecret":"a49QTAYHpyQfT1oWHIdXay7Xubga"

Concat it and encode it.

LsjarDhkaUX8Dhhdf20iY9adSZca:a49QTAYHpyQfT1oWHIdXay7Xubga

Base 64 encoded :
THNqYXJEaGthVVg4RGhoZGYyMGlZOWFkU1pjYTphNDlRVEFZSHB5UWZUMW9XSElkWGF5N1h1Ymdh



Step 03 - Obtain a token with the required scope. Eg : apim:subscribe
---

curl -k -d
"grant_type=password=admin=admin=apim:subscribe" -H
"Authorization: Basic
THNqYXJEaGthVVg4RGhoZGYyMGlZOWFkU1pjYTphNDlRVEFZSHB5UWZUMW9XSElkWGF5N1h1Ymdh"
https://127.0.0.1:8243/token

Response

{
   "access_token":"84553715-6595-39b6-bd83-76cd9387d296",
   "refresh_token":"c4047583-37dd-3cc5-a4c8-31b713c3d90f",
   "scope":"apim:subscribe",
   "token_type":"Bearer",
   "expires_in":3600
}


Step 04
---

Now you can use the "access_token":"84553715-6595-39b6-bd83-76cd9387d296"
to perform the task.

On Fri, Feb 16, 2018 at 12:13 PM, Sivaramya Sivanathan 
wrote:

> Hi All,
>
> I followed the following steps,
>
> 1) Download the fresh package *wso2am-2.1.0*
> 2) Obtain the *clientId* and *clientSecret* from the token endpoint and
>  then get the *access_token. * (*access_token* : 3abb5d89-ddea
> -39ae-aca4-c94ec3b4c1d1)
> 3) Send that access token as a header in the API call.
> 4) When I get the details of the application using the curl command as
> below.
> curl -k -H "Authorization: Bearer 
> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
> 9825-8a75-42d5-b1d9-4987612ea8f5"
>
> I got the response as follows,
>
> {
>"applicationId":"a2dc9825-8a75-42d5-b1d9-4987612ea8f5",
>"name":"sampleapp",
>"subscriber":"admin",
>"throttlingTier":"Unlimited",
>"callbackUrl":"http://my.server.com/callback;,
>"description":"sample app description",
>"status":"APPROVED",
>"groupId":null,
> "keys":[{
>"consumerKey":"RhKMetERTwVWOd9UvEU0v14Sflka","
> consumerSecret":"XWiufquXgT7MfEadNRDdtF_v1Qga","
> supportedGrantTypes":null,"keyState":"COMPLETED","keyType":"PRODUCTION",
>"token":{"accessToken":"58c1d49f-7710-342e-85a9-
> b288f10ba323","tokenScopes":["am_application_scope","
> default"],"validityTime":3600}
> }]
> }
>
> 5) But when I used the following curl command to get the key details of a
> given type I didn't get any response messages as I mentioned above.
>curl -k -H "Authorization: Bearer 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
> 9825-8a75-42d5-b1d9-4987612ea8f5/keys/PRODUCTION"
>
> Regards,
>
> Sivaramya Sivanathan
> Associate Software Engineer | WSO2
> Tel: 0770874960
> WSO2 Inc : http://wso2.org
> 
> LinkedIn | www.linkedin.com/in/sivaramya
>
> On Fri, Feb 16, 2018 at 10:40 AM, Menaka Jayawardena 
> wrote:
>
>> Hi Sivaramya,
>>
>> The basic information related to getting authorization code generation is
>> in the Getting Started section of the documentation. For every request in
>> the documentation, you have to follow the proper request format as
>> Viduranga has mentioned.
>>
>> @Documenatation Team
>> It's not clear in the API documentation because in Request section it
>> just says,
>>
>> GET https://localhost:9443/api/am/store/v0.11/apis
>>
>> There is no indication about the authorization header or the correct
>> curl. IMO it's better if we could restructure this documentation because it
>> will also be used by the other users as well. As this is an autogenerated
>> doc by the swagger file, we have to modify the swagger file with proper
>> information.
>>
>> Thanks and Regards,
>> Menaka
>>
>> On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne <
>> vidura...@wso2.com> wrote:
>>
>>> Hi Sivaramya,
>>>
>>> I checked the store REST API and the specific resource to get the key
>>> details of an individual application that you have mentioned and couldn't
>>> replicate the issue that you stated.
>>>
>>> These are

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Sivaramya Sivanathan

Hi All,

I followed the following steps,

1) Download the fresh package *wso2am-2.1.0*
2) Obtain the *clientId* and *clientSecret* from the token endpoint and
 then get the *access_token. * (*access_token* : 3abb5d89-
ddea-39ae-aca4-c94ec3b4c1d1)
3) Send that access token as a header in the API call.
4) When I get the details of the application using the curl command as
below.
curl -k -H "Authorization: Bearer 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
"https://localhost:9443/api/am/store/v0.11/applications/
a2dc9825-8a75-42d5-b1d9-4987612ea8f5"

I got the response as follows,

{
   "applicationId":"a2dc9825-8a75-42d5-b1d9-4987612ea8f5",
   "name":"sampleapp",
   "subscriber":"admin",
   "throttlingTier":"Unlimited",
   "callbackUrl":"http://my.server.com/callback;,
   "description":"sample app description",
   "status":"APPROVED",
   "groupId":null,
"keys":[{
   "consumerKey":"RhKMetERTwVWOd9UvEU0v14Sflka",
"consumerSecret":"XWiufquXgT7MfEadNRDdtF_v1Qga","supportedGrantTypes":null,"
keyState":"COMPLETED","keyType":"PRODUCTION",
   "token":{"accessToken":"58c1d49f-7710-
342e-85a9-b288f10ba323","tokenScopes":["am_application_scope","default"],"
validityTime":3600}
}]
}

5) But when I used the following curl command to get the key details of a
given type I didn't get any response messages as I mentioned above.
   curl -k -H "Authorization: Bearer 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
"https://localhost:9443/api/am/store/v0.11/applications/a2dc
9825-8a75-42d5-b1d9-4987612ea8f5/keys/PRODUCTION"

Regards,

Sivaramya Sivanathan
Associate Software Engineer | WSO2
Tel: 0770874960
WSO2 Inc : http://wso2.org

LinkedIn | www.linkedin.com/in/sivaramya

On Fri, Feb 16, 2018 at 10:40 AM, Menaka Jayawardena 
wrote:

> Hi Sivaramya,
>
> The basic information related to getting authorization code generation is
> in the Getting Started section of the documentation. For every request in
> the documentation, you have to follow the proper request format as
> Viduranga has mentioned.
>
> @Documenatation Team
> It's not clear in the API documentation because in Request section it just
> says,
>
> GET https://localhost:9443/api/am/store/v0.11/apis
>
> There is no indication about the authorization header or the correct curl.
> IMO it's better if we could restructure this documentation because it will
> also be used by the other users as well. As this is an autogenerated doc by
> the swagger file, we have to modify the swagger file with proper
> information.
>
> Thanks and Regards,
> Menaka
>
> On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne  > wrote:
>
>> Hi Sivaramya,
>>
>> I checked the store REST API and the specific resource to get the key
>> details of an individual application that you have mentioned and couldn't
>> replicate the issue that you stated.
>>
>> These are the steps that I followed.
>>
>> 1) Obtain the *clientId * and *clientSecret *from the token endpoint [1]
>> and then get the *accessToken *[1]
>> 2) Send that access token as a header in the API call
>> 3) This is the request path that I used
>>
>> *https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
>> *
>>
>>
>> Can you please state the exact steps that you followed?
>>
>> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide
>>
>> Thanks,
>> Viduranga.
>>
>> On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan > > wrote:
>>
>>> Hi all,
>>>
>>> I'm trying to use store REST API to do  the following operations using
>>> the curl command. But for these operations I'm unable to get the response
>>> (I'm getting empty response). But in APIM 2.1.0  console I'm getting the
>>> error as [5]. What could be the reason for this?
>>>
>>>- Get key details of a given type as in [1]
>>>- Get scopes associated with a particular application based on
>>>subscribed APIs as in [2]
>>>- Update grant types and callback url of an application as in [3]
>>>- Add new subscriptions (multiple) as in [4]
>>>
>>>
>>> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>>> html#!/operations#ApplicationIndividual#applicationsApplicat
>>> ionIdKeysKeyTypeGet
>>>
>>> [2] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>>> html#!/operations#ApplicationIndividual#applicationsScopesAp
>>> plicationIdGet
>>>
>>> [3] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>>> html#!/operations#ApplicationIndividual#applicationsApplicat
>>> ionIdKeysKeyTypePut
>>> 
>>>
>>>

Re: [Dev] CLI Client for MB4 using GoLang

2018-02-15 Thread Eranda Rajapakshe

Hi Lahiru,

For the moment we are using Java as it will be easy to use and maintain
with Broker implementation which we have currently.

Thanks,

On Fri, Feb 16, 2018 at 11:38 AM, Lahiru Sandaruwan 
wrote:

> Hi Eranda,
>
> Is this still developed with Go? I can see Java CLI client at [1].
>
> However, +1 for using Go for the CLI. IMO it would be cleaner to keep the
> CLI code separately, as two are written in different languages.
>
> [1] https://github.com/wso2/message-broker/tree/master/
> modules/broker-cli-client
>
> Thanks.
>
> On Thu, Feb 8, 2018 at 4:30 AM, Eranda Rajapakshe 
> wrote:
>
>> Hi,
>>
>> For MB4 we are writing a CLI client to perform admin operations. I have
>> done a draft design and doing an implementation. At the moment I am trying
>> out this with GoLang as its really flexible for building CLIs and it can
>> be, executables will be able to run on machines without a JVM.
>>
>> We are hoping to package this CLI client into MB itself. Also, our idea
>> is to include the source code in message-broker repo[1] (to make it easy to
>> maintain). Since message-broker repo is built using maven, I am hoping to
>> use this maven-go plugin[2] to build the Go source code of the CLI.
>>
>> Is there a better approach to achieve our requirement? (as it seems
>> maven-go plugin can manage dependencies and compile the Go code without any
>> external involvement.)
>>
>> [1]. https://github.com/wso2/message-broker
>> [2]. https://github.com/raydac/mvn-golang/
>>
>> Thanks,
>> --
>> *Eranda Rajapakshe*
>> Software Engineer
>> WSO2 Inc.
>> Mobile : +94784822608
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> Lahiru Sandaruwan
> WSO2 Inc., http://wso2.com
>
> lean.enterprise.middleware
>
> m: +1 901 530 2379 <(901)%20530-2379>
> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CLI Client for MB4 using GoLang

2018-02-15 Thread Lahiru Sandaruwan

Hi Eranda,

Is this still developed with Go? I can see Java CLI client at [1].

However, +1 for using Go for the CLI. IMO it would be cleaner to keep the
CLI code separately, as two are written in different languages.

[1]
https://github.com/wso2/message-broker/tree/master/modules/broker-cli-client

Thanks.

On Thu, Feb 8, 2018 at 4:30 AM, Eranda Rajapakshe  wrote:

> Hi,
>
> For MB4 we are writing a CLI client to perform admin operations. I have
> done a draft design and doing an implementation. At the moment I am trying
> out this with GoLang as its really flexible for building CLIs and it can
> be, executables will be able to run on machines without a JVM.
>
> We are hoping to package this CLI client into MB itself. Also, our idea is
> to include the source code in message-broker repo[1] (to make it easy to
> maintain). Since message-broker repo is built using maven, I am hoping to
> use this maven-go plugin[2] to build the Go source code of the CLI.
>
> Is there a better approach to achieve our requirement? (as it seems
> maven-go plugin can manage dependencies and compile the Go code without any
> external involvement.)
>
> [1]. https://github.com/wso2/message-broker
> [2]. https://github.com/raydac/mvn-golang/
>
> Thanks,
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

Lahiru Sandaruwan
WSO2 Inc., http://wso2.com

lean.enterprise.middleware

m: +1 901 530 2379
e: lahi...@wso2.com b: https://medium.com/@lahirugmg
in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Metrics databases for IS and EI

2018-02-15 Thread Lahiru Sandaruwan

Hi,

We have metrics databases for APIM 2.x.x[1] and IS 5.1.0[2].
But latest IS versions and EI does not have DBs to store metrics, even
though EI has a list of MBeans supported at [3].

This is an useful feature for tracking information if users don't want to
setup advanced monitoring tools. Are we planning to add this feature in the
future?

[1] https://docs.wso2.com/display/AM2xx/Enabling+Metrics+and+Storage+Types
[2] https://docs.wso2.com/display/IS510/Enabling+Metrics+and+Storage+Types
[3] https://docs.wso2.com/display/EI611/JMX+Monitoring

Thanks.

-- 
--

Lahiru Sandaruwan
WSO2 Inc., http://wso2.com

lean.enterprise.middleware

m: +1 901 530 2379
e: lahi...@wso2.com b: https://medium.com/@lahirugmg
in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Menaka Jayawardena

Hi Sivaramya,

The basic information related to getting authorization code generation is
in the Getting Started section of the documentation. For every request in
the documentation, you have to follow the proper request format as
Viduranga has mentioned.

@Documenatation Team
It's not clear in the API documentation because in Request section it just
says,

GET https://localhost:9443/api/am/store/v0.11/apis

There is no indication about the authorization header or the correct curl.
IMO it's better if we could restructure this documentation because it will
also be used by the other users as well. As this is an autogenerated doc by
the swagger file, we have to modify the swagger file with proper
information.

Thanks and Regards,
Menaka

On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne 
wrote:

> Hi Sivaramya,
>
> I checked the store REST API and the specific resource to get the key
> details of an individual application that you have mentioned and couldn't
> replicate the issue that you stated.
>
> These are the steps that I followed.
>
> 1) Obtain the *clientId * and *clientSecret *from the token endpoint [1]
> and then get the *accessToken *[1]
> 2) Send that access token as a header in the API call
> 3) This is the request path that I used
>
> *https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
> *
>
>
> Can you please state the exact steps that you followed?
>
> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide
>
> Thanks,
> Viduranga.
>
> On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan 
> wrote:
>
>> Hi all,
>>
>> I'm trying to use store REST API to do  the following operations using
>> the curl command. But for these operations I'm unable to get the response
>> (I'm getting empty response). But in APIM 2.1.0  console I'm getting the
>> error as [5]. What could be the reason for this?
>>
>>- Get key details of a given type as in [1]
>>- Get scopes associated with a particular application based on
>>subscribed APIs as in [2]
>>- Update grant types and callback url of an application as in [3]
>>- Add new subscriptions (multiple) as in [4]
>>
>>
>> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>> html#!/operations#ApplicationIndividual#applicationsApplicat
>> ionIdKeysKeyTypeGet
>>
>> [2] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>> html#!/operations#ApplicationIndividual#applicationsScopesAp
>> plicationIdGet
>>
>> [3] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
>> html#!/operations#ApplicationIndividual#applicationsApplicat
>> ionIdKeysKeyTypePut
>> 
>>
>> [4]*https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#!/operations#SubscriptionMultitple#subscriptionsMultiplePost
>> *
>>
>> [5]
>> [2018-02-15 17:31:01,903]  WARN - JAXRSUtils No operation matching
>> request path 
>> "/api/am/store/v0.11/applications/a9e14a8b-7906-42e9-9466-132c883db4ce/keys/PRODUCTION"
>> is found, Relative Path: 
>> /a9e14a8b-7906-42e9-9466-132c883db4ce/keys/PRODUCTION,
>> HTTP Method: GET, ContentType: */*, Accept: */*,. Please enable FINE/TRACE
>> log level for more details.
>> [2018-02-15 17:31:01,904]  WARN - WebApplicationExceptionMapper
>> javax.ws.rs.ClientErrorException: HTTP 404 Not Found
>> at org.apache.cxf.jaxrs.utils.SpecExceptions.toHttpException(Sp
>> ecExceptions.java:117)
>> at org.apache.cxf.jaxrs.utils.ExceptionUtils.toHttpException(Ex
>> ceptionUtils.java:169)
>> at org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRS
>> Utils.java:529)
>> at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processR
>> equest(JAXRSInInterceptor.java:177)
>> at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMe
>> ssage(JAXRSInInterceptor.java:77)
>> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(Phase
>> InterceptorChain.java:308)
>> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(C
>> hainInitiationObserver.java:121)
>> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke
>> (AbstractHTTPDestination.java:254)
>> at org.apache.cxf.transport.servlet.ServletController.invokeDes
>> tination(ServletController.java:234)
>> at org.apache.cxf.transport.servlet.ServletController.invoke(
>> ServletController.java:208)
>> at org.apache.cxf.transport.servlet.ServletController.invoke(
>> ServletController.java:160)
>> at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(
>> CXFNonSpringServlet.java:180)
>> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleR
>>

Re: [Dev] Issues while using Store REST API

2018-02-15 Thread Viduranga Gunarathne

Hi Sivaramya,

I checked the store REST API and the specific resource to get the key
details of an individual application that you have mentioned and couldn't
replicate the issue that you stated.

These are the steps that I followed.

1) Obtain the *clientId * and *clientSecret *from the token endpoint [1]
and then get the *accessToken *[1]
2) Send that access token as a header in the API call
3) This is the request path that I used

*https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
*


Can you please state the exact steps that you followed?

[1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide

Thanks,
Viduranga.

On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan 
wrote:

> Hi all,
>
> I'm trying to use store REST API to do  the following operations using the
> curl command. But for these operations I'm unable to get the response (I'm
> getting empty response). But in APIM 2.1.0  console I'm getting the error
> as [5]. What could be the reason for this?
>
>- Get key details of a given type as in [1]
>- Get scopes associated with a particular application based on
>subscribed APIs as in [2]
>- Update grant types and callback url of an application as in [3]
>- Add new subscriptions (multiple) as in [4]
>
>
> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
> html#!/operations#ApplicationIndividual#applicationsApplicat
> ionIdKeysKeyTypeGet
>
> [2] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
> html#!/operations#ApplicationIndividual#applicationsScopesApplicationIdGet
>
> [3] https://docs.wso2.com/display/AM2xx/apidocs/store/index.
> html#!/operations#ApplicationIndividual#applicationsApplicat
> ionIdKeysKeyTypePut
> 
>
> [4]*https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#!/operations#SubscriptionMultitple#subscriptionsMultiplePost
> *
>
> [5]
> [2018-02-15 17:31:01,903]  WARN - JAXRSUtils No operation matching request
> path "/api/am/store/v0.11/applications/a9e14a8b-7906-
> 42e9-9466-132c883db4ce/keys/PRODUCTION" is found, Relative Path:
> /a9e14a8b-7906-42e9-9466-132c883db4ce/keys/PRODUCTION, HTTP Method: GET,
> ContentType: */*, Accept: */*,. Please enable FINE/TRACE log level for more
> details.
> [2018-02-15 17:31:01,904]  WARN - WebApplicationExceptionMapper
> javax.ws.rs.ClientErrorException: HTTP 404 Not Found
> at org.apache.cxf.jaxrs.utils.SpecExceptions.toHttpException(
> SpecExceptions.java:117)
> at org.apache.cxf.jaxrs.utils.ExceptionUtils.toHttpException(
> ExceptionUtils.java:169)
> at org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(
> JAXRSUtils.java:529)
> at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(
> JAXRSInInterceptor.java:177)
> at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(
> JAXRSInInterceptor.java:77)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> PhaseInterceptorChain.java:308)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
> ChainInitiationObserver.java:121)
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(
> AbstractHTTPDestination.java:254)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(
> ServletController.java:234)
> at org.apache.cxf.transport.servlet.ServletController.
> invoke(ServletController.java:208)
> at org.apache.cxf.transport.servlet.ServletController.
> invoke(ServletController.java:160)
> at org.apache.cxf.transport.servlet.CXFNonSpringServlet.
> invoke(CXFNonSpringServlet.java:180)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(
> AbstractHTTPServlet.java:299)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.
> doGet(AbstractHTTPServlet.java:223)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.
> service(AbstractHTTPServlet.java:274)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:303)
> 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.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:218)
> at org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:122)
> at

Re: [Dev] WSO2 ESB and EI Clustering Guide

2018-02-15 Thread Pubudu Gunatilaka

Hi Chandana,

Thank you for pointing out. We will update the docs.

Thank you!

On Fri, Feb 16, 2018 at 3:27 AM, Chandana Napagoda 
wrote:

> Hi,
>
> I have noticed both ESB and EI products clustering guides recommending to
> use an external database(schema) to store local registry related data. If
> we use an external database such as MySQL, Oracle, there can be many issues
> when changing the mounting configuration, etc.
>
> This issue has been pointed before and added below note mentioning that we
> can use H2 database for the local registry[1]. However, the section below
> the above notice has not updated with proper configuration[2][3].
>
> [1]. https://docs.wso2.com/pages/diffpagesbyversion.
> action?pageId=47525766=11=6
> [2]. https://docs.wso2.com/display/EI611/Clustering+the+ESB+Profile#
> ClusteringtheESBProfile-Creatingthedatabases
> [3]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>
> Regards,
> Chandana
>
> --
>
> Blog: http://blog.napagoda.com
> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in visualizing an execution plan

2018-02-15 Thread Pamoda Wimalasiri

On Fri, Feb 16, 2018 at 4:49 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Hi Pamoda,
>
> I believe this will not affect the event processing cases and only happens
> when viewing the execution plan. Can you please report a github issue for
> this?
>
Yes. It does not affect the process.


>
> Thanks,
> Mohan
>
>
> On Thu, Feb 8, 2018 at 11:16 AM, Pamoda Wimalasiri 
> wrote:
>
>> Hi,
>>
>> The following error occurred when visualizing an execution plan with a
>> customized javascript function.
>>
>> [2018-02-08 11:11:53,907] ERROR {org.wso2.carbon.event.process
>> or.ui.executionPlan.flow.ExecutionPlanFlow} -  Error in visualizing
>> execution plan '/* Enter a unique ExecutionPlan */
>> @Plan:name('RiskScoreCalculator-AllowedIpRange-ip2-realtime1')
>>
>> /* Enter a unique description for ExecutionPlan */
>> @Plan:description('Detect logins outside the allowed ip range')
>>
>> define function ipToLong[JavaScript] return double {
>> var octetsOfIp = data[0].split(".");
>> var ipAddressAsLong = octetsOfIp[0]* 256 * 256 * 256
>> + octetsOfIp[1]* 256 * 256
>> + octetsOfIp[2] * 256
>> + octetsOfIp[3] * 1;
>> return ipAddressAsLong;
>> };
>>
>> /* define streams/tables and write queries here ... */
>>
>> @Import('org.wso2.is.analytics.stream.ProcessedOverallAuthen
>> tication:1.0.0')
>> define stream ProcessedOverallAuthentication (meta_tenantId int,
>> contextId string, eventId string, eventType string, authenticationSuccess
>> bool, username string, localUsername string, userStoreDomain string,
>> tenantDomain string, remoteIp string, region string, inboundAuthType
>> string, serviceProvider string, rememberMeEnabled bool, forceAuthEnabled
>> bool, passiveAuthEnabled bool, rolesCommaSeparated string,
>> authenticationStep string, identityProvider string, authStepSuccess bool,
>> stepAuthenticator string, isFirstLogin bool, identityProviderType string,
>> _timestamp long);
>>
>> @Export('org.wso2.is.analytics.stream.SuspiciousLoginAttempt:1.0.0')
>> define stream SuspiciousLoginAttempt (meta_tenantId int, username string,
>> userStoreDomain string, tenantDomain string, remoteIp string, region
>> string, _timestamp long, message string);
>>
>> from ProcessedOverallAuthentication[(authStepSuccess == true) AND
>> (eventType =='step') AND ipToLong(remoteIp) < ipToLong("123.56.7.8") OR
>> ipToLong(remoteIp) > ipToLong("123.9.9.1")]
>> select meta_tenantId, username, userStoreDomain, tenantDomain, remoteIp,
>> region, _timestamp, "WARNING : IP is not in the allowed range" as message
>> insert into SuspiciousLoginAttempt;
>> ', null
>> java.lang.NullPointerException
>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.
>> ExtractJsonValueImpl.setTriggerJsonValue(ExtractJsonValueImpl.java:202)
>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.
>> ExtractJsonValueImpl.setJsonValues(ExtractJsonValueImpl.java:123)
>> at org.wso2.carbon.event.processor.ui.executionPlan.flow.
>> ExecutionPlanFlow.getExecutionPlanFlow(ExecutionPlanFlow.java:37)
>> at org.apache.jsp.eventprocessor.execution_005fplan_005fdetails
>> _jsp._jspService(execution_005fplan_005fdetails_jsp.java:207)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>> rvice(ContextPathServletAdaptor.java:37)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>> (DelegationServlet.java:68)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.core.ApplicationDispatcher.invoke(Applic
>> ationDispatcher.java:743)
>> at org.apache.catalina.core.ApplicationDispatcher.doInclude(App
>> licationDispatcher.java:603)
>> at org.apache.catalina.core.ApplicationDispatcher.include(Appli
>> cationDispatcher.java:542)
>> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherA
>>

Re: [Dev] Error in visualizing an execution plan

2018-02-15 Thread Mohanadarshan Vivekanandalingam

Hi Pamoda,

I believe this will not affect the event processing cases and only happens
when viewing the execution plan. Can you please report a github issue for
this?

Thanks,
Mohan


On Thu, Feb 8, 2018 at 11:16 AM, Pamoda Wimalasiri  wrote:

> Hi,
>
> The following error occurred when visualizing an execution plan with a
> customized javascript function.
>
> [2018-02-08 11:11:53,907] ERROR {org.wso2.carbon.event.
> processor.ui.executionPlan.flow.ExecutionPlanFlow} -  Error in
> visualizing execution plan '/* Enter a unique ExecutionPlan */
> @Plan:name('RiskScoreCalculator-AllowedIpRange-ip2-realtime1')
>
> /* Enter a unique description for ExecutionPlan */
> @Plan:description('Detect logins outside the allowed ip range')
>
> define function ipToLong[JavaScript] return double {
> var octetsOfIp = data[0].split(".");
> var ipAddressAsLong = octetsOfIp[0]* 256 * 256 * 256
> + octetsOfIp[1]* 256 * 256
> + octetsOfIp[2] * 256
> + octetsOfIp[3] * 1;
> return ipAddressAsLong;
> };
>
> /* define streams/tables and write queries here ... */
>
> @Import('org.wso2.is.analytics.stream.ProcessedOverallAuthentication
> :1.0.0')
> define stream ProcessedOverallAuthentication (meta_tenantId int, contextId
> string, eventId string, eventType string, authenticationSuccess bool,
> username string, localUsername string, userStoreDomain string, tenantDomain
> string, remoteIp string, region string, inboundAuthType string,
> serviceProvider string, rememberMeEnabled bool, forceAuthEnabled bool,
> passiveAuthEnabled bool, rolesCommaSeparated string, authenticationStep
> string, identityProvider string, authStepSuccess bool, stepAuthenticator
> string, isFirstLogin bool, identityProviderType string, _timestamp long);
>
> @Export('org.wso2.is.analytics.stream.SuspiciousLoginAttempt:1.0.0')
> define stream SuspiciousLoginAttempt (meta_tenantId int, username string,
> userStoreDomain string, tenantDomain string, remoteIp string, region
> string, _timestamp long, message string);
>
> from ProcessedOverallAuthentication[(authStepSuccess == true) AND
> (eventType =='step') AND ipToLong(remoteIp) < ipToLong("123.56.7.8") OR
> ipToLong(remoteIp) > ipToLong("123.9.9.1")]
> select meta_tenantId, username, userStoreDomain, tenantDomain, remoteIp,
> region, _timestamp, "WARNING : IP is not in the allowed range" as message
> insert into SuspiciousLoginAttempt;
> ', null
> java.lang.NullPointerException
> at org.wso2.carbon.event.processor.ui.executionPlan.
> flow.ExtractJsonValueImpl.setTriggerJsonValue(
> ExtractJsonValueImpl.java:202)
> at org.wso2.carbon.event.processor.ui.executionPlan.
> flow.ExtractJsonValueImpl.setJsonValues(ExtractJsonValueImpl.java:123)
> at org.wso2.carbon.event.processor.ui.executionPlan.
> flow.ExecutionPlanFlow.getExecutionPlanFlow(ExecutionPlanFlow.java:37)
> at org.apache.jsp.eventprocessor.execution_005fplan_
> 005fdetails_jsp._jspService(execution_005fplan_005fdetails_jsp.java:207)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:439)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(
> ContextPathServletAdaptor.java:37)
> at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(
> ServletRegistration.java:61)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> processAlias(ProxyServlet.java:128)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.
> service(DelegationServlet.java:68)
> 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:743)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(
> ApplicationDispatcher.java:603)
> at org.apache.catalina.core.ApplicationDispatcher.include(
> ApplicationDispatcher.java:542)
> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.
> include(RequestDispatcherAdaptor.java:37)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$
> RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(
>

Re: [Dev] [Architecture] WSO2 Identity Server 5.4.1 Update2 Released !!!

2018-02-15 Thread Cyril Rognon

Hi team

Thank you for the good job !

Any idea about the release date of apim 2.2.0 to pair with is 5.4.x ?

Thanks
Cyril


Le 15 févr. 2018 10:27 PM, "Dinali Dabarera"  a écrit :

The WSO2 Identity and Access Management team is pleased to announce the
release of WSO2 Identity Server 5.4.1 Update2.
You can build the distribution from the source tag,

Runtime: https://github.com/ws 
o2/product-is/releases/tag/v5. 4.1-update2


follow the steps given below.

*Building from the source*

   1. Install Java8 or above
   2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
   3. Get the source,
  - For the Runtime: Get a clone from https://github.com/wso2/p
  roduct-is.git and checkout to v5.4.1-update2 tag or you can directly
  download the source for the tag from https://github.com/wso2/p
  
  roduct-is/releases/tag/v5.4.1-
  
  update2
  
   4. Run the one of the below maven commands from product-is directory,
  - *mvn** clean install* (To build the binary and source distributions
  with the tests)
  - *mvn** clean install -Dmaven.test.skip=true* (To build the binary
  and source distributions, without running any of the
unit/integration tests)
   5. You can find the wso2is-5.4.1-update2.zip binary distribution in
   product-is/modules/distribution/target directory.

What's new in WSO2 Identity Server 5.4.1 Update2

New Features & Bug Fixes: A list of new features and bug fixes shipped with
this release can be found here
.
Download

You can download WSO2 Identity Server 5.4.1 Update2 here

.
Contribute to WSO2 Identity ServerMailing Lists

Join our mailing lists and correspond with the developers directly. We also
encourage you to take part in discussions related to the product in the
architecture mailing list. If you have any questions regarding the product
you can use our StackOverflow forum to raise them as well.

   -

   Developer List: dev@wso2.org
   -

   Architecture List: architect...@wso2.org
   -

   User Forum: StackOverflow
   

Reporting Issues

We encourage you to report issues, improvements, and feature requests
regarding WSO2 Identity Server through our public WSO2 Identity Server GIT
Issues .


~ The WSO2 Identity and Access Management Team ~


-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933 <+94%2077%20019%208933>



















___
Architecture mailing list
architect...@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB and EI Clustering Guide

2018-02-15 Thread Chandana Napagoda

Hi,

I have noticed both ESB and EI products clustering guides recommending to
use an external database(schema) to store local registry related data. If
we use an external database such as MySQL, Oracle, there can be many issues
when changing the mounting configuration, etc.

This issue has been pointed before and added below note mentioning that we
can use H2 database for the local registry[1]. However, the section below
the above notice has not updated with proper configuration[2][3].

[1].
https://docs.wso2.com/pages/diffpagesbyversion.action?pageId=47525766=11=6
[2].
https://docs.wso2.com/display/EI611/Clustering+the+ESB+Profile#ClusteringtheESBProfile-Creatingthedatabases
[3]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database

Regards,
Chandana

-- 

Blog: http://blog.napagoda.com
Linkedin: https://www.linkedin.com/in/chandananapagoda/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Identity Server 5.4.1 Update2 Released !!!

2018-02-15 Thread Dinali Dabarera

The WSO2 Identity and Access Management team is pleased to announce the
release of WSO2 Identity Server 5.4.1 Update2.
You can build the distribution from the source tag,

Runtime: https://github.com/ws 
o2/product-is/releases/tag/v5. 4.1-update2


follow the steps given below.

*Building from the source*

   1. Install Java8 or above
   2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
   3. Get the source,
  - For the Runtime: Get a clone from https://github.com/wso2/p
  roduct-is.git and checkout to v5.4.1-update2 tag or you can directly
  download the source for the tag from https://github.com/wso2/p
  
  roduct-is/releases/tag/v5.4.1-
  
  update2
  
   4. Run the one of the below maven commands from product-is directory,
  - *mvn** clean install* (To build the binary and source distributions
  with the tests)
  - *mvn** clean install -Dmaven.test.skip=true* (To build the binary
  and source distributions, without running any of the
unit/integration tests)
   5. You can find the wso2is-5.4.1-update2.zip binary distribution in
   product-is/modules/distribution/target directory.

What's new in WSO2 Identity Server 5.4.1 Update2

New Features & Bug Fixes: A list of new features and bug fixes shipped with
this release can be found here
.
Download

You can download WSO2 Identity Server 5.4.1 Update2 here

.
Contribute to WSO2 Identity ServerMailing Lists

Join our mailing lists and correspond with the developers directly. We also
encourage you to take part in discussions related to the product in the
architecture mailing list. If you have any questions regarding the product
you can use our StackOverflow forum to raise them as well.

   -

   Developer List: dev@wso2.org
   -

   Architecture List: architect...@wso2.org
   -

   User Forum: StackOverflow
   

Reporting Issues

We encourage you to report issues, improvements, and feature requests
regarding WSO2 Identity Server through our public WSO2 Identity Server GIT
Issues .


~ The WSO2 Identity and Access Management Team ~


-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933 <+94%2077%20019%208933>





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

[Dev] [Architecture] BOSH Releases for WSO2 Identity Server Released!

2018-02-15 Thread Chiranga Alwis

WSO2 Installation Experience team is pleased to announce the release of
BOSH Releases for WSO2 Identity Server 5.4.0.

In this release, BOSH Releases for WSO2 Identity Server deployment patterns
have been introduced.

*Released Artifacts:*

   - https://github.com/wso2/pivotal-cf-is/releases/tag/v5.4.0.1

*Issues:*

   - https://github.com/wso2/pivotal-cf-is/issues

*How You Can Contribute*

Join our mailing list and correspond with the developers directly.

   - Developer List: dev@wso2.org
   - User List: u...@wso2.org

*Reporting Issues*

We encourage you to report issues and documentation faults regarding BOSH
releases by creating issues.

Thank you!
WSO2 Installation Experience Team

-- 
Yours sincerely,

*Chiranga Alwis*
Software Engineer | WSO2

*Mobile : *+94775930497 <+94%2077%20593%200497>
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
*Medium:* https://medium.com/@chirangaalwis


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

[Dev] WSO2 Docker and Docker Compose Resources Released!

2018-02-15 Thread Muhammed Shariq

WSO2 Installation Experience team is pleased to announce the release of
WSO2 Docker resources for following products.

   - WSO2 API Manager 2.1.0
   - WSO2 Identity Server 5.4.1
   - WSO2 Enterprise Integrator 6.1.1
   - WSO2 Stream Processor 4.0.0

Released Artifacts:

   - WSO2 Enterprise Integrator -
   https://github.com/wso2/docker-ei/releases/tag/v6.1.1.3
   - WSO2 API Manager -
   https://github.com/wso2/docker-apim/releases/tag/v2.1.0.3
   - WSO2 Identity Server -
   https://github.com/wso2/docker-is/releases/tag/v5.4.1.2
   - WSO2 Stream Processor -
   https://github.com/wso2/docker-sp/releases/tag/v4.0.0.1


Issues:

   - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues
   - WSO2 API Manager - https://github.com/wso2/docker-apim/issues
   - WSO2 Identity Server - https://github.com/wso2/docker-is/issues
   - WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues


*How You Can Contribute*

Join our mailing list and correspond with the developers directly.

   - Developer List: dev@wso2.org
   - User List: u...@wso2.org

*Reporting Issues*

We encourage you to report issues and documentation faults regarding WSO2
Docker resources through respective repositories by creating issues.

Thank you!

WSO2 Installation Experience Team.

-- 
Thanks,
Shariq
Associate Technical Lead
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Vagrant Resources Released!

2018-02-15 Thread Vimukthi Perera

WSO2 Installation Experience team is pleased to announce the release of
WSO2 Vagrant resources.


Released Artifacts:


WSO2 Enterprise Integrator v6.1.1.2 - https://github.com/wso2/vagrant-ei

WSO2 API Manager v2.1.0.2 - https://github.com/wso2/vagrant-apim

WSO2 Identity Server v5.4.1.1 - https://github.com/wso2/vagrant-is

WSO2 Vagrant Resources to create boxes for WSO2 Products v1.0.0 -
https://github.com/wso2/vagrant-boxes


Issues:

WSO2 Enterprise Integrator v6.1.1.2 - https://github.com/wso2/
vagrant-ei/issues

WSO2 API Manager v2.1.0.2 - https://github.com/wso2/vagrant-apim/issues

WSO2 Identity Server v5.4.1.1 - https://github.com/wso2/vagrant-is/issues

WSO2 Vagrant Resources to create boxes for WSO2 Products 1.0.0 -
https://github.com/wso2/vagrant-boxes/issues


How You Can Contribute

Join our mailing list and correspond with the developers directly.

Developer List: dev@wso2.org

User List: u...@wso2.org


Reporting Issues
We encourage you to report issues and documentation faults regarding WSO2
Vagrant resources through respective repositories by creating issues.

Thank you!

WSO2 Installation Experience Team

Vimukthi Perera
Software Engineer
WSO2 Inc.

Email: vimuk...@wso2.com
Mobile: +94771153999
Web: http://wso2.com

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

[Dev] Vagrant Resources for WSO2 Stream Processor 4.0.0 Released!

2018-02-15 Thread Ching Tien Shi

WSO2 Installation Experience team is pleased to announce the release of
Vagrant resources for WSO2 Stream Processor 4.0.0.

*Released Artifacts* - https://github.com/wso2/vagrant-sp

*Issues* - https://github.com/wso2/vagrant-sp/issues

*How Can You Contribute*

Join our mailing list and correspond with the developers directly.

   - Developer List: dev@wso2.org
   - User List: u...@wso2.org

*Reporting Issues*

We encourage you to report issues and documentation faults regarding WSO2
Vagrant resources through respective repositories by creating issues.

Thank you!

WSO2 Installation Experience Team

Ching Shi
Software Engineer
WSO2

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

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

2018-02-15 Thread Afkham Azeez

Yeah get rid of it!

On Thu, Feb 15, 2018 at 7:11 PM, Sagara Gunathunga  wrote:

>
> It seems -Dsetup is broken in some products, the correct action should be
> get rid of this non-production feature instead of fixing. Going forward we
> will remove relevant doc content from IS 5.0.0 and will try to remove code
> from next release.
>
> Thanks !
>
> On Fri, May 6, 2016 at 1:31 PM, Isuru Perera  wrote:
>
>> Hi Sameera,
>>
>> Thanks for confirming!
>>
>> So, the products also should not try to implement this feature. (This is
>> what I wanted to confirm. Not just implementing -Dsetup support in C5).
>>
>> On Fri, May 6, 2016 at 1:24 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> As I've explained earlier. We will not implement -Dsetup support in C5.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Fri, May 6, 2016 at 1:11 PM, Isuru Perera  wrote:
>>>
 Yes. -Dsetup is easier, but let's avoid setting up database from the
 server. In Wiki, we can give instructions on setting up databases for each
 vendor.

 Carbon Team, could you please let us know your conclusion on this?

 On Wed, May 4, 2016 at 4:55 PM, Isuru Haththotuwa 
 wrote:

> Hi Sagara,
>
> On Fri, Apr 29, 2016 at 5:31 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Fri, Apr 29, 2016 at 4:21 PM, Isuru Perera 
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> As Thilini mentioned, most of the products need a database to keep
>>> data. With -Dsetup we could execute scripts based on the vendor. We need
>>> some way of setting up the database in C5 as well.
>>>
>>> I'm sorry I couldn't create a JIRA for $subject yet.
>>>
>>> In C5, what is the recommended way to setup a database (by creating
>>> required tables) for a WSO2 product?
>>>
>>> On Fri, Apr 29, 2016 at 3:45 PM, Thilini Cooray 
>>> wrote:
>>>
 Hi,

 In many of our carbon 4.x.x based products, we use -Dsetup option
 allowing users to create databases on their preferred vendor (instead 
 of
 our inbuilt H2 database).
 Without this option, users will have to run database scripts
 against each of the databases by themselves prior to server startup.

 Therefor I think it is a useful option to have in C5.

>>>
>>  I'm -1 to include this option into C5 products due to following
>> reasons.
>>
>> 1.) This option available with C4 product is just a demoware only,
>> nobody use this option to populate databases in production systems.
>> Recommended practise for production environments is  DB admin/team 
>> populate
>> databases manually and create user with limited privileges so that
>> applications use this limited-privileged user to access the database
>> server.
>>
>
>> 2.) In production systems, those admin rights are not anyway assign
>> to generic users hence not usable feature even if we include this option 
>> it
>> will use for demos only. Also previously we found some lazy practises 
>> where
>> developer assumed DB user always got admin rights and try to perform DB
>> admin tasks through our Java codes[1].
>>
>> 3.) Having this option in production systems increase security risks.
>>
> Fully agreed that this should not be the recommended method for
> creating DB tables in production environments. However IMHO the ease of
> trying out/demonstrating is very important.
>
> As an example scenario, we are focusing more and more on making wso2
> products container friendly and easy to try out. A user trying out a
> distributed deployment deployment on a containerized environment (docker,
> kubernetes, etc.) will expect to deploy it with minimal steps: start a
> mysql container and start the products pointing to the mysql container. If
> a method similar to -Dsetup is available, it will make the life of the 
> user
> much easier, rather than having to run the DB scripts manually.
>
>
> [1] - "TrustedIdPDBInitializer Class should not create any tables,
> indexes when -Dsetup is not given"
>
>
> Thanks !
>
>>
>>> Thanks.
>>>
>>> On Fri, Apr 29, 2016 at 3:24 PM, Sameera Jayasoma 
>>> wrote:
>>>
 Hi Isuru,

 Can you explain the need to have a -Dsetup option? Can we simply
 remove this in C5?

 Thanks,
 Sameera.


 On Fri, Mar 25, 2016 at 1:45 PM, Isuru Perera 
 wrote:

> Hi,
>
> In Carbon 4.x.x, we extend [1] 
> org.wso2.carbon.utils.dbcreator.DatabaseCreator
> [2]. How can we do the same in Carbon 5?

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

2018-02-15 Thread Sagara Gunathunga

It seems -Dsetup is broken in some products, the correct action should be
get rid of this non-production feature instead of fixing. Going forward we
will remove relevant doc content from IS 5.0.0 and will try to remove code
from next release.

Thanks !

On Fri, May 6, 2016 at 1:31 PM, Isuru Perera  wrote:

> Hi Sameera,
>
> Thanks for confirming!
>
> So, the products also should not try to implement this feature. (This is
> what I wanted to confirm. Not just implementing -Dsetup support in C5).
>
> On Fri, May 6, 2016 at 1:24 PM, Sameera Jayasoma  wrote:
>
>> Hi Isuru,
>>
>> As I've explained earlier. We will not implement -Dsetup support in C5.
>>
>> Thanks,
>> Sameera.
>>
>> On Fri, May 6, 2016 at 1:11 PM, Isuru Perera  wrote:
>>
>>> Yes. -Dsetup is easier, but let's avoid setting up database from the
>>> server. In Wiki, we can give instructions on setting up databases for each
>>> vendor.
>>>
>>> Carbon Team, could you please let us know your conclusion on this?
>>>
>>> On Wed, May 4, 2016 at 4:55 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Sagara,

 On Fri, Apr 29, 2016 at 5:31 PM, Sagara Gunathunga 
 wrote:

>
>
> On Fri, Apr 29, 2016 at 4:21 PM, Isuru Perera  wrote:
>
>> Hi Sameera,
>>
>> As Thilini mentioned, most of the products need a database to keep
>> data. With -Dsetup we could execute scripts based on the vendor. We need
>> some way of setting up the database in C5 as well.
>>
>> I'm sorry I couldn't create a JIRA for $subject yet.
>>
>> In C5, what is the recommended way to setup a database (by creating
>> required tables) for a WSO2 product?
>>
>> On Fri, Apr 29, 2016 at 3:45 PM, Thilini Cooray 
>> wrote:
>>
>>> Hi,
>>>
>>> In many of our carbon 4.x.x based products, we use -Dsetup option
>>> allowing users to create databases on their preferred vendor (instead of
>>> our inbuilt H2 database).
>>> Without this option, users will have to run database scripts against
>>> each of the databases by themselves prior to server startup.
>>>
>>> Therefor I think it is a useful option to have in C5.
>>>
>>
>  I'm -1 to include this option into C5 products due to following
> reasons.
>
> 1.) This option available with C4 product is just a demoware only,
> nobody use this option to populate databases in production systems.
> Recommended practise for production environments is  DB admin/team 
> populate
> databases manually and create user with limited privileges so that
> applications use this limited-privileged user to access the database
> server.
>

> 2.) In production systems, those admin rights are not anyway assign to
> generic users hence not usable feature even if we include this option it
> will use for demos only. Also previously we found some lazy practises 
> where
> developer assumed DB user always got admin rights and try to perform DB
> admin tasks through our Java codes[1].
>
> 3.) Having this option in production systems increase security risks.
>
 Fully agreed that this should not be the recommended method for
 creating DB tables in production environments. However IMHO the ease of
 trying out/demonstrating is very important.

 As an example scenario, we are focusing more and more on making wso2
 products container friendly and easy to try out. A user trying out a
 distributed deployment deployment on a containerized environment (docker,
 kubernetes, etc.) will expect to deploy it with minimal steps: start a
 mysql container and start the products pointing to the mysql container. If
 a method similar to -Dsetup is available, it will make the life of the user
 much easier, rather than having to run the DB scripts manually.


 [1] - "TrustedIdPDBInitializer Class should not create any tables,
 indexes when -Dsetup is not given"


 Thanks !

>
>> Thanks.
>>
>> On Fri, Apr 29, 2016 at 3:24 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Can you explain the need to have a -Dsetup option? Can we simply
>>> remove this in C5?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Fri, Mar 25, 2016 at 1:45 PM, Isuru Perera 
>>> wrote:
>>>
 Hi,

 In Carbon 4.x.x, we extend [1] 
 org.wso2.carbon.utils.dbcreator.DatabaseCreator
 [2]. How can we do the same in Carbon 5?

 Thanks!

 [1] https://github.com/search?l==DatabaseCreator++user%
 3Awso2=advsearch=Code=%E2%9C%93
 [2] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/
 org.wso2.carbon.utils/src/main/java/org/wso2/carbon/

[Dev] Issues while using Store REST API

2018-02-15 Thread Sivaramya Sivanathan

Hi all,

I'm trying to use store REST API to do  the following operations using the
curl command. But for these operations I'm unable to get the response (I'm
getting empty response). But in APIM 2.1.0  console I'm getting the error
as [5]. What could be the reason for this?

   - Get key details of a given type as in [1]
   - Get scopes associated with a particular application based on
   subscribed APIs as in [2]
   - Update grant types and callback url of an application as in [3]
   - Add new subscriptions (multiple) as in [4]


[1] https://docs.wso2.com/display/AM2xx/apidocs/store/
index.html#!/operations#ApplicationIndividual#applicationsApplicationIdKeysK
eyTypeGet

[2] https://docs.wso2.com/display/AM2xx/apidocs/store/
index.html#!/operations#ApplicationIndividual#applicationsScopesApplicationI
dGet

[3] https://docs.wso2.com/display/AM2xx/apidocs/store/
index.html#!/operations#ApplicationIndividual#applicationsApplicationIdKeysK
eyTypePut


[4]*https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#!/operations#SubscriptionMultitple#subscriptionsMultiplePost
*

[5]
[2018-02-15 17:31:01,903]  WARN - JAXRSUtils No operation matching request
path
"/api/am/store/v0.11/applications/a9e14a8b-7906-42e9-9466-132c883db4ce/keys/PRODUCTION"
is found, Relative Path:
/a9e14a8b-7906-42e9-9466-132c883db4ce/keys/PRODUCTION, HTTP Method: GET,
ContentType: */*, Accept: */*,. Please enable FINE/TRACE log level for more
details.
[2018-02-15 17:31:01,904]  WARN - WebApplicationExceptionMapper
javax.ws.rs.ClientErrorException: HTTP 404 Not Found
at
org.apache.cxf.jaxrs.utils.SpecExceptions.toHttpException(SpecExceptions.java:117)
at
org.apache.cxf.jaxrs.utils.ExceptionUtils.toHttpException(ExceptionUtils.java:169)
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:529)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:177)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:77)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:254)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:299)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:274)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
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.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
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.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:958)
at

[Dev] WSO2 API Manager 3.0.0-M18 Released!

2018-02-15 Thread Malintha Amarasinghe

The WSO2 API Manager team is pleased to announce the release of API Manager
3.0.0-M18. It's now available to download.

Distribution

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

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


Documentation

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

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

   -
   
https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=label%3A3.0.0+milestone%3A3.0.0-m18+is%3Aclosed+label%3A%22Type%2FNew+Feature%22+

Bug Fixes

   -


   
https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+milestone%3A3.0.0-m18+label%3AType%2FBug+
   -


   
https://github.com/wso2/carbon-auth/issues?q=is%3Aissue+is%3Aclosed+closed%3A2018-02-09..2018-02-15+label%3AType%2FBug

Improvements and Takss

   -
   
https://github.com/wso2/carbon-auth/issues?q=is%3Aissue+is%3Aclosed+closed%3A2018-02-09..2018-02-15+label%3AType%2FImprovement

List of Open Issues

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


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
.

~ WSO2 API Manager Team ~


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

Mobile : +94 712383306 <+94%2071%20238%203306>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Announce] [Architecture] WSO2 Enterprise Integrator 6.1.1-update21 Released !

2018-02-15 Thread Malaka Gangananda

Hi All,

The WSO2 Integration team is pleased to announce the release of Enterprise
Integrator 6.1.1-update21. It is available for download from here

.

*Tasks/Bug Fixes and Improvements*

   - https://github.com/wso2/product-ei/milestone/29?closed=1
   - https://wso2.org/jira/issues/?filter=14520


*Issues*

   - https://wso2.org/jira/issues/?filter=13994
   - https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue


*Documentation*

   -
   https://docs.wso2.com/display/EI611/WSO2+Enterprise+Integrator+Documentation



*How To Contribute*
Your feedback is most welcome!

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

*Mailing Lists*
Join our mailing lists and correspond with the developers directly.

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

WSO2 Architecture List: architect...@wso2.org

User Forum : StackOverflow 

~ The WSO2 Integration Team ~

Thanks,
-- 
Malaka.
-- 
Malaka Gangananda - Software Engineer | WSO2
Email : mala...@wso2.com
Mobile : +94713564340
Web : http://wso2.com
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clustering in WSO2 EI 6.1.1

2018-02-15 Thread dhanya

Got it now. Thanks Senduran for the quick reply. 



--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues while using Store REST API

Re: [Dev] Issues while using Store REST API

Re: [Dev] Issues while using Store REST API

Re: [Dev] Issues while using Store REST API

Re: [Dev] CLI Client for MB4 using GoLang

Re: [Dev] CLI Client for MB4 using GoLang

[Dev] Metrics databases for IS and EI

Re: [Dev] Issues while using Store REST API

Re: [Dev] Issues while using Store REST API

Re: [Dev] WSO2 ESB and EI Clustering Guide

Re: [Dev] Error in visualizing an execution plan

Re: [Dev] Error in visualizing an execution plan

Re: [Dev] [Architecture] WSO2 Identity Server 5.4.1 Update2 Released !!!

[Dev] WSO2 ESB and EI Clustering Guide

[Dev] WSO2 Identity Server 5.4.1 Update2 Released !!!

[Dev] [Architecture] BOSH Releases for WSO2 Identity Server Released!

[Dev] WSO2 Docker and Docker Compose Resources Released!

[Dev] WSO2 Vagrant Resources Released!

[Dev] Vagrant Resources for WSO2 Stream Processor 4.0.0 Released!

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

[Dev] Issues while using Store REST API

[Dev] WSO2 API Manager 3.0.0-M18 Released!

[Dev] [Announce] [Architecture] WSO2 Enterprise Integrator 6.1.1-update21 Released !

Re: [Dev] Clustering in WSO2 EI 6.1.1

25 matches

Site Navigation

Mail list logo

Footer information