Hi All, According to current implementation when adding a user via SCIM, first user is added to user store with basic claims and again invoke setUserClaimValues in carbon user manager to set SCIM specific claims. Above approach raised two issues
1. Single SCIM user add operation do two calls to carbon user manager 2. Since carbon user manager receive two calls, it triggers DefaultInboundUserProvisioningListener twice and finally two provisioning requests go to out side As the first approach, what we could do is build SCIM specific claims inside SCIMUserOperationListener doPreAddUser() method and add user to user store from single call. This approach works fine but always SCIMUserOperationListener should come after DefaultInboundUserProvisioningListener so solution depends on order of UserOperationEventListeners. There are further suggestions to resolve above issue like remove, add SCIM specific claims functionality from SCIMUserOperationListener and put it some where else. Please mention your concerns and suggestions. -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: [email protected] Mobile: +94 (71) 8020933
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
