Hi Agung,

Unfortunately, there is no single config setting or script you can run to do this other than what I describe.  However, I assume you also affectively want to temporarily prevent logged in users from doing anything whilst not forcing them to have to log back in again?  This could be quite tricky to implement but we can look into adding such a feature for a future release, as I would sometimes find this useful.

Regards

David Newman

On 23/01/2025 11:15, Agung Prasetyo W. wrote:

CAUTION: This e-mail originated outside the University of Southampton.

Hi David,

Thank you for answering my questions. But I want this condition not for long time, only just for short time only. After that, user or editor can log in again.

Thank you,

Regards,

Agung PW

On Thu, Jan 23, 2025, 17:36 David R Newman <drn@ecs.soton.ac.uk> wrote:

Hi Agung,

I normally do two things.   (If you use Shibboleth-based login this will not work):

1. Edit the phrase "cgi/login:page_layout" to remove the login form.  You can do this through the phrase editor but it is best if you do this by adding (if not present) and editing it in your archive's cfg/lang/en/phrases/zz_webcfg.xml.  The original phrase should be in EPRINTS_PATH/lib/lang/en/phrases/system.xml if you need it.  Once edited reload Apache to make sure the new phrase it used by checking what happens when you click the Login link in your web browser.

2. As well as stopping new users logging in you may want to remove existing logged in user.  You can do this by manually remove all the loginticket records from the database. (I have been meeting to write a bin script to allow you to do this).

DELETE FROM loginticket.

Bear in mind this will also log you out so you may want to add a "WHERE userid != 1;"  This assume your user record is the first user record, i.e. 1.

Technically third-party applications that use the REST and similar API users would be able to make requests that require authentication.  However, this is not normally an issue for most people.

If you use Shibboleth-based login you will also want to disable your archive's cfg/cfg.d/zz_shibboleth.pl (as described in [1]).  I typically do this by copying it to zz_shibboleth.pl.disable and then reloading Apache.

Regards

David Newman

On 23/01/2025 09:11, Agung Prasetyo W. wrote:

CAUTION: This e-mail originated outside the University of Southampton.

CAUTION: This e-mail originated outside the University of Southampton.

Hi,

Can I disable login access so that no one can log in, but the repository can still be accessed?

What file should I must edit?

Thank you,

Regards,

Agung PW.

*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/