Technical data

Managing User Accounts
7.9 Setting Up Special Accounts
• On systems running DECnet-Plus:
NET$PROXY.DAT contains proxy information stored using DECnet-Plus
full names.
NETPROXY.DAT contains proxy information stored using DECnet-Plus
node synonyms.
Note
Deleting either NETPROXY.DAT or NET$PROXY.DAT will result in
incorrect functioning of proxy access on systems running DECnet for
OpenVMS Phase IV. Also, many applications such as ALL-IN-1 rely on
NETPROXY.DAT.
The SYSUAF.DAT file, on your local system, must associate proxy accounts with
user accounts. You will probably want to create a ‘‘standard access’’ account in
the UAF for proxy accounts. For example, you could create an account named
REMOTE_MKT with limited privileges, which allows access to certain data files
on your local system.
Suppose you have a group of users on your local system who prepare marketing
reports and who rely on input from users on other systems. You would assign
the REMOTE_MKT account in SYSUAF.DAT the same group number and
default privileges you assign to the local marketing group. In this way, the
remote contributors could access any data files that are ‘‘owned’’ by users in your
marketing group and that are not protected from group access.
How to Perform This Task
Use the AUTHORIZE command CREATE/PROXY to create and initialize network
proxy authorization files:
UAF> CREATE/PROXY
7.9.5 Adding Proxy Accounts
Create a proxy account by adding entries to the network proxy authorization file;
these entries equate one or more users on a remote node to users on your home
node.
How to Perform This Task
The command syntax for adding a proxy account is as follows:
ADD/PROXY node::remote-user local-user/DEFAULT [,...]
You can allow remote users access to up to 16 total local accounts: 1 default proxy
account and 15 alternate proxy accounts. Use the /DEFAULT qualifier to specify
the default proxy account.
Examples
1. The following command adds a user proxy account:
UAF> ADD/PROXY HAL::WALTER REMOTE_MKT/DEFAULT,PROXY2,PROXY3
Assume that you have created three accounts named REMOTE_MKT,
PROXY2, and PROXY3 on your home node. The entry in this example
permits the user WALTER on remote node HAL to access data by way of the
REMOTE_MKT account on your home node. WALTER can access any data
from his node that REMOTE_MKT can access locally. To access data through
7–38 Managing User Accounts