nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to apply permission on search content

maiconramones

Hellow,

I'm searching how to restrict the results of search API basead on some permission.

My business requirements is:

Document A belongs to Entity X

Document B belongs to Entity Y

Document C belongs to Entity X

So I need to apply a restriction on search to show only documents of Entity X.

How I can implement this?

Find more posts tagged with

Alfresco Content Services

Comments

mbajpai

In the api AuthenticationUtil (Alfresco 5.0.3 Public API) , there is a method runAs . Try it .I guess it should work .

maiconramones

Thanks for the answer Mansha but stil not clear to me.

Because in my case I'm using Rest Api "/search" and running query with cmis language or alfresco full text search... In this case I don't have the UID of alfresco user to try runAs

afaust

The only way to restrict the visibility of the documents via search is by applying specific read permissions (for different user groups) on these documents and/or their parent folders. You also need to disable permissions inheritance on some ancestor node of your content structure so that the default "everyone can read" permissions is not propagated. "Manage Permissions" is the action you want to look for within Share.

maiconramones

Thanks Axel.

How does Alfresco work with this permissions on a query? Is it not necessary to apply "where" restrictions in a cmis query? Because I thought it was necessary to append the restrictions on a query to a group or something like that.

One more time Thanks.

afaust

Permissions are always handled in the background of queries and do not require any special fragments in the query. Only when you use AuthenticationUtils.runAsSystem() can you circumvent the permission checks.