HI Ushani,
On Tue, Nov 14, 2017 at 10:22 AM, Ushani Balasooriya <[email protected]> wrote: > > Hi, > > @Farsath - Thanks Farsath for the clear explanation. I just had it > configured since I was validating a scenario for testing purpose. Shouldn't > we remove the SPML connector from the product and documents if it is > deprecated? If we are going to have it in the product, I think document > should provide adequate information. > > @Ishara - I will try SCIM outbound provisioning connector as well in my > latter part of testing. > At the moment SPML is not a high priority item for Identity server so we are not focusing on doing improvement SPML related implementation or Document. And also I'm agree with you since its in the doc we need to clarify it more, but we can do it in future. In practical scenario only users who are interested on SPML will try it, But I'm doubt if there are any. So better to invest time on SCIM since its high priority. Thanks. -Ishara > > Thanks, > Ushani > > On Mon, Nov 13, 2017 at 7:07 PM, Ishara Karunarathna <[email protected]> > wrote: > >> Hi Ushani, >> >> Shall we try with the SCIM outbound provisioning scenario? >> SPML is not widely used provisioning mechanism in the industry but >> testing SCIM is important. >> >> Thanks, >> Ishara >> >> >> On Mon, Nov 13, 2017 at 7:01 PM, Farasath Ahamed <[email protected]> >> wrote: >> >>> Hi Ushani, >>> >>> When you configure an outbound provisioning to *Resident Service >>> Provider, *any changes you do to local users will be provisioned to >>> configured outbound provisioning connectors. >>> >>> So, >>> >>> SCIM Call ---> Resident SP --> Provision using SPML. >>> >>> By configuring an outbound provisioning connector you are asking IS to >>> sync any changes(any CRUD operation) you do to a local user (in a user >>> store) with an external entity. You would observe the same behaviour even >>> if you add a user from the management console. >>> >>> Any CRUD to local user ---> Resident SP --> Trigger outbound >>> provisioning connectors. >>> >>> Any particular reason you are trying out SPML since it's a deprecated >>> connector? >>> >>> Thanks, >>> Farasath >>> >>> Farasath Ahamed >>> Software Engineer, WSO2 Inc.; http://wso2.com >>> Mobile: +94777603866 >>> Blog: blog.farazath.com >>> Twitter: @farazath619 <https://twitter.com/farazath619> >>> <http://wso2.com/signature> >>> >>> >>> >>> On Mon, Nov 13, 2017 at 6:31 PM, Ushani Balasooriya <[email protected]> >>> wrote: >>> >>>> Hi IAM Team, >>>> >>>> >>>> Can you please explain me how does SPML outbound connector works? >>>> >>>> In my scenario, I am adding a user via SCIM and trying to update the >>>> user via SCIM. I have enabled SPML connector and added it under resident >>>> service provider. >>>> >>>> When I add a user via SCIM, I get the below warning. Please explain why >>>> it triggers SPML connector when I add a user via SCIM. >>>> >>>> I cannot find enough information in this doc [1] >>>> >>>> [1] https://docs.wso2.com/display/IS530/Outbound+Provisioning+with+SPML >>>> >>>> [2017-11-13 18:26:39,204] WARN {org.wso2.carbon.identity.prov >>>> isioning.connector.spml.SPMLProvisioningConnector} - Unsupported >>>> provisioning opertaion. >>>> [2017-11-13 18:26:39,212] WARN {org.wso2.carbon.identity.prov >>>> isioning.connector.spml.SPMLProvisioningConnector} - Unsupported >>>> provisioning opertaion. >>>> [2017-11-13 18:26:39,218] WARN {org.wso2.carbon.identity.prov >>>> isioning.connector.spml.SPMLProvisioningConnector} - Unsupported >>>> provisioning opertaion. >>>> [2017-11-13 18:26:39,227] ERROR {org.wso2.carbon.identity.prov >>>> isioning.connector.spml.SPMLProvisioningConnector} - Error while SPML >>>> user updating >>>> >>>> >>>> >>>> Thanks, >>>> -- >>>> *Ushani Balasooriya* >>>> Associate Technical Lead - EE; >>>> WSO2 Inc; http://www.wso2.com/. >>>> Mobile; +94772636796 >>>> >>>> >>> >> >> >> -- >> Ishara Karunarathna >> Associate Technical Lead >> WSO2 Inc. - lean . enterprise . middleware | wso2.com >> >> email: [email protected], blog: isharaaruna.blogspot.com, mobile: >> +94717996791 <+94%2071%20799%206791> >> >> >> > > > -- > *Ushani Balasooriya* > Associate Technical Lead - EE; > WSO2 Inc; http://www.wso2.com/. > Mobile; +94772636796 > > -- Ishara Karunarathna Associate Technical Lead WSO2 Inc. - lean . enterprise . middleware | wso2.com email: [email protected], blog: isharaaruna.blogspot.com, mobile: +94717996791
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
