Access Record Composition

The server access file contains one or more access records. Each access record comprises the following fields:

Client Machine Name	The official host name by which the client machine is identified on the TCP/IP network. For distributed processing on Windows, this name is found in the Host field under Control Panel > TCP/IP Properties > DNS Configuration. Under UNIX, use the hostname or uname -n command to determine the name
Client Username	The user's login name on the client system
Local Username	The local user name that AcuConnect will use when fulfilling requests for the client user
Password	Optional password protection. When used, the requester must supply a password that matches this field
umask	A three-digit file creation mask

A typical server access record might look like the following:

Client Machine Name	Client Username	Local Username	Password	umask
starling	bernie	bsmith	. . . . . . .	002

This record allows user "bernie" to connect from machine "starling". AcuConnect uses the local user name "bsmith" (Bernie's account on the file server) when executing requests for "bernie". In this case, ". . . . . ." represents Bernie's local Windows password, which is required if Windows security is used.

Four fields — Client Machine Name, Client Username, Local Username, and Password — each have a wild card value that is used to indicate a general behavior. These wild cards are:

Field name	Wild card	Meaning
Client Machine Name	*	Match all client machines
Client Username	(empty field)	Match all client users
Local Username	same as client	Use the Client Username
Password	*	Deny access to user

When the string "same as client" is specified in the Local Username field, certain conditions apply. If Client Username is not a valid name on the server, DEFAULT_USER is used. DEFAULT_USER is used also if the Local Username field is blank.

Again, if DEFAULT_USER is used to connect to AcuConnect on a security partition under Windows server, be sure that DEFAULT_USER has both READ (RX) permissions on the wrun32.exe file and the appropriate permissions to access any file.

Common Access Records Example

For illustrative purposes, here is a set of common access records:

Client Machine Name	Client Username	Local Username	Password	umask
support-pc		techie	<none>	002
warehouse-pc			<none>	002
president-pc	diamond	<same as client>	<none>	002
robin		<same as client>	<none>	002
starling	felice	<same as client>	<none>	002
starling	baxter		......	002
swallow	hartley	hartley	<none>	002
swallow		acct	<none>	002
raven			*	002

These entries are interpreted as follows:

The entry for "support-pc" allows any user of "support-pc" to use AcuConnect. AcuConnect will use the local user name "techie" when executing requests for "support-pc".
The entry for "warehouse-pc" allows any user of "warehouse-pc" to use AcuConnect. Because the Local Username field is empty, AcuConnect will use the value of DEFAULT_USER as the local user name when executing requests for "warehouse-pc".
The entry for "president-pc" allows user "diamond" to access AcuConnect. Because the Local Username field holds "same as client," AcuConnect will attempt to use "diamond" as the Local Username. If "diamond" is not a valid local user name, the value of DEFAULT_USER will be used.
The entry for "robin" allows all users of "robin" to access AcuConnect. If the requester has an account on the server by the same name, AcuConnect will use that name; otherwise, AcuConnect will use the value of DEFAULT_USER.
The first entry for "starling" allows user "felice" to access AcuConnect. AcuConnect will follow the same rules as the previous entry to assign a local user name.
The second entry for "starling" allows user "baxter" to access AcuConnect. AcuConnect will use the value of DEFAULT_USER when executing requests for "baxter." "baxter" will need to provide a password before a connection will be established.
The first entry for "swallow" allows user "hartley" to access AcuConnect. AcuConnect will use the local user name "hartley" when executing requests for "hartley."
The second entry for "swallow" allows all users of "swallow" to access AcuConnect. AcuConnect will use the local user name "acct" for all users of "swallow," except "hartley" (or other records for "swallow" that explicitly name a client user).
The entry for "raven" denies any user of "raven" access to AcuConnect.

The most permissive access record that can be created is:

Client Machine Name	Client Username	Local Username	Password	umask
*		<same as client>	<none>	002

This record allows any user of any client to use AcuConnect, as long as the user has an account on the server by the same name, or DEFAULT_USER is defined with a valid user name (DEFAULT_USER cannot be defined to be root). A client user running as root will be mapped to DEFAULT_USER.