Users

The server decides what access a client should have based on the username and password provided.  When run using the QuickStart method, Anonymous Users are given read and write access to a single directory.  When run using the install–servedat script on a unix system, System Users are given the same type of access they would have with FTP.

Anonymous Users

Any request that does not contain a username and password is considered Anonymous.  If there is no AuthFile and SysAuth is not on, then anonymous users are given access only to the server's Default Home.  Within that directory, anonymous users can read and write with the same privileges as the servedat process.  If there is an AuthFile or SysAuth is turned on, then anonymous users are treated the same as if they entered a username of "ANONYMOUS".

SysAuth is turned on by default if servedat is run as root or as a Windows service.  Anonymous users will then be disabled unless you create an AuthFile with an ANONYMOUS entry.  See the enclosed svpasswd AuthFile sample.

System Users

If servedat is run with sufficient privileges, it can authenticate clients based on the same logon usernames and passwords used by the host operating system.  Operations performed using system logons will inherite whatever privileges and limitations are assigned by the operating system.  See the SysAuth section for details.

AuthFile Users

You can customize access to the server through the use of a private authorization file.  This gives you a greater degree of control over who can access the server and exactly what they are allowed to do.  You can set what home directory will be used, whether the user can access files outside that directory, restrict the user to read-only access, and on unix systems you can set user and group ids to govern each user's access.  See the AuthFile section for details.