We set this default behaviour to make the OOTB experience better for the user.
First you need to check if it's a problem with the code that make the performance bad. IMO here it's a problem with the code if I understood this correctly where it goes and unnecessarily check for the SP, because the SP has already been identified in the inbound side, so that information should be available for the outbound side as well. Probably through the context variable, or alternatively as a threadlocal, if not it's a problem in the code IMO. If we decide not to fix in the code then it has to enabled by default and in the production deployment guideline recommend to turn it off if we are not using outbound provisioning. On Tue, Jul 19, 2016 at 9:13 AM, Gayan Gunawardana <[email protected]> wrote: > Hi All, > > Currently if we do not define DefaultIdentityUserProvisioningListener in > <EventListeners> (identity.xml) default behavior is to enable listener. > This behavior is fine if you have outbound provisioning user story but if > you do not have outbound provisioning user story at all, having > DefaultIdentityUserProvisioningListener enable make additional overhead to > all user CRUD operations. > > Specially we retrieve Service provider information for each user operation > which is totally unnecessary if there is no outbound provisioning user > story. > > Shall we change default behavior to make it disable ? > > Thanks, > Gayan > > -- > Gayan Gunawardana > Software Engineer; WSO2 Inc.; http://wso2.com/ > Email: [email protected] > Mobile: +94 (71) 8020933 > -- Thanks & Regards, *Johann Dilantha Nallathamby* Technical Lead & Product Lead of WSO2 Identity Server Governance Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
