Although I do it with an LDAP-server, this is not needed.
You can simply set up a second IB-Database, set up a remote NT-Service
or a small Java-class and access their values via INDY or even COM. I am
using LDAP, as we have it installed anyway running on an AppServer and
need it for several other tasks in the application, and so it was very
convenient.
I strongly propose the idea of having a separate
user-authentizication-server, so the users never get in touch with their
real logins, and therefore can't mess around in the database anyway.

> -----Original Message-----
> From: Martijn Hoedeman [mailto:m.hoedeman@...]
> Sent: Friday, August 03, 2001 3:22 PM
> To: IBObjects@yahoogroups.com
> Subject: Betr.: RE: [IBO] IB User-security with IBO
>
> Many thanks everybody for the responses :-)
>
> Although I really like nick's idea for setting up a LDAP server (would
> love to hear more about this*) I think it's a little out of my

client's

> league.
>
> For now I'm going with the stored-procedure solution (as soon as they

get

> rid of that nasty IB-Novell server and I can start using stored
> procedures*)
>
> Regards,
> Martijn Hoedeman
> OPG-Medico B.V.
>
>