Re: [Architecture] [IAM] SCIM 2.0 Outbound Connector

2018-02-12 Thread Gayan Gunawardana
On Mon, Feb 12, 2018 at 12:11 PM, Isuranga Perera wrote: > Hi Gayan, > > Currently working on the configuration option. Sure I'll move changes to > *identity-outbound-provisioning-scim*. > Thank you very much for the contribution. > > Best Regards > Isuranga Perera >

[Architecture] [IS] Personal information export UI option

2018-02-12 Thread Ayesha Dissanayaka
Hi all, We have implemented Personal information export API as discussed in the mail thread [1]. In order to enable this capability in the the user-portal UI, we are planing to provide *"Download UserInfo"* option in the *"User Profile"* gadget in the "Dashboard -

Re: [Architecture] [X509 Authenticator] Certificate Revocation Verification with CRL and OCSP

2018-02-12 Thread Indunil Upeksha Rathnayake
Adding Azeez On Mon, Feb 12, 2018 at 10:28 AM, Maheshika Goonetilleke wrote: > hi Azeez > > Please confirm. > > On Mon, Feb 12, 2018 at 10:26 AM, Indunil Upeksha Rathnayake < > indu...@wso2.com> wrote: > >> Hi Maheshika, >> >> Can you please create a new git repository with

Re: [Architecture] [IAM] SCIM 2.0 Outbound Connector

2018-02-12 Thread Dimuthu Leelarathne
Hi Isuranga/Gayan and All, WSO2 IS should be able to provision with both SCIM 1.1 and SCIM 2.0 at the same time. There can be two systems - one supporting 1.1 and the other supporting 2.0, and we need to provision users to both of them. The above statement does *not* mean we need two separate

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

2018-02-12 Thread Sanjeewa Malalgoda
In that case please consider http status code 207[1] as simple resource update actually handle multiple resource updates (which usually refer as multi state update) [1]https://httpstatuses.com/207 Thanks, sanjeewa. On Tue, Feb 13, 2018 at 12:00 PM, Chiran Wijesekara wrote: >

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

2018-02-12 Thread Chiran Wijesekara
Hi Prasanna, Appreciate your suggestion. However, It was done in such a way with the RESTful design guidelines and usability in mind. Thanks On Tue, Feb 13, 2018 at 11:28 AM, Sanjeewa Malalgoda wrote: > It looks like claims are attributes of dialect. In that case when user >

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

2018-02-12 Thread Chiran Wijesekara
Hi Sanjeewa, Local claims are termed as attributes. That is *Attributes = Local claim Dialect* and further, the term attributes were used to lessen the confusion between those two. Thus, the dialect refers to the custom claim dialects other the Local Claim Dialect.When adding a dialect, providing

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

2018-02-12 Thread Prasanna Dangalla
Hi Chiran, To mitigate the inconsistencies between SOAP end REST APIs parameters, is there a possibility to use same parameter names in SOAP and REST API's?. As an example in 'DeleteLocalClaim' in SOAP claim ID is 'claimDialectURI' and in the given REST API solution its 'local-claim-id'. Thanks

[Architecture] Updated invitation: [IS] Architecture Review for SAML SSO HTTP... @ Tue Feb 13, 2018 1pm - 2pm (IST) (architecture@wso2.org)

2018-02-12 Thread indunil
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180213T073000Z DTEND:20180213T083000Z DTSTAMP:20180213T054040Z ORGANIZER;CN=indu...@wso2.com:mailto:indu...@wso2.com UID:7qnie84b1epvq6ogvi45hrp...@google.com

[Architecture] Updated invitation: [IS] Architecture Review for SAML SSO HTTP... @ Tue Feb 13, 2018 2pm - 3pm (IST) (architecture@wso2.org)

2018-02-12 Thread indunil
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180213T083000Z DTEND:20180213T093000Z DTSTAMP:20180213T054436Z ORGANIZER;CN=indu...@wso2.com:mailto:indu...@wso2.com UID:7qnie84b1epvq6ogvi45hrp...@google.com

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

2018-02-12 Thread Sanjeewa Malalgoda
It looks like claims are attributes of dialect. In that case when user create/update dialect he should be able to create it with all claims he need. I hope that claims go to externalClaims tag in json. Can you explain how it works? Is user allowed to create dialect with all claims at once? If few