topic Re: Customizing Alfresco Permissions in Alfresco Archive

Customizing Alfresco Permissions

pavankk — Wed, 13 Mar 2013 18:26:29 GMT

Alfresco is one of the best ECM tool which is built on top of stack of Java technologies. It amazingly uses the Spring to accommodate customizations through bunch of configuration files.Out of the Box Alfresco comes with 5 default roles defined for cm:content type. like consumer, editor,collaborator

Re: Customizing Alfresco Permissions

afaust — Wed, 13 Mar 2013 21:30:36 GMT

Hello,

I would suggest handing the ownership over to another user or even to the "empty" user (any non-null value for cmwner that doesn't match an existing user) instead of adding your custom interceptors in the core services for this use case. Simply implement an action or script that sets cmwner, and since the OWNER dynamic authority bases its evaluation on this property, the previous owner / creator will no longer have more permissions on a document than via the assigned privileges.

Regards
Axel

Re: Customizing Alfresco Permissions

pavankk — Thu, 14 Mar 2013 01:53:42 GMT

Hello,

Yes you are right we can use cmwner for handling the ownership , but the business use case for us is , even though the user is a owner or creator, at some point of time if they want to make this user just a read only , and still they want the creator of the document remain same, this use case will not be achieved just using cmwnable aspect

Thanks
Pavan

Re: Customizing Alfresco Permissions

afaust — Mon, 18 Mar 2013 08:34:24 GMT

Hello,

I don't see why not. They will remain the creator, but no longer be owner and no longer have the privileges that come with that.

Regards
Axel

Re: Customizing Alfresco Permissions

hagak — Fri, 27 Feb 2015 16:09:06 GMT

If packaging within an amp how do you override the PerssionService Bean?

Re: Customizing Alfresco Permissions

afaust — Fri, 27 Feb 2015 16:14:44 GMT

Hello,

an AMP should typically NOT override the permissionServiceImpl bean. It should only provide the DynamicAuthority and the permissionServiceImpl bean should be overriden only in either the final build Project (where all AMPs are merged into the WAR) or in shared/classes/alfresco/Extension.

An alternative to overriding the XML would be the use of a Spring BeanFactoryPostProcessor to simply add a reference to your DynamicAuthority to the list of authorities in the bean Definition after it is read from XML but before the bean is instantiated. But this is rather advanced use of Spring and non-Standard in Alfresco.

Regards
Axel