Re: [Architecture] [Dev] Personal information export API

2018-02-07 Thread Maduranga Siriwardena
Hi all, Based on the discussions had offline we did few changes to the api. We have come up with 3 endpoints. /api/identity/user/v1.0/me Get the personal information of authenticated user. /api/identity/user/v1.0/pi-info/{userId} Get the personal information of the user with the given id. Users

Re: [Architecture] [MB4] Durable queue spilling mode

2018-02-07 Thread Shazni Nazeer
Hi Asanka, +1 for the idea. I think this will bring down the memory footprint significantly. I would also like to suggest to have queue wise configurable in memory limit, if that's not in your plan as of now. Say we have two queues A and B. And we know queue A will be heavily populated and consum

[Architecture] [IS] REST endpoint for Claim Management in IS

2018-02-07 Thread Chiran Wijesekara
Hi all, we have decided to create a REST endpoint for the purpose of claim management of WSO2 Identity Server future versions. Currently, ClaimMetaDataManagement Service is exposed as a SOAP endpoint as per the documentation provided under [1]. As the first step toward the above effort, the prosp

Re: [Architecture] Support FIDP initiated logout with new identity framework

2018-02-07 Thread Dimuthu Leelarathne
Hi Darshana, Would the core IS team provide a method for this (terminate framework level session) functionality? thanks, Dimuthu On Wed, Feb 7, 2018 at 2:33 PM, Malithi Edirisinghe wrote: > > > On Wed, Feb 7, 2018 at 2:32 AM, Johann Nallathamby > wrote: > >> It is in fact an inbound connecto

Re: [Architecture] Support FIDP initiated logout with new identity framework

2018-02-07 Thread Kanapriya Kuleswararajan
Hi All, For the moment, as per the off-line discussion with Malithi and Johann, I have tried to move the code to *identity-outbound-auth-samlsso* to make this feature compatible with new identity framework. But I have get the code [1] (without adding the changes related to this feature) and repl

Re: [Architecture] CLI Client for the Message Broker

2018-02-07 Thread Dakshika Jayathilaka
Hi All, IMO we need to support basic level features such as *--help*, *--version* and *--verbose* on each CLI tool that we are building. Also, we need to think about the standard output for each scenario as well. Shall we add few samples for that as well? Regards, *Dakshika Jayathilaka* PMC Mem

Re: [Architecture] [GDPR] API Manager 3.0.0 GDPR Support

2018-02-07 Thread Ishara Karunarathna
Hi Sanjeewa, On Tue, Feb 6, 2018 at 12:33 PM, Sanjeewa Malalgoda wrote: > > > On Mon, Feb 5, 2018 at 11:29 PM, Ishara Karunarathna > wrote: > >> HI Sanjeewa, >> >> Pseudonym user ID (User ID) is not only limited to GDPR requirements but >> its really useful supporting features like changing use

Re: [Architecture] Support FIDP initiated logout with new identity framework

2018-02-07 Thread Johann Nallathamby
On Wed, Feb 7, 2018 at 2:33 PM, Malithi Edirisinghe wrote: > > > On Wed, Feb 7, 2018 at 2:32 AM, Johann Nallathamby > wrote: > >> It is in fact an inbound connector. So +1 to use the inbound framework >> and write a InboundProcessor to process this request. This way we can have >> an abstract Fe

Re: [Architecture] Support FIDP initiated logout with new identity framework

2018-02-07 Thread Malithi Edirisinghe
On Wed, Feb 7, 2018 at 2:32 AM, Johann Nallathamby wrote: > It is in fact an inbound connector. So +1 to use the inbound framework and > write a InboundProcessor to process this request. This way we can have an > abstract FederatedIdPInitiatedLogoutProcessor (you may come up with a > different na