There was a proposed way to permit non-sysdba access the USERS table in
isc4.gdb, and to establish a trigger on the USERS table that raises an
exception unless the request to change a user's password is from that same
user, or from sysdba. It's kind of untested, though.

In a future world where we have authentication plugins to access OS
directories, presumably there is a way for a user to change his or her
password through an OS interface.

Bill

----- Original Message -----
From: "Mark Shapiro" <Mark.Shapiro@...>
To: <IB-Architect@egroups.com>
Sent: Wednesday, May 03, 2000 1:46 PM
Subject: RE: [IB-Architect] Database names


> >> I am not convinced that the isc4.gdb model of a single list
> >> of users/passwords is a good idea. What if two projects
> >> are totally disjoint, with different user communities?
> >> What if a user wants different passwords in different
> >> applications?
> >
> >Right, we've seen this request periodically on the InterBase list. For
> >instance, I recently read a question from a fellow who wanted SYSDBA to
> have
> >different passwords to access different databases.
>
>
> For that matter, what if a user wants to change their password without
> getting the sysdba involved? At the moment, it appears this is not
> possible, though on the Interbase list, it was suggested there may be a
way
> to fudge this.
>
> --
> Mark Shapiro
> Software Engineer
> Segue Technologies, Inc.
> http://www.seguetech.com/
>
>
> --------------------------------------------------------------------------
------
>
>
>
> --------------------------------------------------------------------------
------
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>
>