[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dear colleagues,

My apologies for the delay, but I have been on extended sick leave. A number
of people were interested in our settings for WAM proxy to prevent on campus
users from having to login.

I am including the WAM table settings for Infotrac from Gale, which would be
common to many sites.

1 > Token                  gale
2 > IP Address/Host Name   *.galegroup.com
3 > Port                   80
4 > Service Level          0
5 > Verify                 3
6 > Valid Patron Types
    1-20,22-29,99,106-108,113,120,203-204,209-210,215-216,218-219,222
7 > Valid Patron Home Libs
8 > Database Identifier
9 > Database Name          Infotrac

In explanation, the relevant fields are Service Level and Verify. We could
also use Home Library which is new, but have not had any need to do so yet.

Basically this needs to be taken in conjunction with the Limit Network
Access Function, which is under Logins. Choose your HTTP option, and you can
set service levels (and logins) associated with particular IP ranges,
individual IPs, and most importantly, the default All, which includes
everything not listed above it in the table. Here are two examples from our
system -

 8 > 134.115.                 Yes            webmurd        3
 9 > all                      Yes            webout         0

The columns represent:
*the IP range
*if that range can login
*if there is a predetermined login
*what the service level is for that range. 

In this example, line 8 is our campus IP range, set at service level 3. 
Line 9 is the default, so every IP that doesn't fall within the ranges
specified above will have a service level of 0. 

If you look at the WAM table example above for Gale, you will see that the
Service level is set to 0, so anyone with a service level of 0 or higher can
use this database (in our case everyone), but Verify is set to 3. 

This means that IP ranges with service levels of 3 or higher (in this
example on campus users) will not get asked to verify themselves - ie enter
their user name, barcode and PIN. They will get passed straight through to
the Gale database. But if they are from another IP range, they will be asked
to verify, and if they meet the ptype criteria, and are not blocked, they
will then be passed through.

This has worked well for us for a long time now. It hasn't changed at all
with the introduction of the rewrite method, it only has made the service
levels more significant.

Please note the Limit Network Access table is read from the top, so you need
to put the most specific IPs or ranges at the top, and work down to the most
general 'All' at the bottom.

Please contact me if you have any further queries.

Best regards
Carolyn Wilson
Library IT Coordinator
Murdoch University
Murdoch WA 6150
ph: 9360 6273
c.wilson@xxxxxxxxxx <mailto:c.wilson@xxxxxxxxxx> 

-----Original Message-----
From: Mitlin, Laurance R. [mailto:mitlinl@xxxxxxxxxx] 
Sent: Tuesday, 21 May 2002 3:58 AM
To: innopac@xxxxxxxxxx
Subject: RE: Proxy question


Please share your reply with the list.

-----Original Message-----
From: Gina_K_Bolger@xxxxxxxxxx [mailto:Gina_K_Bolger@xxxxxxxxxx]
Sent: Monday, May 20, 2002 2:18 PM
To: innopac@xxxxxxxxxx
Subject: RE: Proxy question



Carolyn,

I "listened in" on your conversation about the new proxy rewrite setup and
wondered if I could take you up on your offer to send examples of your
setup. I am trying to plan our setup so that we can switch to the rewrite
method this weekend.  I think that seeing how you have set your service and
verification levels will be helpful as I try to muddle my way through this.

Thank you so much!

Gina Bolger

Gina K. Bolger
Cornerstone University
Miller Library
1001 E. Beltline NE
Grand Rapids, MI 49525
gbolger@xxxxxxxxxx
(616) 949-5300 ext.1245



 

                    Carolyn Wilson

                    <c.wilson@xxxxxxxxxx       To:
"'innopac@xxxxxxxxxx'" <innopac@xxxxxxxxxx>        
                    u.au>                      cc:

                    Sent by:                   Subject:     RE: Proxy
question                                        
                    innopac-admin@innopa

                    cusers.org

 

 

                    05/06/2002 08:45 PM

                    Please respond to

                    innopac

 

 





John,

We have only just implemented the rewrite version, but were using the old
version for some time.

Without going into it in great detail, providing your different members have
different discrete IP ranges, I would think that the service levels and
verification levels, along with the Limit Network Access functions, should
give you what you need. The outside vendor might be a problem if the IP
numbers allocated are not discrete.

The URLS will need to be changed, but you can use global updates to do that.
You shouldn't need two URLS.

The links will use the proxy whether the user is on campus or not, but you
can set the verification level so they are not asked to verify themselves -
making it seem the same to the patron as going direct. I don't believe there
is a problem with server load, but if you have to pay for your network
traffic it could be an issue.

If you want some more detail I am happy to answer questions or send you
examples of our setup. The documentation isn't very clear on this. We
require off campus patrons to verify, and but not on campus patrons.

Regards
Carolyn Wilson
Library IT Coordinator
Murdoch University
Murdoch Western Australia 6150
ph: 9360 6273
c.wilson@xxxxxxxxxx <mailto:c.wilson@xxxxxxxxxx>


-----Original Message-----
From: John Hammer [mailto:jhammer@xxxxxxxxxx]
Sent: Tuesday, 7 May 2002 12:28 AM
To: innopac@xxxxxxxxxx
Subject: Proxy question


We are a member of a consortium considering using the WAM in its new
version.  One of our institutions are using the old version, one is
contracting with an outside vendor, one is using Squid, and one is not using
any form of proxy.  I have some questions for those in the group that have
some experience with a rewriting proxy.  The colleges all share the bib
record.

I have been told the urls in the bib records will need to be changed.

1) How will this affect the institution not using a proxy and the one
contracting with the outside vendor? Will the changed urls be a problem for
them? Will there have to be two versions of urls?

2) Will the links use the proxy whether the users are on campus or not? If
so, how will that affect the resources of the Innovative server?

As you can see I am not quite sure how this is going to work for us. Any
words of advice will be greatly appreciated.


*********************************************************
John C. Hammer
Automation Librarian                            210.733.2669 (v)
San Antonio College LRC                 210.733.2597 (f)
1001 Howard St.                                 jhammer@xxxxxxxxxx
San Antonio, TX 78212
*********************************************************

--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx Update your subscription
options:
http://innopacusers.org/list/listinfo/innopac
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx Update your subscription options:
http://innopacusers.org/list/listinfo/innopac



--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx Update your subscription options:
http://innopacusers.org/list/listinfo/innopac
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx Update your subscription options:
http://innopacusers.org/list/listinfo/innopac