At 11:17 AM 12/06/2007, MRF wrote:

>I must admit - it would be nice for us to be able to connect to a Firebird
>Server and ask "what database files do you know about that I have
>permission to use?" without a registration overhead - using the existing
>aliases.conf entries.

That information doesn't exist anywhere...given that user
authentication occurs at server level. Even if the server had some
utility routine whereby it could read through aliases.conf (which is
nothing but a text file), there's nothing about a database header
that the server could visit and read and say "UserX has (or has not)
permission to use this database".

If the user gets past server authentication then any connection
request will succeed. Once the connection exists, the user's access
to *that* database depends entirely on his/her SQL permissions.

Other authentication models exist, of course, and in Firebird 3
you'll be able to mix and match permissions at several levels
according to requirements. I have no idea at this point how (or if)
that would translate to satisfy the kind of inquiry you stated above.

./heLen