Reload greyed out in 9.2 browser GUI

["Oakley, Craig (NIH/NLM/NCBI) [C]" <cr...@nih.gov.INVALID>]

After upgrading from Solr8.11.1 to Solr9.2.1, the browser GUI (at hostname:port/solr/#/~collections/collection_name) has the "Reload" button greyed out and not functional ("Add Collection" and "Delete Collection" have also become greyed-out, but I am not as concerned about those). This is when logged in as a user which can execute solr/admin/collections?action=RELOAD&name=collection_name using curl; but it would be nice to allow the browser interface to work as well. I have not found any clues in the request logs, nor using SolrLogAuditLoggerPlugin, nor by increasing logging levels for security, or in the "Major Changes" web page. Any ideas?

RE: [EXTERNAL] Re: Reload greyed out in 9.2 browser GUI

["Oakley, Craig (NIH/NLM/NCBI) [C]" <cr...@nih.gov.INVALID>]

Thank you

Indeed that worked: and placing far enough down in security.json it did not inadvertently grant CREATE or DELETE permissions

Thanks again

-----Original Message-----
From: Shawn Heisey <ap...@elyograg.org.INVALID> 
Sent: Wednesday, November 15, 2023 12:48 PM
To: users@solr.apache.org
Subject: [EXTERNAL] Re: Reload greyed out in 9.2 browser GUI

On 11/15/23 08:10, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
> After upgrading from Solr8.11.1 to Solr9.2.1, the browser GUI (at hostname:port/solr/#/~collections/collection_name) has the "Reload" button greyed out and not functional ("Add Collection" and "Delete Collection" have also become greyed-out, but I am not as concerned about those). This is when logged in as a user which can execute solr/admin/collections?action=RELOAD&name=collection_name using curl; but it would be nice to allow the browser interface to work as well. I have not found any clues in the request logs, nor using SolrLogAuditLoggerPlugin, nor by increasing logging levels for security, or in the "Major Changes" web page. Any ideas?

After starting a 9.2.1 cloud example and examining the resulting web
page in the browser debug console, I can see that what will cause the
reload button to be disabled is a lack of collection edit permissions
for the logged-in user.

Because calling the reload with curl works, the overall permission
system is functioning as expected.

Explicitly grant the collection-admin-edit permission to the logged in
user or their group, and it should fix the UI.

The fix for SOLR-16621, which is included in 9.2.1, should have
eliminated this problem.  Are you absolutely sure you're running 9.2.1
and not 9.0.x or 9.1.x?

Thanks,
Shawn

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.

Re: Reload greyed out in 9.2 browser GUI

[Shawn Heisey <ap...@elyograg.org.INVALID>]

On 11/15/23 08:10, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
> After upgrading from Solr8.11.1 to Solr9.2.1, the browser GUI (at hostname:port/solr/#/~collections/collection_name) has the "Reload" button greyed out and not functional ("Add Collection" and "Delete Collection" have also become greyed-out, but I am not as concerned about those). This is when logged in as a user which can execute solr/admin/collections?action=RELOAD&name=collection_name using curl; but it would be nice to allow the browser interface to work as well. I have not found any clues in the request logs, nor using SolrLogAuditLoggerPlugin, nor by increasing logging levels for security, or in the "Major Changes" web page. Any ideas?

After starting a 9.2.1 cloud example and examining the resulting web 
page in the browser debug console, I can see that what will cause the 
reload button to be disabled is a lack of collection edit permissions 
for the logged-in user.

Because calling the reload with curl works, the overall permission 
system is functioning as expected.

Explicitly grant the collection-admin-edit permission to the logged in 
user or their group, and it should fix the UI.

The fix for SOLR-16621, which is included in 9.2.1, should have 
eliminated this problem.  Are you absolutely sure you're running 9.2.1 
and not 9.0.x or 9.1.x?

Thanks,
Shawn