Back
Home
Up
Next

New user management API calls.

    A typical complaint against IB4 was the lack of any documented API call to manage the creation of users. The only ways were the Server Manager in Windows and the command line gsec utility. Borland never published the trick.

In IB5, three API calls were defined:

  • isc_add_user()
  • isc_delete_user()
  • isc_modify_user()

These calls avoid workarounds like spanning a command line session to call gsec or to hard code the path to the security database and connecting directly to it. However, Borland made clear that those functions were intended as transitory solutions for a more comprehensive solution in IB6. No API call was offered to list all users registered in the security database.

Beware that you are given the power to shoot yourself if you want: isc_delete_user() allows SYSDBA to delete itself from the security database, so in this case you must recover isc4.gdb from some working copy (gdb), by simply overwriting it after stopping the server (you will lose new defined users). A backed up copy (gbk) won't work because you cannot use the gbak restore facility if you cannot login.

 

This page was last updated on 2001-02-04 01:04:51