Password file format
The file provider uses a binary password database file, spwd.db. You can generate a binary password file from a master.passwd-formatted file by running the pwd_mkdb command.
The master.passwd file contains ten colon-separated fields, as shown in the following example:
admin:*:10:10::0:0:Web UI Administrator:/ifs/home/admin:/bin/zsh
The fields are defined below in the order in which they appear in the file.
UNIX systems often define the
passwd format as a subset of these fields, omitting the Class, Change, and Expiry fields. To convert a file from
passwd to
master.passwd format, add
:0:0: between the GID field and the Gecos field.
- Username
- The user name. This field is case-sensitive. OneFS does not limit the length; many applications truncate the name to 16 characters, however.
- Password
- The user’s encrypted password. If authentication is not required for the user, you can substitute an asterisk (*) for a password. The asterisk character is guaranteed to not match any password.
- UID
- The UNIX user identifier. This value must be a number in the range 0- 4294967294 that is not reserved or already assigned to a user. Compatibility issues occur if this value conflicts with an existing account's UID.
- GID
- The group identifier of the user’s primary group. All users are a member of at least one group, which is used for access checks and can also be used when creating files.
- Class
- This field is not supported by OneFS and should be left empty.
- Change
- OneFS does not support changing the passwords of users in the file provider. This field is ignored.
- Expiry
- OneFS does not support the expiration of user accounts in the file provider. This field is ignored.
- Gecos
- This field can store a variety of information but is usually used to store the user’s full name.
- Home
- The absolute path to the user’s home directory, beginning at /ifs.
- Shell
- The absolute path to the user’s shell. If this field is set to /sbin/nologin, the user is denied command-line access.