Subject | Re: [Firebird-Architect] RDB$USERS Prospective Definition |
---|---|
Author | Pierre Y. |
Post date | 2005-10-15T17:41:47Z |
Jim,
groups id to discriminate users between appplications, in the login form
I fill a combobox with users_names belonging to the users group(s)
allowed to connect to the application.
won't have to use the GID field but will it be possible to extend the
"standard" users table to add useful fields ? (emails address, phone or
whatever can be needed by the application...)
Regards,
Pierre Y.
pierre@...
>Question: are uid, guid, and group actually used for anything? They'reSince the users table is centralized in the security database, I use
>defined in access control lists (acls) from the days when users were
>
>
groups id to discriminate users between appplications, in the login form
I fill a combobox with users_names belonging to the users group(s)
allowed to connect to the application.
>authenticated from /etc/passwd, but I don't see how they could be usefulIf the users table can be owned by the database itself (as in vulcan) i
>in the current settings. If they are useful, this would be a very good
>time to drop them. I'd much rather add them back if/when we know what
>they mean than carry them around as lost baggage that might interfere
>with future use.
>
won't have to use the GID field but will it be possible to extend the
"standard" users table to add useful fields ? (emails address, phone or
whatever can be needed by the application...)
Regards,
Pierre Y.
pierre@...