Login-Only Repository - Revision history

Drn@ecs.soton.ac.uk: /* EPrints 3.4 and above */

2025-04-25T10:56:45Z

‎EPrints 3.4 and above

Drn@ecs.soton.ac.uk: Added eprints config instructions for 3.4.x

2025-04-25T10:56:22Z

Added eprints config instructions for 3.4.x

Drn@ecs.soton.ac.uk: /* HTTP-only Repository Archive */

2025-04-19T12:01:46Z

‎HTTP-only Repository Archive

Drn@ecs.soton.ac.uk: /* HTTP-only Repository Archive */

2025-04-19T12:00:13Z

‎HTTP-only Repository Archive

Drn@ecs.soton.ac.uk: Improved instructions

2025-04-19T11:59:12Z

Improved instructions

Drn@ecs.soton.ac.uk: Updated more config

2025-04-18T21:04:55Z

Updated more config

Drn@ecs.soton.ac.uk: Updayed instructions for Apache 2.4.x

2025-04-18T15:41:20Z

Updayed instructions for Apache 2.4.x

Pm705 at 12:36, 20 March 2010

2010-03-20T12:36:39Z

Pm705 at 16:27, 8 February 2010

2010-02-08T16:27:44Z

Tdb01r at 11:58, 12 August 2009

2009-08-12T11:58:34Z

@@ Line 16: / Line 16: @@
 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:
+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.
   $c->{login_required_for_static}->{enable} = 1;
   $c->{login_required_for_static}->{exceptions} = [ "/", "/favicon.ico", "/images/.*", "/style/images/.*" ];

@@ Line 1: / Line 1: @@
-'''* * * MODIFIED APRIL 2025 TO UPDATE INSTRUCTIONS FOR APACHE 2.4.x * * *'''
+'''* * * MODIFIED APRIL 2025 TO ADD INSTRUCTIONS ON USING EPRINTS CONFIGURATION UPDATE EXISTING INSTRUCTIONS FOR USER WITH APACHE 2.4.x * * *'''
-This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.
+This instructions tell you how to configure your repository so that even search and view pages and potentially even static pages require a valid username/password.
 The <code>/images</code> and <code>/style</code> directories are deliberately unsecured, so that you can explicitly always view the files in them (you need the CSS + images to render the login page!)
@@ Line 7: / Line 7: @@
 This even secures things like the OAI interface, and registration. So you'll probably want to disable web-based registration in favour of importing users or creating them with an admin account.
-== HTTP-only Repository Archive ==
+== EPrints 3.4 and above ==
 . In <code>[[archives/ARCHIVEID/cfg/lang/en/static/]]</code> rename <code>index.xpage</code> to <code>home.xpage</code>.
@@ Line 49: / Line 64: @@
 . Restart Apache.
-== HTTPS-only or HTTP and HTTPS Repository Archive ==
+=== HTTPS-only or HTTP and HTTPS Repository Archive ===
 ''TO BE WRITTEN''
-== Allowing a few things without a password... ==
+=== Allowing a few things without a password... ===
 If you need to make any other directories available without a password, say the javascript directory, copy the directory directive for the images directory and tweak it:

@@ Line 14: / Line 14: @@
   EPRINTS_PATH/bin/generate_static ARCHIVEID
-. Add the following to <code>[[archives/ARCHIVEID/cfg/]]apachevhost.conf</code>. (Be sure to substitute <code>EPRINTS_PATH</code>, <code>ARCHIVEID</code> and <code>HOSTNAME</code> as appropriate):
+. Add the following to <code>[[Apachevhost.conf|archives/ARCHIVEID/cfg/apachevhost.conf]]</code>. (Be sure to substitute <code>EPRINTS_PATH</code>, <code>ARCHIVEID</code> and <code>HOSTNAME</code> as appropriate):
    <Location "">

@@ Line 14: / Line 14: @@
   EPRINTS_PATH/bin/generate_static ARCHIVEID
-. Add the following to [[archives/ARCHIVEID/cfg/]]apachevhost.conf (be sure to substitute <code>EPRINTS_PATH</code>, <code>ARCHIVEID</code> and <code>HOSTNAME</code> as appropriate):
+. Add the following to <code>[[archives/ARCHIVEID/cfg/]]apachevhost.conf</code>. (Be sure to substitute <code>EPRINTS_PATH</code>, <code>ARCHIVEID</code> and <code>HOSTNAME</code> as appropriate):
    <Location "">

@@ Line 3: / Line 3: @@
 This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.
-The /images and /style directories are deliberately unsecured so that you can explicitly always view the files in them (you need the CSS + images to render the login page!)
+The <code>/images</code> and <code>/style</code> directories are deliberately unsecured, so that you can explicitly always view the files in them (you need the CSS + images to render the login page!)
 This even secures things like the OAI interface, and registration. So you'll probably want to disable web-based registration in favour of importing users or creating them with an admin account.
-. In [[archives/ARCHIVEID/cfg/lang/en/static/]] rename index.xpage to home.xpage
+== HTTP-only Repository Archive ==
-. Run bin/generate_static to generate the home.html file (and others).
+. In <code>[[archives/ARCHIVEID/cfg/lang/en/static/]]</code> rename <code>index.xpage</code> to <code>home.xpage</code>.
-. Add the following to [[archives/ARCHIVEID/cfg/]]apachevhost.conf (use your site URL in the last bit and replace ARCHIVEID):
+. Generate static pages to create the file <code>home.html</code> amongst others.
    <Location "">
@@ Line 19: / Line 22: @@
      PerlAuthzHandler EPrints::Apache::Auth::authz
      require valid-user
    </Location>
-   <Directory "/opt/eprints3/archives/ARCHIVEID/html/en/images">
+   <Directory "EPRINTS_PATH/archives/ARCHIVEID/html/en/images">
     require all granted
    </Directory>
-   <Directory "/opt/eprints3/archives/ARCHIVEID/html/en/style">
+   <Directory "EPRINTS_PATH/archives/ARCHIVEID/html/en/style">
      require all granted
    </Directory>
@@ Line 39: / Line 41: @@
    <LocationMatch "^/$">
-     Redirect / http://myarchive.ac.uk/cgi/users/login?target=/home.html
+     Redirect / http://HOSTNAME/cgi/users/login?target=/home.html
    </LocationMatch>
-. Restart Apache.
+. If you did not already have an [[archives/ARCHIVEID/cfg/]]apachevhost.conf then run the following to make sure it is included in your Apache configuration:
 == Allowing a few things without a password... ==
-If you need to make any other Directories available without a password, copy the directory directive for the images dir and tweak it.
+If you need to make any other directories available without a password, say the javascript directory, copy the directory directive for the images directory and tweak it:
+  <Directory "EPRINTS_PATH/archives/ARCHIVEID/html/en/javascript">
-If you need to make a single file public, for example the RSS feed, use the following:
+    require all granted
-  <Directory "/opt/eprints3/archives/ARCHIVEID/html/en/style">
+If you need to make a single file public, for example the RSS/Atom feeds for latest publications, use the following:
    <Files "latest_tool">
      require all granted
    </Files>
 [[Category:Authentication]]

← Older revision		Revision as of 12:36, 20 March 2010
Line 1:		Line 1:
−	~~[[Category:Configuration]]~~
−	~~[[Category:Howto]]~~
	This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.		This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.

← Older revision		Revision as of 16:27, 8 February 2010
Line 1:		Line 1:
		+	[[Category:Configuration]]
		+	[[Category:Howto]]
	This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.		This instructions tell you how to configure your repository so that even the static pages and search and view pages require a valid username/password.

← Older revision		Revision as of 11:58, 12 August 2009
Line 63:		Line 63:
	</Files>		</Files>
	</Directory>		</Directory>
		+
		+	[[Category:Authentication]]