APC Snap Server 2200 Specifications download pdf (Page 37)

Snap Server Administrator Guide 23Snap Server Administrator Guide 23

Chapter 3

User & Group Management

Authentication validates a user’s identity by requiring the user to provide a

registered login name and corresponding password. Snap Servers ship with

predefined local users and groups that allow administrative and guest user

access to the server via all protocols. Administrators may choose to join the

Snap Server to a Windows NT, Windows 2000, or Active Directory domain,

and Windows clients can then authenticate to the server using their domain

credentials. To accommodate NFS clients, the Snap Server can also join an

NIS domain, and the Snap Server can look up user and group IDs

maintained by the domain. For authentication control beyond the guest

account, Macintosh and FTP client login credentials can be duplicated

locally on the sever.

Topics in User and Group Configuration:

• Default User and Group Settings

•UID and GID Assignments

• Local Users and Groups

• Windows Workgroup or Domain

•NIS Domain

Default User and Group Settings

Snap Server default security configuration provides one share to the entire volume.

All network protocols for the share are enabled, and all users are granted read-write

permission to the share via the guest account.

UID and GID Assignments

The Snap Server uses the POSIX standard to assign user IDs (UID) and group IDs

(GID), in which each user and group must have a unique ID. This requirement

applies to all users and groups on the Snap Server, including local, NIS, and

Windows users and groups.

If you join the Snap Server to a Windows domain, unique IDs are automatically

assigned. If you join the Snap Server to an NIS domain, consider the following

1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 147 148

No comments

APC Snap Server 2200 Specifications Page 37