Administrator Guide : Gateway Alias Configuration : gwsetlogin Utility
 
Share this page                  
gwsetlogin Utility
The gwsetlogin utility allows a single gwalias entry to be used by multiple users. As described previously, the gateway uses a gateway alias to obtain a DBMS database name, user ID, and password. The database name can reference a local or remote database. The user ID and password can be stored in the alias entry in clear text or can be encrypted and stored in the Name Server database.
The gwsetlogin utility was written to allow an administrator to create the entries needed to store the encrypted user IDs and passwords. The gwsetlogin utility assumes that the alias entry contains a user ID of an asterisk ('*') and a password of an asterisk '*'. Specifying '*' for the user ID and password portion of the alias tells the gateway to access the Name Server database in order to retrieve the user ID and password.
This utility must be run by a user with the NETADMIN permission.
The gwsetlogin command has the following format:
gwsetlogin [-user] {server_class dbalias feuser dbuser dbpasswd}
-user
Allows the current user, even if non-privileged, to create their own private DBMS authentication entries.
Note:  If the –user parameter is not used, it is assumed that the gwsetlogin command is being run by a user with the NETADMIN privilege.
server class
Creates a global login vnode for Enterprise Access to server class. Valid values are:
mssql
oracle
odbc
dbalias
Specifies the alias name that was previously set up.
feuser
Specifies the Ingres client username used to access the gateway.
dbuser
Specifies the database username used to connect to the host dbms.
dbpasswd
Specifies the database password used to connect to the host dbms.
Note:  See the information about configuring the previously defined parameters in this chapter for more information.