We have considered Innovative's LDAP product but decided it would not
achieve what we had wanted and decided to wait for Single Sign On which
is still being developed.
My understanding of Innovative's LDAP is that it allows users who are on
the campus system to authenticate on that system and thus remove the need
to use the barcode and PIN in the Millennium patron records. Had we
implemented Innovative's LDAP product we would only have retained PINs for
patrons who are not on the campus system so they can continue to renew
their loans, place holds, etc.
I don't know whether it will be possible for the campus system to force
users to change their password every 30 days when they authenticate
from within the OPAC. As Martin Myhill suggests they may need to go to
the campus system to change their password.
Mieko
On Wed, 3 Aug 2005, Mandy Phillips wrote:
> Hi there,
>
> We are looking at implementing the III LDAP product shortly and are
> just chewing over a number of issues. Can anyone help?
>
> Is there a way from the Opac to force users to change passwords, our
> network people insist that LDAP passwords are changed every 30 days? If
> users can't change their own password, they'll be 'locked out' of their
> accounts.
>
> We have purchased the new Patron API product, which we can't have until
> Release 2005 is launched. Does anyone have any experience of this as a
> beta product, and how that fits with the LDAP product?
>
> Thanks,
>
> Mandy
-----
Mieko Yamaguchi [log in to unmask]
Technical Services Manager/System Coordinator +44 (0)1248 382970
Main Library, University of Wales Bangor, UK +44 (0)1248 382979 (Fax)
|