Jump to content
Wiki Home
EPrints Home
Bazaar
Files
Main menu
Main menu
move to sidebar
hide
Navigation
Front Page
EPrints 3 Manual
EPrints Training Course
EPrints Glossary
Installing EPrints
How-to Configure EPrints
EPrints 3.2+ API
EPrints 3 Reference
EPrints Plugins
Wiki
All categories
Recent changes
Main Page
Help
EPrints Documentation
Search
Search
Appearance
Log in
Request account
Personal tools
Log in
Request account
Pages for logged out editors
learn more
Contributions
Talk
Editing
Login-Only Repository
(section)
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== EPrints 3.4 and above == Set the following configurations settings in a configuration file under your archive's <code>cfg/cfg.d/</code> directory (e.g. <code>zz_login_required.pl</code>). $c->{login_required_for_cgi}->{enable} = 1; $c->{login_required_for_eprints}->{enable} = 1; $c->{login_required_for_views}->{enable} = 1; $c->{login_required_for_cgi}->{exceptions} = [ "users/login", "handle_404" ]; $c->{login_required_url} = "/cgi/users/login"; This configuration will block all access to publication abstract/summary pages and their documents, browse view pages and any CGI script pages, such as search, export, etc. It will still allow users to access a login page, so if they do have an account they can login. In the configuration above, it is assumed that users will be authenticated locally. If institutions single sign-on (e.g. [[Shibboleth]] is being used then <code>"users/login"</code> can be removed from the exceptions and <code>login_required_url</code> should be updated appropriately. The <code>"handle_404"</code> exception is not essential but it saves a user having to login to find a page does not actually exist, which may be preferable or may be a security concern if they can see a page does not exist without logging in. You may want to add additional CGI scripts to exceptions such as <code>"reset_password"</code> and <code>"confirm"</code> to support password resets or <code>"register"</code> to allow visitors to register for user accounts. The above configuration does not prevent access to static pages like the home, about, policies, etc. If these need authentication as well, then similar configuration as describe fore EPrints 3.3 and older described below will need to be added to the HTTPS and also possibly HTTP Apache virtualhost configuration. From '''EPrints 3.4.7+''' there will be additional configuration options for static pages. The following two lines of configuration will allow all but the homepage (and its resources, based on a vanilla installation) to be restricted behind a login: $c->{login_required_for_static}->{enable} = 1; $c->{login_required_for_static}->{exceptions} = [ "/", "/favicon.ico", "/images/.*", "/style/images/.*" ];
Summary:
Please note that all contributions to EPrints Documentation may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
EPrints Documentation:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)