Failure to Access as Community Administrator

[Agustín Alfieri]

Hi, 

I have a user that's an Administrator for  Community. When she tries to access her Dspace account the page keeps loading the "Recent Submissions" section and doesn't load the admin side bar. I tried deleting all the user's permissions and setting them back but the error persists.

Here's the dspace.log for the error.

2024-05-24 10:23:18,394 ERROR unknown unknown org.dspace.authorize.AuthorizeServiceImpl @ Failed getting getting community/collection admin status for user-account@gmail.com The search error is: Error from server at http://localhost:8983/solr/search: org.apache.solr.search.SyntaxError: Cannot parse 'read:(g71fb6810-8a88-43ad-86bd-b73df11f6540 OR ecb5e2e7e-603b-47fa-89c8-217a81b9b7d9 OR g71fb6810-8a88-43ad-86bd-b73df11f6540 OR g6a10a411-7bd4-41db-bb16-7fe5309e2c43) OR location:( m65c45c94-d7ed-407a-8788-b20e199cb87e OR lf19298b2-8d64-4dc7-bb39-0dc3003cccf7 OR ld065ee92-f56b-41f5-ac2d-f2a323bf88b5 OR l0cfd4ed6-ea4c-4c63-aa1d-f6ad59c9c30e OR lb12c1b0a-ead0-4834-9156-621482ed5384...

...... (a lot of other "OR bitstream")

 a21f5-5f33-4b84-b360-1d5462594b3a OR lf029f785-4a1b-4200-9bd3-28cd6842c036 OR lf4f36dc2-524b-4433-b188-4e6722995110 OR l12a672a4-eb94-44b7-9cc5-68894375b441 OR l501d8332-12b4-4386-955d-5b68ebf30faf OR l0b976fe4-9452-43cc-aabd-6c0e5276f9de)': too many boolean clauses The search resourceType filter was: search.resourcetype:Collection

Any help would be appreciated.

Agustín.

[Agustín Alfieri]

Update: I tried to solve the issue by adding a new user to the Community's Admin group, but the result was the same.

[Agustín Alfieri]

Well I've found a similar post from Alan Orth https://groups.google.com/u/1/g/dspace-tech/c/lYlxeZSVUzw/m/1q5EOlHAAgAJ and I've ended up using the solution proposed on the "I'm getting "SolrException: Bad Request" followed by a long query or a "tooManyClauses" Exception" section of https://wiki.lyrasis.org/display/DSArchive/TechnicalFAQ (Dspace 4).

First I tried to implement the maxBooleanClauses; solution but even after I set it to 8192 it didn't worked. So eventually what I did was Disable the Access Rights Awareness (https://wiki.lyrasis.org/display/DSDOC4x/Discovery#Discovery-AccessRightsAwareness) and this appears to solve the problem.

Nevertheless I would like to understand a little better what exactly was the problem and if this is the best solution, since I'm not quite sure about it. 

Again, any help would be appreciated.

Agustín.

[Agustín Alfieri]

Hi! 

I've rolled back the last change that I made "Disable the Access Rights Awareness" since it caused for some reason that the rest of the users lose their privileges on the rest of the communitys and collections. So I'm stuck in the same place as in the beginning, the "too many boolean clauses" error.

Just in case, I'm working with Dspace 7.6.1 on an Ubuntu 22.04 server with tomcat 9, Solr 8.11.2 and postgresql 13.

I really need some guidance, since I'm quite stuck with this issue.

[DSpace Technical Support]

Hi Agustin,

These issues sound very similar to ones that we've been fixing in the upcoming 7.6.2 release (likely to be out in July/Aug).  Namely these bug tickets:

* https://github.com/DSpace/DSpace/issues/9544

* https://github.com/DSpace/DSpace/issues/9201

* https://github.com/DSpace/DSpace/issues/9053

These fixes may be difficult to backport manually (as there's a lot of small changes involved).    The cause appears to be when an EPerson is a member of a large number of groups (either directly or inherited by nested groups within groups) and they are *not* an Administrator.  So, it's a situation that is more likely to occur for a Community or Collection Admin, but *not* for someone with full Administrator privileges.

I don't know of a great way to workaround the issue (other than temporarily making the user a full Admin or decreasing their group memberships), but fixes are coming.  We're just trying to finish getting 8.0 out the door and then we'll have a 7.6.2 release full of backported bug fixes.

Tim

[Agustín Alfieri]

Hi Tim,

Thanks for your answer! I worked around the issue giving the user Admin privileges on all the sub-communities of the community she should be admin of, which means she can do almost all of her tasks. But it's nice to know it's most likely a bug and not a issue of our repository.

I will keep an eye open for these fixes on 7.6.2

Agustin