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 <dimut...@wso2.com> wrote: > 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 8:45 AM, Dimuthu Leelarathne <dimut...@wso2.com> > wrote: > >> 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 outbound >> connectors. It could mean we use one connector but that single connector >> supports both of the protocols at the same time. >> >> thanks, >> Dimuthu >> >> >> On Mon, Feb 12, 2018 at 3:26 PM, Gayan Gunawardana <ga...@wso2.com> >> wrote: >> >>> >>> >>> On Mon, Feb 12, 2018 at 12:11 PM, Isuranga Perera < >>> isurangamper...@gmail.com> 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 >>>> >>>> On Mon, Feb 12, 2018 at 11:59 AM, Gayan Gunawardana <ga...@wso2.com> >>>> wrote: >>>> >>>>> Hi Isuranga, >>>>> >>>>> Could you be able to move *identity-outbound-**provisioning-scim2* to >>>>> *identity-outbound-provisioning-scim* by having configuration option >>>>> for SCIM 1.1 and 2.0 ? >>>>> >>>>> Thanks, >>>>> Gayan >>>>> >>>>> On Mon, Feb 5, 2018 at 10:48 AM, Isuranga Perera < >>>>> isurangamper...@gmail.com> wrote: >>>>> >>>>>> 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 >>>>>> instantiate the appropriate provisioning client. As an alternative, >>>>>> we can instantiate ScimClient [1] instead of ProvisioningClient since it >>>>>> provides almost all SCIM version specific functions related to object >>>>>> encoding and decoding. Anyway, if I'm not mistaken all of these changes >>>>>> are >>>>>> required only if we're going to use >>>>>> *identity-outbound-provisioning-scim* with SCIM client [2]. >>>>>> >>>>>> *@Malithi* >>>>>> Will work on the SCIM response error code issue asap. >>>>>> >>>>>> >>>>>> [1] https://github.com/IsurangaPerera/identity-client-scim2/ >>>>>> blob/ab5bdd6382ce4b055f99b65568c77289472c9c14/src/main/java/ >>>>>> org/wso2/scim2/util/SCIMClient.java >>>>>> [2] https://github.com/wso2-extensions/identity-client-scim2/pull/1 >>>>>> >>>>>> >>>>>> Best Regards >>>>>> Isuranga Perera >>>>>> >>>>>> On Sun, Feb 4, 2018 at 2:22 PM, Malithi Edirisinghe < >>>>>> malit...@wso2.com> wrote: >>>>>> >>>>>>> Hi Gayan, >>>>>>> >>>>>>> +1 for the thought. Basically, it's always the CRUD operations being >>>>>>> triggered for User and Group resources in the outbound provisioning flow >>>>>>> and based on the version the respective client can initiate calls upon >>>>>>> the >>>>>>> protocol. >>>>>>> So that's a matter of initializing the appropriate client based on >>>>>>> the version that will be configured with respect to the protocol version >>>>>>> used by the outbound party. That means version will be a connector >>>>>>> configuration and the connector will instantiate the appropriate client >>>>>>> upon the version with the application of factory pattern. >>>>>>> >>>>>>> *@Isuranga*, >>>>>>> Thanks a lot for the contribution. >>>>>>> Can we improve debug logs in the client to log respective requests >>>>>>> calls and responses for outbound party. >>>>>>> Also, looks like SCIM response errors are being swallowed in the >>>>>>> client without passing them back to the connector [1]. In that case, the >>>>>>> provisioning connector might not know if the request has been success or >>>>>>> not and act accordingly. >>>>>>> >>>>>>> [1] https://github.com/wso2-extensions/identity-client-scim2/pul >>>>>>> l/1/files#diff-5d09971e2f15b2c4858e2d49950f571cR75 >>>>>>> >>>>>>> Thanks, >>>>>>> Malithi. >>>>>>> >>>>>>> On Sat, Feb 3, 2018 at 6:01 PM, Gayan Gunawardana <ga...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> 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 >>>>>>>> for code duplication. Ideally protocol difference SCIM 1.1 and SCIM 2.0 >>>>>>>> should be very minimum to the provisioning connector level and protocol >>>>>>>> difference should be handled from *ProvisioningClient*. I do not >>>>>>>> think existing SCIM 1.1 provisioning connector do much about SCIM >>>>>>>> specific >>>>>>>> logic rather >>>>>>>> *org.wso2.carbon.identity.scim.common.impl.ProvisioningClient >>>>>>>> *handle all HTTP communication according to protocol. Is it >>>>>>>> possible to switch *ProvisioningClient* based on protocol (SCIM >>>>>>>> 1.1 and SCIM 2.0) ? @Darshana wdyt? >>>>>>>> >>>>>>>> I suppose in [2] swagger documentation doesn't have all error >>>>>>>> codes. For example user creation has only one error code (404) but >>>>>>>> there >>>>>>>> should be many more like 409. >>>>>>>> >>>>>>>> Also could you be able to consider about unit test coverage ? >>>>>>>> >>>>>>>> Thanks again for your valuable contribution. >>>>>>>> >>>>>>>> [1] https://github.com/wso2-extensions/identity-outbound-provisi >>>>>>>> oning-scim2/pull/1 >>>>>>>> [2] https://github.com/wso2-extensions/identity-client-scim2/pull/1 >>>>>>>> [3] https://github.com/wso2-extensions/identity-outbound-provisi >>>>>>>> oning-scim/ >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Gayan >>>>>>>> >>>>>>>> On Mon, Nov 27, 2017 at 1:12 PM, Isuranga Perera < >>>>>>>> isurangamper...@gmail.com> wrote: >>>>>>>> >>>>>>>>> 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 functions. >>>>>>>>> >>>>>>>>> *PRs for Charon* >>>>>>>>> IDENTITY-6962: Client-side validator for Charon 3 [3] fixed with >>>>>>>>> PR [4] >>>>>>>>> IDENTITY-6960: Missing Charon setter method of user password [5] >>>>>>>>> fixed with PR [6] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> [1] https://github.com/wso2-extensions/identity-client-scim2 >>>>>>>>> /pull/1 >>>>>>>>> [2] https://github.com/wso2-extensions/identity-outbound-pro >>>>>>>>> visioning-scim2/pull/1 >>>>>>>>> [3] https://wso2.org/jira/browse/IDENTITY-6962 >>>>>>>>> [4] https://github.com/wso2/charon/pull/80 >>>>>>>>> [5] https://github.com/wso2/charon/pull/79 >>>>>>>>> >>>>>>>>> Best Regards >>>>>>>>> Isuranga Perera >>>>>>>>> >>>>>>>>> On Thu, Nov 23, 2017 at 9:54 AM, Johann Nallathamby < >>>>>>>>> joh...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Thanks a lot Maheshika. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Johann. >>>>>>>>>> >>>>>>>>>> On Thu, Nov 23, 2017 at 8:56 AM, Maheshika Goonetilleke < >>>>>>>>>> mahesh...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Johann >>>>>>>>>>> >>>>>>>>>>> Created the two repos. >>>>>>>>>>> >>>>>>>>>>> On Tue, Nov 21, 2017 at 10:03 PM, Johann Nallathamby < >>>>>>>>>>> joh...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> 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 <az...@wso2.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Now you need approval for 2 repos of 3 repos? >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Nov 21, 2017 at 2:53 PM, Isura Karunaratne < >>>>>>>>>>>>> is...@wso2.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> 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 <az...@wso2.com >>>>>>>>>>>>>> > wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> What is the repo name? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Nov 7, 2017 at 1:06 PM, Maheshika Goonetilleke < >>>>>>>>>>>>>>> mahesh...@wso2.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Azeez >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please confirm. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Nov 7, 2017 at 11:23 AM, Johann Nallathamby < >>>>>>>>>>>>>>>> joh...@wso2.com> 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. *identity-scim2-common* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> For common utilities for inbound and outbound connectors. >>>>>>>>>>>>>>>>> E.g. AttributeMapper class in inbound connector which is >>>>>>>>>>>>>>>>> needed for >>>>>>>>>>>>>>>>> outbound connector as well. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 3. *identity-client-scim2* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> For SCIM2 client generated using SCIM2 swagger files. This >>>>>>>>>>>>>>>>> will be used by outbound connector as well as can be used by >>>>>>>>>>>>>>>>> anyone as >>>>>>>>>>>>>>>>> standalone client. Ideally this should be used for the scim2 >>>>>>>>>>>>>>>>> compliance >>>>>>>>>>>>>>>>> test suite as well, but have failed to do so. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>> Johann. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Oct 16, 2017 at 2:21 PM, Johann Nallathamby < >>>>>>>>>>>>>>>>> joh...@wso2.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Yes, I also think we need to take the approach of using >>>>>>>>>>>>>>>>>> the Swagger files and generate SDK because that is what >>>>>>>>>>>>>>>>>> standard Rest API >>>>>>>>>>>>>>>>>> world will be doing. We can find any issues early. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>> Johann. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Oct 16, 2017 at 2:18 PM, Gayan Gunawardana < >>>>>>>>>>>>>>>>>> ga...@wso2.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Oct 16, 2017 at 1:21 PM, Isuranga Perera < >>>>>>>>>>>>>>>>>>> isurangamper...@gmail.com> 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 < >>>>>>>>>>>>>>>>>>>> ga...@wso2.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Since you are looking for abstraction layer, can >>>>>>>>>>>>>>>>>>>>> implement something like [1] for SCIM2 as well. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> [1] https://github.com/wso2-extens >>>>>>>>>>>>>>>>>>>>> ions/identity-inbound-provisio >>>>>>>>>>>>>>>>>>>>> ning-scim/blob/master/componen >>>>>>>>>>>>>>>>>>>>> ts/org.wso2.carbon.identity.sc >>>>>>>>>>>>>>>>>>>>> im.common/src/main/java/org/ws >>>>>>>>>>>>>>>>>>>>> o2/carbon/identity/scim/common >>>>>>>>>>>>>>>>>>>>> /impl/ProvisioningClient.java >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Sun, Oct 15, 2017 at 11:16 PM, Gayan Gunawardana < >>>>>>>>>>>>>>>>>>>>> ga...@wso2.com> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Sun, Oct 15, 2017 at 8:39 PM, Johann Nallathamby < >>>>>>>>>>>>>>>>>>>>>> joh...@wso2.com> 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 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. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> There is no clear abstraction layer. Both SCIM2 >>>>>>>>>>>>>>>>>>>>>> compliance test developed by Vindula and SCIM 1.1 >>>>>>>>>>>>>>>>>>>>>> outbound provisioning >>>>>>>>>>>>>>>>>>>>>> connector are utilized apache commons http client . >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> In addition to that, I found this[2] repository >>>>>>>>>>>>>>>>>>>>>>>> which contains another SCIM client. can I know the >>>>>>>>>>>>>>>>>>>>>>>> completion level of this >>>>>>>>>>>>>>>>>>>>>>>> project? >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> This is feign http client and Vindula found it hard >>>>>>>>>>>>>>>>>>>>>> to use. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> In summary, there are 3 options which I can use to >>>>>>>>>>>>>>>>>>>>>>>> generate a SCIM 2.0 client. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Most feasible way is to go with apache commons >>>>>>>>>>>>>>>>>>>>>> HttpClient but better to give a try with swagger doc as >>>>>>>>>>>>>>>>>>>>>> well. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> 1. Separate SCIM 2.0 client from [1] >>>>>>>>>>>>>>>>>>>>>>>> 2. Separate SCIM 2.0 client from [2] >>>>>>>>>>>>>>>>>>>>>>>> 3. Use swagger doc [3] to generate client >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> [1] https://github.com/wso2-in >>>>>>>>>>>>>>>>>>>>>>>> cubator/scim2-compliance-test-suite >>>>>>>>>>>>>>>>>>>>>>>> [2] https://github.com/HansageeSJ/scim-client >>>>>>>>>>>>>>>>>>>>>>>> [3] https://wso2.org/jira/browse/IDENTITY-5695 >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Appreciate any suggestions. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Best Regards >>>>>>>>>>>>>>>>>>>>>>>> Isuranga Perera >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On Fri, Oct 13, 2017 at 9:42 AM, Gayan Gunawardana >>>>>>>>>>>>>>>>>>>>>>>> <ga...@wso2.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Thu, Oct 12, 2017 at 5:33 PM, Johann >>>>>>>>>>>>>>>>>>>>>>>>> Nallathamby <joh...@wso2.com> 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. >>>>>>>>>>>>>>>>>>>>>>>>>>> I'm looking at >>>>>>>>>>>>>>>>>>>>>>>>>>> identity-outbound-provisioning-scim [1] >>>>>>>>>>>>>>>>>>>>>>>>>>> and scim2-compliance-test-suite [2]. Appreciate >>>>>>>>>>>>>>>>>>>>>>>>>>> further suggestions. >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Hi Isuranga, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> It should be same as [1] you just have to think >>>>>>>>>>>>>>>>>>>>>>>>> SCIM provider is version 2 and send http requests >>>>>>>>>>>>>>>>>>>>>>>>> according to SCIM2 >>>>>>>>>>>>>>>>>>>>>>>>> format. As a starting point you can setup existing >>>>>>>>>>>>>>>>>>>>>>>>> SCIM provisioning >>>>>>>>>>>>>>>>>>>>>>>>> connector and debug from point [1] so you will >>>>>>>>>>>>>>>>>>>>>>>>> understand the flow. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> [1] https://github.com/wso2-extens >>>>>>>>>>>>>>>>>>>>>>>>> ions/identity-outbound-provisi >>>>>>>>>>>>>>>>>>>>>>>>> oning-scim/blob/master/compone >>>>>>>>>>>>>>>>>>>>>>>>> nts/org.wso2.carbon.identity.p >>>>>>>>>>>>>>>>>>>>>>>>> rovisioning.connector.scim/src >>>>>>>>>>>>>>>>>>>>>>>>> /main/java/org/wso2/carbon/ide >>>>>>>>>>>>>>>>>>>>>>>>> ntity/provisioning/connector/s >>>>>>>>>>>>>>>>>>>>>>>>> cim/SCIMProvisioningConnector.java#L99 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> [1] https://github.com/wso2-ex >>>>>>>>>>>>>>>>>>>>>>>>>>> tensions/identity-outbound-provisioning-scim >>>>>>>>>>>>>>>>>>>>>>>>>>> [2] https://github.com/wso2-in >>>>>>>>>>>>>>>>>>>>>>>>>>> cubator/scim2-compliance-test-suite >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Best Regards >>>>>>>>>>>>>>>>>>>>>>>>>>> Isuranga Perera >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>>>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/ >>>>>>>>>>>>>>>>>>>>>>>>>>> mailman/listinfo/architecture >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>>>>>>>>>>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>>>>>>>>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>>>>>>>>>>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>>>>>>>>>>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>>>> Gayan Gunawardana >>>>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer; WSO2 Inc.; >>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com/ >>>>>>>>>>>>>>>>>>>>>>>>> Email: ga...@wso2.com >>>>>>>>>>>>>>>>>>>>>>>>> Mobile: +94 (71) 8020933 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/ >>>>>>>>>>>>>>>>>>>>>>>>> mailman/listinfo/architecture >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>>>>>>>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>>>>>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>>>>>>>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>>>>>>>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>> Gayan Gunawardana >>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>>>>>>>>>>>>>>>>>>>>> Email: ga...@wso2.com >>>>>>>>>>>>>>>>>>>>>> Mobile: +94 (71) 8020933 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>> Gayan Gunawardana >>>>>>>>>>>>>>>>>>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>>>>>>>>>>>>>>>>>>>> Email: ga...@wso2.com >>>>>>>>>>>>>>>>>>>>> Mobile: +94 (71) 8020933 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Gayan Gunawardana >>>>>>>>>>>>>>>>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>>>>>>>>>>>>>>>>>> Email: ga...@wso2.com >>>>>>>>>>>>>>>>>>> Mobile: +94 (71) 8020933 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks & Best Regards, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Maheshika Goonetilleke >>>>>>>>>>>>>>>> Senior Engineering Process Coordinator >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *WSO2 Inc* >>>>>>>>>>>>>>>> *email : mahesh...@wso2.com <mahesh...@wso2.com>* >>>>>>>>>>>>>>>> *mobile : +94 773 596707 <077%20359%206707>* >>>>>>>>>>>>>>>> *www: :http://wso2.com <http://wso2.com/>*lean . >>>>>>>>>>>>>>>> enterprise . middleware >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> *Afkham Azeez* >>>>>>>>>>>>>>> Senior Director, Platform Architecture; WSO2, Inc.; >>>>>>>>>>>>>>> http://wso2.com >>>>>>>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>>>>>>> * <http://www.apache.org/>* >>>>>>>>>>>>>>> *email: **az...@wso2.com* <az...@wso2.com> >>>>>>>>>>>>>>> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: * >>>>>>>>>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org> >>>>>>>>>>>>>>> *twitter: **http://twitter.com/afkham_azeez* >>>>>>>>>>>>>>> <http://twitter.com/afkham_azeez> >>>>>>>>>>>>>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez >>>>>>>>>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> >>>>>>>>>>>>>> *Isura Dilhara Karunaratne* >>>>>>>>>>>>>> Associate Technical Lead | WSO2 >>>>>>>>>>>>>> Email: is...@wso2.com >>>>>>>>>>>>>> Mob : +94 772 254 810 <077%20225%204810> >>>>>>>>>>>>>> Blog : http://isurad.blogspot.com/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> *Afkham Azeez* >>>>>>>>>>>>> Senior Director, Platform Architecture; WSO2, Inc.; >>>>>>>>>>>>> http://wso2.com >>>>>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>>>>> * <http://www.apache.org/>* >>>>>>>>>>>>> *email: **az...@wso2.com* <az...@wso2.com> >>>>>>>>>>>>> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: * >>>>>>>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org> >>>>>>>>>>>>> *twitter: **http://twitter.com/afkham_azeez* >>>>>>>>>>>>> <http://twitter.com/afkham_azeez> >>>>>>>>>>>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez >>>>>>>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>* >>>>>>>>>>>>> >>>>>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>> >>>>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>> >>>>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> Thanks & Best Regards, >>>>>>>>>>> >>>>>>>>>>> Maheshika Goonetilleke >>>>>>>>>>> Senior Engineering Process Coordinator >>>>>>>>>>> >>>>>>>>>>> *WSO2 Inc* >>>>>>>>>>> *email : mahesh...@wso2.com <mahesh...@wso2.com>* >>>>>>>>>>> *mobile : +94 773 596707 <+94%2077%20359%206707>* >>>>>>>>>>> *www: :http://wso2.com <http://wso2.com/>*lean . enterprise . >>>>>>>>>>> middleware >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Architecture mailing list >>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Thanks & Regards, >>>>>>>>>> >>>>>>>>>> *Johann Dilantha Nallathamby* >>>>>>>>>> Senior Lead Solutions Engineer >>>>>>>>>> WSO2, Inc. >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> Mobile - *+94777776950* >>>>>>>>>> Blog - *http://nallaa.wordpress.com >>>>>>>>>> <http://nallaa.wordpress.com>* >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Architecture mailing list >>>>>>>>>> Architecture@wso2.org >>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Architecture mailing list >>>>>>>>> Architecture@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Gayan Gunawardana >>>>>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>>>>>>> Email: ga...@wso2.com >>>>>>>> Mobile: +94 (71) 8020933 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> Architecture@wso2.org >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Malithi Edirisinghe* >>>>>>> Associate Technical Lead >>>>>>> WSO2 Inc. >>>>>>> >>>>>>> Mobile : +94 (0) 718176807 >>>>>>> malit...@wso2.com >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Gayan Gunawardana >>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>>>> Email: ga...@wso2.com >>>>> Mobile: +94 (71) 8020933 >>>>> >>>> >>>> >>> >>> >>> -- >>> Gayan Gunawardana >>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/ >>> Email: ga...@wso2.com >>> Mobile: +94 (71) 8020933 >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Dimuthu Leelarathne >> Director, Solutions Architecture >> >> WSO2, Inc. (http://wso2.com) >> email: dimut...@wso2.com >> Mobile: +94773661935 <077%20366%201935> >> Blog: http://muthulee.blogspot.com >> >> Lean . Enterprise . Middleware >> > > > > -- > Dimuthu Leelarathne > Director, Rapid Response Team > > WSO2, Inc. (http://wso2.com) > email: dimut...@wso2.com > Mobile: +94773661935 <+94%2077%20366%201935> > Blog: http://muthulee.blogspot.com > > Lean . Enterprise . Middleware >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
