[Dev] Missing Attributes in Token Introspection Response

Hi Indunil, Form token introspection response I can get below attributes. {"scope":"openid","active":true,"token_type":"Bearer","exp":1503061170,"iat":1503057570,"client_id":"oRbEK6KkycbSLGxt3JHciaitPzoa","username":"admin@carbon.super "} But some of optional attributes are not included in

Re: [Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

Hi Abimaran and all, Is the requirement to expose as SPI service something introduced in Carbon 5? I am curious on how it worked with APIM 2.1.0. Can't we do the same thing? On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan wrote: > Hi, > > We are embedding Message

Re: [Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

+Thusitha, +Jayanga On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan wrote: > Hi, > > We are embedding Message Broker feature into API Manager 3.0 core, now API > Manager will function as both MB server and client to manage its artifacts > such as API, application,

[Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

Hi, We are embedding Message Broker feature into API Manager 3.0 core, now API Manager will function as both MB server and client to manage its artifacts such as API, application, subscription, throttling etc between its nodes and Gateway. andes-client [1] will function as JMS client for embedded

Re: [Dev] [IS] Need to get the consent page back in SSO flow

Hi Isura & Indunil, On Fri, Aug 18, 2017 at 6:58 PM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > Hi Naduni, > > This was an improvement for IS 5.2.0 (Refer [1] for more information). As > isura mentioned, you can use "updateApproveAlwaysForAppCons > entByResourceOwner" in

Re: [Dev] [IS] Need to get the consent page back in SSO flow

Hi Indunil, On Fri, Aug 18, 2017 at 7:16 PM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > > Hi, > On Fri, Aug 18, 2017 at 3:12 PM, Naduni Pamudika wrote: > >> Hi All, >> >> In the SSO flow, first the login page appears and then the consent page where >> the scopes

Re: [Dev] Display the roles of a custom user store for Identity Server

Hi Thomas, It is wrong to set tenantId as follows for carbon.super tenant. Super tenant's tenantID is -1234. Can you attach full exception stacktrace. carbonContext.setTenantId(64302); Thanks Isura. On Fri, Aug 18, 2017 at 6:50 PM, Thomas LEGRAND < thomas.legr...@versusmind.eu> wrote: >

Re: [Dev] Improve Default Claim Handler logic

Hi Farasath, The logic behind returning claims in 'oidc' is based on the intersection of both sp requested claims and the registry defined claims for the scope. So in order to return a specific claims it should define in the registry and it should define as a requested claims. 2. Improve the

Re: [Dev] Improve Default Claim Handler logic

yes, we should get rid of unwanted processing. IMO we should honour the configured requested claims in the service provider. But I'm not aware whether there was a need to send all the claims for open id. On Sat, Aug 19, 2017 at 7:48 PM, Farasath Ahamed wrote: > Hi All, >

Re: [Dev] Summarization of JSON data in DAS

Hi Grainier, Thanks for the reply. I had a discussion with Nirmal and the final solution was to use Siddhi Map extension as you also suggesting. However we change our approach later to push avg data directly from the device agent, than computing them in DAS. (EDGE analytics) Anyway thanks for

Re: [Dev] Summarization of JSON data in DAS

Hi Lahiru, You can achieve that by using JSON custom mapping [1] + Siddhi MAP extension + IfThenElse (optional to check the availability of attributes). Basically what you have to do is, have a; JSON structure like this; > > { >"userData": { >"timestamp": 19900813115534, > >

Re: [Dev] Where is the create publishers, streams and receivers page in wso2das-4.0.0-M6

Hi Sagar, >From SP 4.0.0-MX [1] (formerly DASw-4.0.0-MX) <, we don't have a management console page (localhost:9443/carbon). Instead, we have the editor. Also, there are some changes to key concepts such as receivers and publishers. Instead of receivers and publishers, we have a new concept

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

Hi all, Thanks for the feedback. I have fixed the issues mentioned in the review comments and also made some modifications. Please review. Regards, Abilashini *Thiyagarajah Abilashini* Student Department of Computer Science and Engineering University of Moratuwa, Sri Lanka On 11 August 2017

Re: [Dev] Invitation: [GSoC][APIM] Environment Support for API Manager weekly ... @ Fri Aug 18, 2017 2:30pm - 3:30pm (Ravindu Perera)

Hi Meeting Notes . - Discussed on how to fix the issue CROS and tried some of the suggested once. - Planned what should be done within the next week. - discussed on putting an PR on Monday. Thank you Ravindu Perera On Fri, Aug 18, 2017 at 2:08 PM, Kasun Thennakoon