[ 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]
- Date: Fri, 1 Aug 2003 07:55:17 -0600 (MDT)
- From: Carol Gyger <gyger@xxxxxxxxxx>
- Subject: Re: Disabling Running of other modules
Bravismore,
We use three different configurations for our PCs for Millennium use.
1) All of our PCs at the Circulation Desks have Millennium logins
associated with their IP addresses. This is done in Limit Network Access.
When Millennium is launched from a PC with this setup, Millennium
automatically logs in to the system with the login specified in Limit
Network Access for that IP Address.
2) For a few staff members who have their own PCs on their desks and need
access to several modules, I do not enter a login for their IP address in
Limit Network Access. I leave the login field blank. When Millennium is
launched from one of these PCs, the user will have to type in a Millennium
Username and Password. I have this setup for Systems Administration staff
and Technical Services (cataloging).
3) This is a kind of hybrid setup. We have a few staff members who need
to login to different modules but they don't want to worry about
remembering several logins. This works for PCs that are shared by staff
members who have different needs. Like #2 above, there is no login
specified for these IP addresses in Limit Network Access. However, the
Millennium icon on the PC's desktop has a login associated with it. I can
have several Millennium icons on one desktop pointing to different logins.
For example, I have a PC that is used by one employee for Interlibrary
Loan and by another for Circulation. There is an icon for MilILL and
another for MilCirc. On my own desktop I have several Millennium icons
which login automatically and one that doesn't.
To create a Millennium icon which logs in automatically, make sure the
properties of the icon include the username and password.
"C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\java.exe" -classpath
.\;.\iiirunner.jar iiirunner username=<username> password=<password>
ip=<III server IP> port=2000 workdir=c:\Millennium
I know that method 3 is not very security minded but I only do this on a
few staff machines for a few logins. It's really for convenience more
than anything else. Security-wise, method 3 is no different than method
2.
I hope this information is helpful.
cg
Carol Gyger
Systems Administrator
Fort Collins Public Library
201 Peterson St.
Fort Collins CO 80524
(970)221-6716
gyger@xxxxxxxxxx
On Thu, 31 Jul 2003, Bravismore Mumanyi wrote:
> No. I haven't got any response yet.
>
> Regards
> /Bravismore
>
> Carol Gyger wrote:
>
> > Bravismore,
> >
> > Did you get an answer to this question?
> >
> > cg
> >
> > Carol Gyger
> > Systems Administrator
> > Fort Collins Public Library
> > 201 Peterson St.
> > Fort Collins CO 80524
> > (970)221-6716
> > gyger@xxxxxxxxxx
> >
> > On Tue, 29 Jul 2003, Bravismore Mumanyi wrote:
> >
> > > > Is there a way of disabling running of other modules on a PC where the
> > >
> > > Java-Runtime environment(Millennium enviroment) is installed?
> > >
> > > Example:
> > > We would like a situation where a user can only run Millennium Acquisitions and not Mill. Circulation or Serials.
> > >
> > > The problem is the user has logins for all modules but has to have access to some modules in a restricted area
> > > like
> > > Issue Desk and not in his office.
> > >
> > > Thanks in advance.
> > >
> > > Regards
> > > /Bravismore
> > >
> > >
> > > --
> > > 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
> > >
>
>