Submitter shows as N/A for workflow editor

[IgorBaptist4]

Originally posted by @IgorBaptist4 in https://github.com/DSpace/dspace-angular/issues/2928#issuecomment-2059922319

Hello, this question was brought by me to Kimberly, so I will explain more about the behavior. I'm not able to reproduce it in the sandbox environment, but I'm able to reproduce it locally with a fresh install (without change any configuration) (in versions 7.6, 7.6, and 8.0 from the dspace-8.0-testathon branch) which is something weird I only be able to reproduce it locally, looks like some configuration that was made in the sandbox change the behavior on this part of DSpace.

So, to do this test I created 3 accounts:

one account to submit the item, added only in the submitter group of the collection ([email protected])

one account to do the test, checking the item submitter in MyDSpace, added only in the workflow editor group ([email protected])

another account to do the test, checking the item submitter in MyDSpace, added in the workflow editor group and collection admin group ([email protected])

Using the account that is only workflow editor, I'm not able to see the submitter of the item in MyDSpace:

I'm only able to see the submitter of the item, if I click on "View" and check the metadata dc.description.provenance of the item:

When I'm using the account that is workflow editor + collection admin (or system admin), I'm able to see the submitter in MyDSpace:

I tried to search for some configuration that add more permissions to workflow editor that can cause this different behavior between the sandbox environment and the fresh install locally, but I don't found nothing.

Thanks!

[tdonohue]

Copying in relevant message From Slack:

Pourbaix Michaël 5 hours ago Ok, so yesterday i went deep down into the backend code to find where the problem is laying. It turned out that information about a submitter can only be retreived if the logged user validates one of the following condition:

• He is the submitter himself,
• He is an admnistrator of the Community where the item has been submitted,
• He is an administrator of the Collection where the item has been submitted,
• He is in the administrator group.

The code that handles those conditions can be found in the file 'dspace-server-webapp/src/main/java/org/dspace/app/rest/security/EPersonRestPermissionEvaluatorPlugin.java'.