We're now upgraded to v5.7, and still seeing this issue. I see that it was resolved in v6.1 via this JIRA item: https://jira.duraspace.org/browse/DS-3446
But the code fix referenced here: https://github.com/DSpace/DSpace/pull/1611/files Isn't quite the same code in v5.7 It seems to be in dspace-api/src/main/java/org/dspace/content/Bitstream.java around line 533 (in the delete() function), where the AuthorizeManager.removeAllPolicies() call is in the incorrect place. Can someone confirm that the fix is simply to move the AuthorizeManager.removeAllPolicies() call to the end of that function, similar to the v6.1 fix? Alex On Tuesday, 6 December 2016 13:31:31 UTC-5, Alex Fletcher wrote: > > We're still experiencing this problem when a non-"full administrator" > collection admin tries to claim a task, it puts it into an "unknown state", > with an error similar to: > > > JavaException: org.dspace.authorize.AuthorizeException: Authorization > denied for action WRITE on ITEM:19020 by user 1982 > > When that task is in that same user's task pool, and they try to approve > it, they get the same error. > > There is a suggested workaround in DS-2910, but applying that fix did not > help. We really don't want to downgrade to 5.5, because we have a number of > items under embargo for various reasons and the security fixes in 5.6 are > required, but this has been a very frustrating experience lately. > > As noted before, we are using 5.6, and we have configurable workflow > implemented. > > What steps can we do in order to get these items approved without > requiring full administrator permissions for the collection admins in > question? > > Thanks, > > Alex > > > On Wednesday, 16 November 2016 09:39:23 UTC-5, Alex Fletcher wrote: >> >> We just upgraded to 5.6 and seem to have come across a bug that was >> recently reported in JIRA: >> >> https://jira.duraspace.org/browse/DS-3367 >> >> By taking a task, the item ends up in an 'unknown state'. >> >> We have a couple of items in our repository in this weird state, and we >> need to: >> >> 1. get them out of this state >> 2. approve them into the repository >> >> Does anyone have any advice/solutions as to how to do this? >> >> >> Thanks, >> >> >> Alex >> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
