Users
A User represents a human or system/service user with the ability to connect to Files.com via any of the available connectivity methods (unless restricted to specific protocols).
Users are associated with API Keys, SSH (SFTP) Keys, Notifications, Permissions, and Group memberships.
Authentication
The authentication_method property on a User determines exactly how that user can login and authenticate to their Files.com account. Files.com offers a variety of authentication methods to ensure flexibility, security, migration, and compliance.
These authentication methods can be configured during user creation and can be modified at any time by site administrators. The meanings of the available values are as follows:
password- Allows authentication via a password. If API Keys or SSH (SFTP) Keys are also configured, those can be used instead of the password. If Two Factor Authentication (2FA) methods are also configured, a valid 2nd factor is required in addition to the password.email_signup- When set upon user creation, an email will be sent to the new user with a link for them to create their password. Once the user has created their password, their authentication type will change topassword.sso- Allows authentication via a linked Single Sign On provider. If API Keys or SSH (SFTP) Keys are also configured, those can be used instead of Single Sign On. If Two Factor Authentication (2FA) methods are also configured, a valid 2nd factor is required in addition to Single Sign On. When using this method, you must also provide a validsso_strategy_idto associate the User to the appropriate SSO provider.password_with_imported_hash- Works like thepasswordmethod but allows importing a hashed password in MD5, SHA-1, or SHA-256 format. Provide the imported hash in the fieldimported_password_hash. Upon first use, the password will be converted to Files.com's internal storage format and the authentication type will change topassword. Typically only used when migrating to Files.com from another MFT solution.none- Does not allow authentication via username and password, but does allow authentication via API Key or SSH (SFTP) Key. Typically only used for service users.password_and_ssh_key- Allows authentication only by providing a password and also a valid SSH (SFTP) Key in a single attempt. If API Keys are also configured, those can be used instead of the password and key combination. This method only works with (typically enterprise) SSH/SFTP clients capable of sending both authentication methods at once. Typically only used for service users.
List Users
XML Element
<filescom:list-users />
Authorization Requirement
Requires either a Site-Wide API key or User API key or session from a User with Folder Admin permissions.
Show User
XML Element
<filescom:show-user />
Authorization Requirement
Requires either a Site-Wide API key or User API key or session from a User with Folder Admin permissions.
| Parameter | Description |
|---|---|
| id Long Required | User ID. |
Create User
XML Element
<filescom:create-user />
Authorization Requirement
Available to all authenticated keys or sessions.
| Parameter | Description |
|---|---|
| username String Required | User's username |
| email String | User's email. |
| groupIds String | A list of group ids to associate this user with. Comma delimited. |
| password String | User password. |
| authenticationMethod String | How is this user authenticated? Possible values: password, email_signup |
| name String | User's full name |
| company String | User's company |
| notes String | Any internal notes on the user |
| requirePasswordChange boolean | Is a password change required upon next user login? |
| userRoot String | If filesystem layout is user_root, this path is the root path the user is fixed to for all interfaces. If the filesystem layout is site_root or partner_root, this acts as a root folder only for FTP and SFTP (SFTP applicability also requires a site-wide setting to be set). For partner_root layout, this path is relative to the Partner root folder for all callers and blank opts out of an additional protocol root. In this situation, this path is not applied to the API, Desktop, or Web interface. |
| userHome String | Home folder for FTP/SFTP. For users with the partner_root filesystem layout, this path is relative to the Partner root folder. In all other cases, it is an absolute path. Only applies to FTP and SFTP, and not any other interface. |
Update User
XML Element
<filescom:update-user />
Authorization Requirement
Not available to user API keys or sessions from users that are marked as Shared/Bot users.
| Parameter | Description |
|---|---|
| id Long Required | User ID. |
| email String | User's email. |
| groupIds String | A list of group ids to associate this user with. Comma delimited. |
| password String | User password. |
| authenticationMethod String | How is this user authenticated? Possible values: password, email_signup |
| name String | User's full name |
| company String | User's company |
| notes String | Any internal notes on the user |
| requirePasswordChange boolean | Is a password change required upon next user login? |
| userRoot String | If filesystem layout is user_root, this path is the root path the user is fixed to for all interfaces. If the filesystem layout is site_root or partner_root, this acts as a root folder only for FTP and SFTP (SFTP applicability also requires a site-wide setting to be set). For partner_root layout, this path is relative to the Partner root folder for all callers and blank opts out of an additional protocol root. In this situation, this path is not applied to the API, Desktop, or Web interface. |
| userHome String | Home folder for FTP/SFTP. For users with the partner_root filesystem layout, this path is relative to the Partner root folder. In all other cases, it is an absolute path. Only applies to FTP and SFTP, and not any other interface. |
| username String | User's username |
Delete User
XML Element
<filescom:delete-user />
Authorization Requirement
Requires either a Site-Wide API key or User API key or session from a User with Site Admin permissions.
| Parameter | Description |
|---|---|
| id Long Required | User ID. |