User Name and Password Requirements
Go Up to Programming with the InterBase API
When an InterBase client application is compiled, linked, and run, the client must always send a valid user name and password combination to the InterBase server. The server checks the user name and password against the user name and password combinations stored in its security database (admin.ib by default). If a match is found, the client can attach to InterBase databases on the server. If a match is not found, the server denies the attachment request.
For a successful attachment to occur, the following steps must be taken:
- A user with
SYSDBAprivileges must add a client’s user name and password to the security database of the server. Use IBConsole to do this on Windows platforms. On UNIX, use thegsecutility. - The client must send a valid user name and password combination to the server. Password is case sensitive.
UNIX logins: Under some circumstances, you can connect to a database even if you do not have a user name in the InterBase security database. In order for this to happen, the following things must be true:
- Both the client and server are running under UNIX,
- Your current login exists on the server host,
- You are logging in from a trusted client; a trusted client is one that is listed in the
/etc/hosts.equivor/etc/gds_hosts.equivfile on the server or in the.rhostsfile in your home directory on the server, - You have not specified a user name and password in the connect string,
InterBase comes with the
SYSDBA user ID predefined. The default password is masterkey. This user ID is for use by the database administrator, and it has special privileges that are not available to any other user ID. Do not use this user ID for a client application.