Errr pardon me ...

just a FNG with interbase/firebird but how about doing a "clone table"

one that has a users long name plus password and have it linked to THE REAL
security table via triggers etc.

jusat a thought from an idiot <G>.

dave.

-----Original Message-----
From: Marc Leclerc <mlpgr@...>
To: ib-support@yahoogroups.com <ib-support@yahoogroups.com>
Date: Wednesday, 11 April 2001 01:21
Subject: Re: [ib-support] User name questions

>Hi,
>
>Thanks for your answer, as it turns out you brought another good point out

when mentionning change rights. I guess I have to get to isc4.dgb in order
to let the users change their passwords. I will have a lot to consider here.
the users were used to be able to change their username & passwords in prior
version using paradox. I delivered the app with dummy entry (USER1, USER2...
and blank password) and let them setup their own things.

>
>Is accessing the security database Evil or is something often used.
>
>TIA
>
>----- Original Message -----
> From: Doug Chamberlin
> To: ib-support@yahoogroups.com
> Cc: ib-support@yahoogroups.com
> Sent: Monday, April 09, 2001 9:21 PM
> Subject: Re: [ib-support] User name questions
>
>
> At 4/9/2001 09:07 PM (Monday), Marc Leclerc wrote:
> >My users want to use their full names for login, as anyone got a nice

way

> >to do this. It seems that IB does not like spaces in user names such as
> >"John Doe".
>
> This is quite feasible but will take a bit of work.
>
> I is quite possible to make the Interbase security database (ISC4.GBD)
> available as a normal Interbase database. You client program could read

the

> list of user accounts from this database and match against a user's name
> entered at a login dialog. The table which holds user accounts includes
> fields for long names as well as the short username and password. The
> client program could then initiate a login using the short name and the
> same password the user entered.
>
> A couple of points worth noting:
> 1) You have to maintain the long names as well as the short names.
> 2) You need to ensure the long names are not duplicated so you can

actually

> identify a specific record.
> 3) You need to be careful of rights to change the records in the security
> database since this is a prime target for breakin attempts.
>
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>
>
>[Non-text portions of this message have been removed]
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>