Hi Thilini,
I got the idea. Thank you. Regards, Yasima. On Mon, Aug 1, 2016 at 11:26 AM, Thilini Cooray <[email protected]> wrote: > Hi, > > On Mon, Aug 1, 2016 at 11:19 AM, Yasima Dewmini <[email protected]> wrote: > >> Hi Thilini, >> >> Only thing I'm doing is changing the permission of the user roles to deny >> the write permission. >> When trying to change state following error comes. >> >> > > As I mentioned above, the lifecycle executor which gets fired in your > scenario tries to update a resource. Since the "user1" doesn't have the > write access to the resource "/_system/governance/processes/process1/ > 1.0.0. <http://1.0.0.0/>", you are unable to update. > > Please check on the executor why this resource needs to be updated on the > lifecycle change. > As per now, user1 needs to have write access. > > > >> [2016-08-01 11:17:01,378] ERROR {rxt.asset} - Failed to invoke action: >> Submit for the asset of id: "02cbe9d0-5482-4d68-b507-c76b4ede6310".The >> following exception was thrown: JavaException: >> org.wso2.carbon.registry.core.secure.AuthorizationFailedException: Resource >> update failed. User user1 is not authorized to update the resource >> /_system/governance/processes/process1/1.0.0. >> [2016-08-01 11:17:01,379] ERROR >> {JAGGERY.extensions.assets.default.apis.asset:jag} - >> org.wso2.carbon.registry.core.secure.AuthorizationFailedException: Resource >> update failed. User user1 is not authorized to update the resource >> /_system/governance/processes/process1/1.0.0. >> >> Regards, >> Yasima. >> > > > Thanks. > > > >> >> >> On Mon, Aug 1, 2016 at 11:06 AM, Thilini Cooray <[email protected]> >> wrote: >> >>> Hi, >>> >>> Unless the executor itself doesn't try to update any resources, the >>> process owner does not require write access. >>> Do you observe any server side errors mentioning user not authorized to >>> access the resource etc.? >>> >>> Thanks. >>> >>> On Mon, Aug 1, 2016 at 10:57 AM, Yasima Dewmini <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I'm creating a new life cycle for PC. I want to remove write permission >>>> of the process owner when the process is in In-Review state. So, I wrote an >>>> executor to be executed at Development state to remove that permission. >>>> When write permission is removed, the process owner is not allowed to >>>> change the states of life cycle. But the process owner has life cycle >>>> permission. >>>> >>>> Does any user need write permission to change life cycle states? Isn't >>>> life cycle permission enough to change states? >>>> >>>> Any clarification on this issue is appreciated. >>>> >>>> Regards, >>>> Yasima. >>>> >>>> -- >>>> http://wso2.com/signatureYasima Dewmini >>>> Software Engineer, WSO2, Inc. >>>> Email: [email protected] >>>> Mobile: +94713117081 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> >>> *Thilini Cooray* >>> Software Engineer >>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194> >>> E-mail : [email protected] >>> >>> WSO2 Inc. www.wso2.com >>> lean.enterprise.middleware >>> >> >> >> >> -- >> http://wso2.com/signatureYasima Dewmini >> Software Engineer, WSO2, Inc. >> Email: [email protected] >> Mobile: +94713117081 >> > > > > -- > Best Regards, > > *Thilini Cooray* > Software Engineer > Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194> > E-mail : [email protected] > > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > -- http://wso2.com/signatureYasima Dewmini Software Engineer, WSO2, Inc. Email: [email protected] Mobile: +94713117081
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
