[Dev] Dynamic client registration request fails due to no user information in the request header.

Hi, In OIDC dynamic client registration, in the request header we need to send an already existing user and the password to register a client in WSO2 Identity server.In OIDC specification[1], It is not mandatory to send user details to register a client. When running the OIDC test suite for

Re: [Dev] Dynamic client registration request fails due to no user information in the request header.

Based on the spec, To support open Dynamic Registration, the Client Registration Endpoint > SHOULD accept registration requests without OAuth 2.0 Access Tokens. These > requests MAY be rate-limited or *otherwise limited to prevent a > denial-of-service attack* on the Client Registration Endpoint.

[Dev] WSO2 ESB Broker Re-Connection in case of Broker Failure

Hi, I am trying to setup a connection to the WSO2 MB from the WSO2 ESB, in a way that in case of a Broker failure or shutdown, ESB be able to handle that and reconnect to it once Broker is up and running. I have this setup in axis2.xml:

Re: [Dev] remoteInstance port for registry when configuring API manager cluster

Hi Feng, It's the URL of the remote instance which depends on the port offset. You can refer https://docs.wso2.com/display/Governance540/Remote+Instance+and+Mount+Configuration+Details . On Thu, Sep 14, 2017 at 6:41 AM, Feng Xu wrote: > Hi all, > > I'm following this article

Re: [Dev] [Siddhi] TestUtility to throw Assertion Errors from main thread

Thanks for the improvement it looks good. I have merged. But I think it should be called as Test*Callback *with a simple b. Can you fix that. Thanks Suho On Mon, Sep 4, 2017 at 5:18 PM, Gobinath wrote: > Hi, > > As per my experience during my GSoC project, the

Re: [Dev] Multiple scopes for REST resources in APIM Store and Publisher

+1. We need to add this support. If there are multiple scopes associated with resource at least one of them need to be there in token scopes. Thanks, sanjeewa. On Fri, Sep 15, 2017 at 8:16 AM, Harsha Kumara wrote: > We created a github issue to track this

[Dev] Fwd: Call Third party web service and Enriching the original message

+Dev -- Forwarded message -- From: Vivek Kumar Date: Fri, Sep 15, 2017 at 10:47 AM Subject: Call Third party web service and Enriching the original message To: "mal...@wso2.com" Hi Malaka, I have below requirement.I have generated below

Re: [Dev] pattern for one to many match or multi match events ?

Hi Grainier, even table approach make sense, but is there a way to limit the event table to keep the events for let say 24 hour or so and then discard it ? Thanks for looking into this. Jay On Thu, Sep 14, 2017 at 11:51 PM, Grainier Perera wrote: > Hi Jay, > > In your

[Dev] pattern for one to many match or multi match events ?

Hello WSO2 community. I am trying to implement a siddhi query where 1 event in publisher can have multiple event in subscriber. this fits well in pattern query but it looks like it outputs as soon as 1 event is matched and there is no way to window or tell the count. here is the execution plan i

Re: [Dev] pattern for one to many match or multi match events ?

Hi Jay, In your pattern, when a match found, it will discard that event (e1 in your scenario), so it won't get compared with other events. However, if you need to hold that event and match it with more than a single event, then you can use an event table as shown below.

Re: [Dev] [Siddhi] TestUtility to throw Assertion Errors from main thread

No worries, thanks for the update! Suho On Sat, Sep 16, 2017 at 3:09 AM Gobinath wrote: > Hi, > > My last PR contains a check-style issue which causes to Sidhhi build > failure. Please merge my new PR #526 > which fixes the

Re: [Dev] [Siddhi] TestUtility to throw Assertion Errors from main thread

Hi, My last PR contains a check-style issue which causes to Sidhhi build failure. Please merge my new PR #526 which fixes the check-style issue and also includes your suggestion. Sorry for the check-style issue. I sent that PR just to make sure the