Was this helpful?
Username Parameter Variation Table
The following table describes how the gateway handles variations for the username parameter.
Variation
username Parameter
user1
Specifies the username in clear text. The gateway simply retrieves this value and uses it as the native DBMS username when it connects to the database.
*
Stores the username as a Name Server vnode entry. When this variation is specified, the password entry must be specified as an asterisk ("*").
Note:  To specify the asterisk on the command line with gwalias, it must be surrounded by double quotes:
gwalias oracle empty_alias host "*" "*"
On UNIX, it must be escaped with a backslash: \*
See gwsetlogin Utility in this chapter for additional information.
The Name Server vnode name is used to obtain a username/password pair that is used to access the DBMS. This entry has the following form:
ServerClass_dbalias_feuser
ServerClass–Specifies the specific server associated with this entry. The allowed values, which correspond to the first three characters of each respective server class, are:
mss
ora
odbc
dbalias–Specifies a value of the alias dbalias entry.
feuser–Specifies the userid passed to the gateway from the client application when it connected to the gateway.
The user1 variation allows a single alias entry to be authorized for use by many gateway client users. Each user can have a different DBMS userid (or the same one). You can use NETU, NETUTIL, GWSETLOGIN, or Visual DBA to create the vnode entry. You must create the entry as either a global vnode or as a private vnode under the feuser userid. See gwsetlogin Utility in this chapter for additional information.
This form of authorization is a secure mechanism. The gateway administrator is responsible for managing the global name server entries. The gateway administrator must have the NET_ADMIN Ingres Net privilege.
@v_node
Specifies a specific vnode entry that contains the username and password needed to connect to the DBMS by the gateway. When this form is used, the password value of the entry must be specified as an asterisk (*). The commercial AT (@) character is stripped and the remaining value is interpreted as a Name Server vnode.
The @v_node variation allows a single alias entry to be authorized for use by many gateway client users. Each user can have a different DBMS userid (or the same). Using NETU, NETUTIL, or Visual DBA can create the vnode entry. The entry must be created as either a global vnode or it must be created under the private vnode entry for the feuser.
If a global vnode is used, each user has the same username and password when accessing the target DBMS. If a private vnode is used, each user can have a different username and password when accessing the target DBMS.
This form of authorization is also very secure. The gateway administrator is responsible for managing the Name Server entries.
NULL
Specifies that the username used to connect to the database is NULL. Before connecting to the database, this value is translated into a NULL value. The value NULL is a reserved value and is not case-sensitive.
blank
Specifies a blank username. This may be used for operating system authentication or to require clients to specify a username.
Note:  To specify a blank username on the command line with gwalias, it must be surrounded by double quotes:
gwalias oracle empty_alias host "" ""
Last modified date: 08/22/2022