topic Re: Owner Permissions disabled after inheritance set to false in Alfresco Archive

Owner Permissions disabled after inheritance set to false

venkat — Mon, 26 Mar 2007 07:44:35 GMT

Hi all, I created a document in the user home space using a custom content type that is derived by extending cm:content. I also set the owner aspect to the custom content type during node creation. The user could checkout the document normally. However when the user sets the inheritance on the

Re: Owner Permissions disabled after inheritance set to false

andy — Mon, 26 Mar 2007 16:36:42 GMT

Hi

Use the the OwnableService to set the owner.

Andy

Re: Owner Permissions disabled after inheritance set to false

venkat — Mon, 26 Mar 2007 18:09:00 GMT

Hi Andy,

I used the ownerable service to set the owner, but that did not help. I had to explicit set the permissions on the owner. Do I need to do this or is there a better solution ? Also, in this case, when I change the owner, I need to again explicitly set the permissions.

/* DID NOT WORK */
ownableService.setOwner(nodeRef, username);

/* WORKED */
ownableService.setOwner(nodeRef, username);
permissionService.setPermission(nodeRef, permissionService.getOwnerAuthority(), permissionService.getAllPermission(), true);

Thanks,
Venkat

Re: Owner Permissions disabled after inheritance set to false

andy — Thu, 29 Mar 2007 14:57:48 GMT

Hi

Could you post any changes you have made to pemissionDefinitions.xml.
Do you still have the global permission for OWNER? If not you would have to set this per node.

The type based issue is more interesting …. If there are no changes to pemissionDefinitions.xml then it looks like a bug. Let us know and I will dig into this further.

Cheers

Andy

Re: Owner Permissions disabled after inheritance set to false

venkat — Thu, 29 Mar 2007 18:56:47 GMT

Hi Andy,

    I did make changes to permissions.xml, but only added to the xml and did not remove anything that is existing already. I created a new content type called cd:document that extends cm:content. As you said, I am explicitly setting the permissions for owner for extension types.
    I am just pasting the extra permissions groups that we added. The global permissions are untouched.

    <!– ================================================ –>
   <!– Permissions available to all content and folders –>
   <!– ================================================ –>

<permissionSet type="cm:cmobject" expose="selected">

<!– MODIFIED Permissions –>
      <permissionGroup name="CdpDelete" expose="true" allowFullControl="false">
          <includePermissionGroup type="sys:base" permissionGroup="Delete"/>
          <includePermissionGroup type="cm:cmobject" permissionGroup="CdpWrite"/>
      </permissionGroup>

      <permissionGroup name="CdpWrite" expose="true" allowFullControl="false">
          <includePermissionGroup type="sys:base" permissionGroup="Write"/>
          <includePermissionGroup type="cm:cmobject" permissionGroup="CdpRead"/>
      </permissionGroup>

      <permissionGroup name="CdpRead" expose="true" allowFullControl="false">
          <includePermissionGroup type="sys:base" permissionGroup="Read"/>
      </permissionGroup>

</permissionSet>

   <!– =============================== –>
   <!– Permissions specific to cd:document : EXTENSION TO cm:content –>
   <!– =============================== –>

   <permissionSet type="cd:document" expose="selected">

      <!– Delete –>
      <permissionGroup name="CdDelete" allowFullControl="false" expose="true">
         <includePermissionGroup permissionGroup="CdpDelete" type="cm:cmobject" />
      </permissionGroup>

      <!– Write –>
      <permissionGroup name="CdWrite" allowFullControl="false" expose="true">
         <includePermissionGroup permissionGroup="CdpWrite" type="cm:cmobject" />
      </permissionGroup>

      <!– Read –>
      <permissionGroup name="CdRead" allowFullControl="false" expose="true">
         <includePermissionGroup permissionGroup="CdpRead" type="cm:cmobject" />
      </permissionGroup>

    </permissionSet>