Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Access denied to read the team at ...

Avatar

Level 4

Where is the team information stored?

We have a servlet that creates projects and then builds out permission sets and workflows to manage tasks associated with the project. If the standard "Create" link is clicked on the project.html page, then the project is created but the details can only be viewed by the administrator user. Even the user who created the project can't view the details. Looking in the error.log, there is an exception thrown, Caused by: com.adobe.cq.projects.impl.team.TeamException: Access denied to read the team at /content/projects/20151110/testofpermissionsproblem.  When I use the useradmin page to view the permissions, the user that created the project has more rights over the project than even the administrator but only the administrator can view the project detail.

What would be the cause of this and what would be the fix? 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

What version of AEM + SP is this?

The possibilities here are that there are some custom permissions that have been applied to your environment which are causing this. Is you local sandbox a clean AEM install?  It would be worth starting a clean instance and seeing what the OOTB behaviour is.

Regards,

Opkar

View solution in original post

7 Replies

Avatar

Level 10

which user you logged in to create project?

Avatar

Level 4

I logged in as myself instead of the administrator. Even though I'm in the administrators group, I couldn't see the information. When when I logged in as the administrator, I could see the data. Figure that one.

Avatar

Employee

If this is for AEM 6.1, then there are some security changes from how it was implemented in 6.0. In 6.1, for users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managing the team, those users need to have read access on /home/users and /home/groups.

Avatar

Level 4

alvawb1 wrote...

If this is for AEM 6.1, then there are some security changes from how it was implemented in 6.0. In 6.1, for users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managing the team, those users need to have read access on /home/users and /home/groups.

 

The problem with that is that I am in the administrators group and they have full access to /home and all child folders and I can't even see the details of the project I created under my user account. Changing permissions for the other groups made no difference at all.

Next possibility.

Avatar

Level 4

roberth55706517 wrote...

alvawb1 wrote...

If this is for AEM 6.1, then there are some security changes from how it was implemented in 6.0. In 6.1, for users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managing the team, those users need to have read access on /home/users and /home/groups.

 

The problem with that is that I am in the administrators group and they have full access to /home and all child folders and I can't even see the details of the project I created under my user account. Changing permissions for the other groups made no difference at all.

Next possibility.

 

Also I can view projects created on my local development sandbox and there aren't any permissions set for me to the /home/users or /home/groups folders.

Avatar

Correct answer by
Employee

Hi,

What version of AEM + SP is this?

The possibilities here are that there are some custom permissions that have been applied to your environment which are causing this. Is you local sandbox a clean AEM install?  It would be worth starting a clean instance and seeing what the OOTB behaviour is.

Regards,

Opkar

Avatar

Level 4

It is 6.1. I'm not sure what version of the service pack. Yes we have customized the permissions but the client's machine has the same customizations, that I know of, as my local copy. The version listed is 6.1.0.20150507.