From 156741ad11f1f5c7e4bb7705de0c65ae7ae8b179 Mon Sep 17 00:00:00 2001 From: Mike Taylor Date: Wed, 18 Jan 2006 10:28:39 +0000 Subject: [PATCH] New --- etc/example.target-auth | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 etc/example.target-auth diff --git a/etc/example.target-auth b/etc/example.target-auth new file mode 100644 index 0000000..a5dd456 --- /dev/null +++ b/etc/example.target-auth @@ -0,0 +1,17 @@ +# $Id: example.target-auth,v 1.1 2006-01-18 10:28:39 mike Exp $ +# +# Sample user-to-target mapping for YP2's target authorisation. Each +# non-blank line either begins with a hash (in which case it is a +# comment, and is ignored) or is a mapping entry. Each entry consists +# of two colon-separated fields: a username and a comma-separated list +# of the targets that user is allowed to access. Note that these are +# not Z39.50 database names (those can be specified in the main +# user-register) but the tokens specified as blah +# within a Virtual DB filter in the YP2 configuration file. +# +# This file is accessed by an Auth-Simple filter containing a +# element whose content is the filename. + +mike:zurg:9901/bdsbkm21,zurg:9902/blconm21 +adam:zurg:9902/blconm21,zurg:9903/lcbkm21 +rob:zurg:9901/bdsbkm21,zurg:9902/blconm21,zurg:9903/lcbkm21,zurg:9904/radmarc -- 1.7.10.4