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

2018-03-07 Thread Gayan Gunawardana
Hi Isuranga, Thanks for sending PRs. Just to be clear, according to [1] Isuranga has instantiated provisioning connector instance based on SCIM version. Reasons to use two provisioning connector instances are 1. Before invoking provisioning client there is bit of data processing have to do in

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

2018-02-16 Thread Isuranga Perera
Hi Dimuthu, Yes, I'll be able to deliver it by the end of next week. Best Regards On Fri, Feb 16, 2018 at 1:42 PM, Dimuthu Leelarathne wrote: > Hi Isurunga, > > I had a chat with the team and understood that what you are proposing is a > connector configuration. If so +1. >

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

2018-02-16 Thread Dimuthu Leelarathne
Hi Isurunga, I had a chat with the team and understood that what you are proposing is a connector configuration. If so +1. We have an internal requirement for this connector by the end of February. Wondering whether you could deliver it by that timeline? thanks, Dimuthu On Tue, Feb 13, 2018 at

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] [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 >

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

2018-02-11 Thread Isuranga Perera
Hi Gayan, Currently working on the configuration option. Sure I'll move changes to *identity-outbound-provisioning-scim*. Best Regards Isuranga Perera On Mon, Feb 12, 2018 at 11:59 AM, Gayan Gunawardana wrote: > Hi Isuranga, > > Could you be able to move

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

2018-02-04 Thread Isuranga Perera
Hi, *@Gayan* yes, *identity-outbound-**provisioning-scim2* has the nearly same code as * identity-outbound-provisioning-scim. **identity-client-scim2 *simply encode and decode SCIM objects and validate some actions. As Malithi suggested we can use version as a connector configuration and

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

2018-02-03 Thread Gayan Gunawardana
Hi Isuranga, Thanks you very much for the contribution and definitely this will be a very valuable feature. I went through some of your PRs [1][2]. As I understood* identity-outbound-* *provisioning-scim2* has nearly same code as* identity-outbound-provisioning-scim.* There is a good possibility

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

2017-11-26 Thread Isuranga Perera
Hi, I've submitted PRs for identity-client-scim2 [1] and identity-outbound-provisioning-scim2 [2]. There were some missing functions in charon3 such as some decoding methods, setter methods etc. Therefore I used some workarounds and also I have submitted some PRs for some of those missing

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

2017-11-23 Thread Johann Nallathamby
Thanks a lot Maheshika. Regards, Johann. On Thu, Nov 23, 2017 at 8:56 AM, Maheshika Goonetilleke wrote: > Hi Johann > > Created the two repos. > > On Tue, Nov 21, 2017 at 10:03 PM, Johann Nallathamby > wrote: > >> We discussed and decided no need of the

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

2017-11-21 Thread Johann Nallathamby
We discussed and decided no need of the scim2-common repo. Two repos mentioned above are enough. On Tue, Nov 21, 2017 at 9:15 PM, Afkham Azeez wrote: > Now you need approval for 2 repos of 3 repos? > > On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne wrote: >

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

2017-11-21 Thread Afkham Azeez
Now you need approval for 2 repos of 3 repos? On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne wrote: > Repo name for outbound connector > >- * identity-outbound-provisioning-scim2* > > Repo name for the scim2 client. > >- > * identity-client-scim2 * > > > @isuraranga,

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

2017-11-21 Thread Afkham Azeez
On Tue, Nov 21, 2017 at 9:12 PM, Johann Nallathamby wrote: > > > On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne wrote: > >> Repo name for outbound connector >> >>- * identity-outbound-provisioning-scim2* >> >> Repo name for the scim2 client. >> >>-

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

2017-11-21 Thread Johann Nallathamby
On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne wrote: > Repo name for outbound connector > >- * identity-outbound-provisioning-scim2* > > Repo name for the scim2 client. > >- > * identity-client-scim2 * > > +1 for above two repos. *@Azeez*: please approve above two

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

2017-11-21 Thread Maheshika Goonetilleke
Hi Azeez Please confirm. On Tue, Nov 21, 2017 at 3:16 PM, Isuranga Perera wrote: > Hi Isura > > In SCIM1 Outbound connector, they have used some classes from SCIM1 > Inbound connector project. So scim2-commons repo will be used for such > classes (which are common

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

2017-11-21 Thread Maheshika Goonetilleke
Hi All, Sorry for the delayed reply. Just to keep you informed, following is the naming convention we follow in wso2-extiontions ; --- Please comply with this convention when suggesting a repo name. On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne wrote: > Repo name for

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

2017-11-21 Thread Isura Karunaratne
Repo name for outbound connector - * identity-outbound-provisioning-scim2* Repo name for the scim2 client. - * identity-client-scim2 * @isuraranga, Why do we need the scim2-commons repo? Can't we use Charon for that? Thanks Isura. On Mon, Nov 20, 2017 at 3:04 PM, Afkham Azeez

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

2017-11-20 Thread Afkham Azeez
What is the repo name? On Tue, Nov 7, 2017 at 1:06 PM, Maheshika Goonetilleke wrote: > Hi Azeez > > Please confirm. > > On Tue, Nov 7, 2017 at 11:23 AM, Johann Nallathamby > wrote: > >> Hi Maheshika, >> >> Can we have following 3 repos for this project

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

2017-11-07 Thread Godwin Shrimal
Hi Johan, On Tue, Nov 7, 2017 at 8:38 PM, Johann Nallathamby wrote: > Hi Godwin, > > On Tue, Nov 7, 2017 at 7:51 PM, Godwin Shrimal wrote: > >> Hi Johan, >> >> >> On Tue, Nov 7, 2017 at 7:33 PM, Johann Nallathamby >> wrote: >> >>> Hi Godwin,

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

2017-11-07 Thread Godwin Shrimal
Hi Johan, On Tue, Nov 7, 2017 at 11:23 AM, Johann Nallathamby wrote: > Hi Maheshika, > > Can we have following 3 repos for this project under wso2-extensions > organization? > > 1. *identity-outbound-provisioning-scim2* > > For the outbound connector > > 2.

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

2017-11-07 Thread Johann Nallathamby
Hi Godwin, On Tue, Nov 7, 2017 at 7:51 PM, Godwin Shrimal wrote: > Hi Johan, > > > On Tue, Nov 7, 2017 at 7:33 PM, Johann Nallathamby > wrote: > >> Hi Godwin, >> >> On Tue, Nov 7, 2017 at 7:11 PM, Godwin Shrimal wrote: >> >>> Hi Johann, >>>

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

2017-11-07 Thread Johann Nallathamby
Hi Godwin, On Tue, Nov 7, 2017 at 6:02 PM, Godwin Shrimal wrote: > Hi Johan, > > > On Tue, Nov 7, 2017 at 11:23 AM, Johann Nallathamby > wrote: > >> Hi Maheshika, >> >> Can we have following 3 repos for this project under wso2-extensions >> organization? >> >>

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

2017-11-07 Thread Godwin Shrimal
Hi Johan, On Tue, Nov 7, 2017 at 7:33 PM, Johann Nallathamby wrote: > Hi Godwin, > > On Tue, Nov 7, 2017 at 7:11 PM, Godwin Shrimal wrote: > >> Hi Johann, >> >> Yes, these are not connectors but don't we need to follow the same naming >> convention for these

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

2017-11-07 Thread Godwin Shrimal
Hi Johann, Yes, these are not connectors but don't we need to follow the same naming convention for these repos as well? Thanks Godwin On Tue, Nov 7, 2017 at 6:40 PM, Johann Nallathamby wrote: > Hi Godwin, > > On Tue, Nov 7, 2017 at 6:02 PM, Godwin Shrimal

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

2017-11-06 Thread Maheshika Goonetilleke
Hi Azeez Please confirm. On Tue, Nov 7, 2017 at 11:23 AM, Johann Nallathamby wrote: > Hi Maheshika, > > Can we have following 3 repos for this project under wso2-extensions > organization? > > 1. *identity-outbound-provisioning-scim2* > > For the outbound connector > > 2.

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

2017-11-06 Thread Johann Nallathamby
Hi Maheshika, Can we have following 3 repos for this project under wso2-extensions organization? 1. *identity-outbound-provisioning-scim2* For the outbound connector 2. *identity-scim2-common* For common utilities for inbound and outbound connectors. E.g. AttributeMapper class in inbound

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

2017-10-16 Thread Gayan Gunawardana
On Mon, Oct 16, 2017 at 1:21 PM, Isuranga Perera wrote: > Hi Gayan, > > In that case, I'll try to create an SDK from swagger and use it as the > client. > That would be great. > > Best Regards > > On Mon, Oct 16, 2017 at 9:12 AM, Gayan Gunawardana

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

2017-10-16 Thread Isuranga Perera
Hi Gayan, In that case, I'll try to create an SDK from swagger and use it as the client. Best Regards On Mon, Oct 16, 2017 at 9:12 AM, Gayan Gunawardana wrote: > Since you are looking for abstraction layer, can implement something like > [1] for SCIM2 as well. > > [1]

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

2017-10-15 Thread Gayan Gunawardana
Since you are looking for abstraction layer, can implement something like [1] for SCIM2 as well. [1]

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

2017-10-15 Thread Gayan Gunawardana
On Sun, Oct 15, 2017 at 8:39 PM, Johann Nallathamby wrote: > *[+ IsharaK, Omindu, Farasath]* > > On Sun, Oct 15, 2017 at 7:34 PM, Isuranga Perera < > isurangamper...@gmail.com> wrote: > >> Hi, >> >> I went through the scim2-compliance-test-suite [1] source code, but I >>

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

2017-10-15 Thread Johann Nallathamby
*[+ IsharaK, Omindu, Farasath]* On Sun, Oct 15, 2017 at 7:34 PM, Isuranga Perera wrote: > Hi, > > I went through the scim2-compliance-test-suite [1] source code, but I > couldn't find an abstraction layer which separates the SCIM 2 client from > the test and report

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

2017-10-15 Thread Isuranga Perera
Hi, I went through the scim2-compliance-test-suite [1] source code, but I couldn't find an abstraction layer which separates the SCIM 2 client from the test and report modules. Is there any way I can separate SCIM 2.0 client from [1] so that I can use it as the SCIM 2.0 client for the $subject.

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

2017-10-12 Thread Gayan Gunawardana
On Thu, Oct 12, 2017 at 5:33 PM, Johann Nallathamby wrote: > > > On Thu, Oct 12, 2017 at 1:28 PM, Isuranga Perera < > isurangamper...@gmail.com> wrote: > >> Hi IAM Team, >> > >> Currently, there is no $subject. Therefore I'm looking at implementing a >> SCIM2 Outbound Connector.

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

2017-10-12 Thread Johann Nallathamby
On Thu, Oct 12, 2017 at 1:28 PM, Isuranga Perera wrote: > Hi IAM Team, > > Currently, there is no $subject. Therefore I'm looking at implementing a > SCIM2 Outbound Connector. I'm looking at identity-outbound-provisioning-scim > [1] > and scim2-compliance-test-suite