Hi Hanen, RC2 uses org.wso2.carbon.user.mgt.ui version 5.7.5, you'll have to add patch with this version or newer version, otherwise it picks the jar with highest version AFAIK.
On Fri, Jan 6, 2017 at 12:13 AM, Hanen Ben Rhouma <[email protected]> wrote: > 5.3.0-rc2 > > Regards, > Hanen > > On Thu, Jan 5, 2017 at 11:36 AM, Chamila Wijayarathna < > [email protected]> wrote: > >> No, UI jars are the same as others, what is the IS version you are using? >> >> On Thu, Jan 5, 2017 at 9:24 PM, Hanen Ben Rhouma <[email protected]> >> wrote: >> >>> Hi Chamila, >>> >>> I did create a directory patch0001 and put the jar under it, the logs >>> were showing it's taken into account but from the GUI side the changes >>> didn't take effect: >>> >>> [2017-01-05 11:13:29,776] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Checking for patch changes ... >>> [2017-01-05 11:13:29,803] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - New patch available - patch0001 >>> [2017-01-05 11:13:29,806] INFO >>> {org.wso2.carbon.server.extensions.PatchInstaller} >>> - Patch changes detected >>> [2017-01-05 11:13:35,757] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Backed up plugins to patch0000 >>> [2017-01-05 11:13:35,757] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Applying patches ... >>> [2017-01-05 11:13:35,758] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Applying - patch0001 >>> [2017-01-05 11:13:35,855] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Patched org.wso2.carbon.user.mgt.ui_5.7.0.jar(MD5:096b6efee440a71e96 >>> 4e1756b8dd25fc) >>> [2017-01-05 11:13:35,855] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Patch verification started >>> [2017-01-05 11:13:35,862] INFO {org.wso2.carbon.server.util.PatchUtils} >>> - Patch verification successfully completed >>> >>> >>> Is there something different about ui jars ? I changed a JSP, is there >>> another step to configure ? >>> >>> >>> Regards, >>> Hanen >>> >>> >>> On Wed, Jan 4, 2017 at 11:53 PM, Chamila Wijayarathna < >>> [email protected]> wrote: >>> >>>> Hi Hanen, >>>> >>>> Changing plugin is not a recommended thing, but applying patch should >>>> work here, refer[1] for guidelines to apply patches. >>>> If patch wasn't taken into account, please make sure the patch you add >>>> is as the same version as the already available jar in plugins folder. >>>> You can verify whether the patch has applied correctly by referring to >>>> repository/logs/patches log >>>> >>>> [1]. https://docs.wso2.com/display/IS510/Applying+Patches >>>> >>>> Regards! >>>> Chamila >>>> >>>> On Thu, Jan 5, 2017 at 4:20 AM, Hanen Ben Rhouma <[email protected]> >>>> wrote: >>>> >>>>> What if I want to change the jsp managing such logic which is within >>>>> org.wso2.carbon.user.mgt.ui_5.7.0 >>>>> The thing is that WSO2 is becoming unstable once I modify the plugin, >>>>> I even tried differently by putting the jar within patches but it wasn't >>>>> taken into account. >>>>> Any idea how can I replace the default plugin with a another one? >>>>> >>>>> >>>>> Regards, >>>>> Hanen >>>>> >>>>> On Wed, Jan 4, 2017 at 4:59 PM, Darshana Gunawardana < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Hanen, >>>>>> >>>>>> As of the current behaviour of the management console, it cannot hide >>>>>> primary user store from the drop down for tenant users. >>>>>> >>>>>> There are two ways to enforce this, >>>>>> * Add backend validation for restricting user creation in primary >>>>>> userstore for tenant users (this requires a listener implementation for >>>>>> user management operations) >>>>>> * Write a separate dashboard with these customizations (this requires >>>>>> to develop separate webapp) >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Wed, Jan 4, 2017 at 7:48 PM, Hanen Ben Rhouma <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Is there a way to restrict tenant users (having the permission to >>>>>>> create other users) to a secondary user store; I noticed PRIMARY user >>>>>>> store >>>>>>> is always there when trying to create a new user even for tenant users, >>>>>>> it >>>>>>> leads to some confusion and some users can persist other newly created >>>>>>> users on the PRIMARY, can't we grey out this drop down so that it works >>>>>>> for >>>>>>> only one secondary user store? >>>>>>> >>>>>>> Regards, >>>>>>> Hanen >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> >>>>>> >>>>>> *Darshana Gunawardana*Associate Technical Lead >>>>>> WSO2 Inc.; http://wso2.com >>>>>> >>>>>> *E-mail: [email protected] <[email protected]>* >>>>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise . >>>>>> Middleware >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Chamila Dilshan Wijayarathna, >>>> PhD Research Student >>>> The University of New South Wales (UNSW Canberra) >>>> Australian Centre for Cyber Security >>>> Australian Defence Force Academy >>>> PO Box 7916, Canberra BA ACT 2610 >>>> Australia >>>> Mobile:(+61)416895795 <+61%20416%20895%20795> >>>> >>>> >>> >> >> >> -- >> Chamila Dilshan Wijayarathna, >> PhD Research Student >> The University of New South Wales (UNSW Canberra) >> Australian Centre for Cyber Security >> Australian Defence Force Academy >> PO Box 7916, Canberra BA ACT 2610 >> Australia >> Mobile:(+61)416895795 <+61%20416%20895%20795> >> >> > -- Chamila Dilshan Wijayarathna, PhD Research Student The University of New South Wales (UNSW Canberra) Australian Centre for Cyber Security Australian Defence Force Academy PO Box 7916, Canberra BA ACT 2610 Australia Mobile:(+61)416895795
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
