On 10/28/14 18:00, Martijn Tonies (Upscene Productions) wrote: >> It's only .exe, that's why I've never used to work with it. > Wine is your friend. ;)
I have and use it but I very often need to check fbclient too, therefore for firebird it's not an option for me. On the other hand I do not need to perform much work with databases therefore isql & flame robin are more than enough for me. >>>>> , this would then create users only specific for the given security >>>>> database (CREATE USER) instead of the server security database. >>>>> >>>>> This would be similar to the Embedded User Authentication for >>>>> InterBase. >>>>> >>>> Sorry, but looks like I completely misunderstand what do you suggest... >>> InterBase has two ways of authenticating to databases, just as Firebird >>> now >>> has: >>> 1) server wide user name >>> 2) per database user names: Embedded User Authentication (EUA) >>> >>> If you enabled EUA on a database, it's detectable once connected, so in >>> this >>> case, >>> Database Workbench enables you to create/modify users on a per database >>> level >>> AND it knows where to find the available user names when visually >>> granting >>> privileges. >>> >>> When EUA is enabled (for InterBase), or a similar feature exists for >>> other >>> database >>> systems, this "Database Navigator" will support a "Users" node: >>> http://www.upscene.com/documentation/dbw5/dbnav_navigator.htm >>> >>> An example of the Grant Manager, which includes a list of available >>> users: >>> http://www.upscene.com/documentation/dbw5/tools_grantmanager.htm >>> Hope this makes things more clear. >> >> Ok, now I've understood that you want to be able to manage users in a >> database not providing login/password info in order to initialize users >> list in it. Well, reasonable client application can easily do it right >> now due to presence of providers architecture. > No, that's not what it is -- Database Workbench will connect to the > database, > via the server, providing a username/password combination. > > But after that, it can provide the user with a list of available user names > for > the use in the Grant Manager. > > Firebird 3 always provides a SEC$USERS table, either from the server wide > user database OR from the secondary user database. > > But for user management, I would like to know if the users list comes from > the > server or from a secondary database, it would be more clear to the users > of Database Workbench to see the difference if there's NO "Users" node > for a database which users server side users, and there is a "Users" node > for databases that use a secondary user database. Well understood at least (I hope). This requires small fix in code processing isc_info_svc_user_dbpath (make it depend upon isc_spb_expected_db). This will help you know what security database is used by given database using services. Please add a ticket to the tracker - such small enhancement may be added in beta2. I understand that using mon$ tables could be better but afraid for FB3 time for such changes is gone. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel