Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator

Hi Madhawa, We have fixed the issue. Please check and let us know. Thanks, Ramindu. On Wed, Jul 5, 2017 at 10:33 AM, Ramindu De Silva wrote: > Hi Madhawa, > > Yes, Simulation configuration should be within inverted commas. I will > fix it and let you know. > > Best Regards,

Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator

Hi Madhawa, Yes, Simulation configuration should be within inverted commas. I will fix it and let you know. Best Regards, Ramindu. On Wed, Jul 5, 2017 at 9:49 AM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > Small correction to my previous mail, actually I was

Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator

Hi, Small correction to my previous mail, actually I was using *GET* http:// :/simulation/feed/{simulationName}, and got the mentioned response from it. I was *not* using /simulation/single endpoint. Any help you can provide is most welcome! On Wed, Jul 5, 2017 at 9:41 AM, Sriskandarajah

Re: [Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator

I don't think you can send a simulation config by calling http:// :/simulation/single/ @Mohan/Ramindu can you guide him on the API of DAS 4.0 Event Simulation On Tue, Jul 4, 2017 at 9:48 PM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > > I am currently working on

Re: [Dev] how to connect custom streaming api's in WSO2 EI-6.1.1

Hi Bala, Doc in [1] will help you to write a custom inbound endpoint. [1] https://docs.wso2.com/display/EI611/Custom+Inbound+Endpoint#CustomInboundEndpoint-CustomPolling On Wed, Jul 5, 2017 at 5:09 AM, Jasintha Dasanayake wrote: > HI Malaka > > In this case, this guy need

Re: [Dev] Handling required claims in ID Token

Thank you Sagara for the response. Yes, as you mentioned it means logical to use the server error response. will proceed with that. Thanks, On Tue, Jul 4, 2017 at 7:08 PM, Sagara Gunathunga wrote: > > > On Tue, Jul 4, 2017 at 6:54 PM, Denuwanthi De Silva

Re: [Dev] [GSoC][SCIM] SCIM 2.0 Test Dependencies

Hi All, Adjusting test *Dynamically* at runtime is wrong. Tests has to be exact and precise. What we should do is to add new tests specifically to target the change in schema/schema extensions. Still each test should not be dynamic. We will end up with many test cases, but each single test only

Re: [Dev] [GSoC][SCIM] SCIM 2.0 Test Dependencies

Since this is a 'compliance test suite' it makes sense to terminate the tests at the point where it deviates from the spec. However, it would be nice to have an option to run certain tests even if some of the said critical tests fail, especially the tests related to sp configs and schemas . The

[Dev] [GSOC][DAS][DEV] Incorrect response from DAS 4.0 Event Simulator

Hi, I am currently working on developing a Python Client for DAS 4.0 Event Simulator as a part of my GSOC project with WSO2. When I used the REST endpoint *GET* http:// :/simulation/single/{simulationName}, I get a JSON response with an incorrect field value. The JSON response consist of two

Re: [Dev] Handling required claims in ID Token

On Tue, Jul 4, 2017 at 6:54 PM, Denuwanthi De Silva wrote: > Hi, > > In OIDC spec,following claims are mentioned as mandatory. > -iss > -sub > -aud > -exp > -iat > > Currently as mentioned in jira [1], it is possible to write custom OAuth2 > grant type which returns IDToken

[Dev] Handling required claims in ID Token

Hi, In OIDC spec,following claims are mentioned as mandatory. -iss -sub -aud -exp -iat Currently as mentioned in jira [1], it is possible to write custom OAuth2 grant type which returns IDToken without "sub" claim. When we handle this scenario, there is a small concern that need to be

Re: [Dev] Modifying Carbon-Messaging Client Connector

Hi, I have a different perspective on this. What if we come up with our own session interface that can be used across > all the transports. For instance, in case of, websockets, I suppose > following are the APIs we want, > > - getID() > - write() // this should be able to handle text and binary

Re: [Dev] Fixing the cache mediator

Hi all, Thank you for the suggestions. Yes the mediator should also work with the call mediator. Further on a discussion with the APIM team I have identified the following issues which points to requiring a rewrite of the cache mediator: 1. Current cache mediator[1] caches responses for

Re: [Dev] Issue in the deployment of WSO2am docker image in to aws EC2 container service

On Mon, Jul 3, 2017 at 8:17 PM, Pubudu Gunatilaka wrote: > Hi, > > Server log looks okay. Can you check whether api manager is running in the > container? I guess you should be able to login to the container. Maybe you > can telnet and check 9443 port is up and running. > >

Re: [Dev] Fixing the cache mediator

Hi, On Tue, Jul 4, 2017 at 3:10 PM, Vijitha Ekanayake wrote: > Hi Riyafa, > > Apart from the issues that you have mentioned, we may need to consider > following points while refactoring the cache mediator implementation. > > 1). Verify the cache mediator functionality with

Re: [Dev] Modifying Carbon-Messaging Client Connector

Hi All, What if we come up with our own session interface that can be used across all the transports. For instance, in case of, websockets, I suppose following are the APIs we want, - getID() - write() // this should be able to handle text and binary payloads - close() - isValid() On Thu, Jun

Re: [Dev] Fixing the cache mediator

Hi Riyafa, Apart from the issues that you have mentioned, we may need to consider following points while refactoring the cache mediator implementation. 1). Verify the cache mediator functionality with different configuration parameters and fix if there is anything broken. 2). Implement a

[Dev] [IS] Federated access for user with multiple email addresses

Hello guys, I have a question regarding user account with multiple email adresses trying to access different tenants; Is there a way to handle such type of user knowing that the use case consists of creating a user in ADFS and federating his access to WSO2, this user is supposed to have access

[Dev] Fixing the cache mediator

Dear all, By going through the issues faced by the customers in the past I discovered the following issues: 1. Continue the execution on cache hit. Reported as an issue in github[1] 2. Issue in processing JSON array (payload) with a single element when response caching is enabled where