mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation updates an existing SSH SFTP user by modifying its properties such as activation status, description, expiration date, password, and public keys. It is useful in scenarios where administrators need to manage SSH access for users on an SFTP server, for example, enabling or disabling user accounts, changing passwords, or updating authorized public keys.

Practical examples include:

  • Disabling a user who no longer requires access.
  • Updating the expiration date of a user's credentials.
  • Changing the user's password or adding/removing SSH public keys for authentication.

Properties

Name Meaning
Ssh User Id The unique identifier of the SSH user to be updated (required).
Active Boolean flag indicating whether the SSH user account is active (true) or inactive (false).
Description A textual description or note about the SSH user.
Expires At Expiration date/time for the SSH user account, typically in ISO 8601 string format.
Password New password for the SSH user.
Public Keys JSON array of SSH public keys associated with the user, used for key-based authentication.

Output

The node outputs JSON data representing the updated SSH user object returned from the API after the update operation. This typically includes the current state of the user’s properties such as ID, active status, description, expiration, password status (usually not returned for security), and public keys.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the mittwald mStudio API.
  • The node uses the mittwald mStudio API endpoint https://api.mittwald.de to perform the update.
  • Proper configuration of the API credential within n8n is necessary for successful execution.

Troubleshooting

  • Invalid SSH User Id: If the provided SSH User Id does not exist, the API will likely return a "not found" error. Verify the ID before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
  • Malformed Public Keys JSON: The Public Keys property expects valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
  • Permission Denied: Insufficient permissions on the API side may prevent updates. Confirm that the API key has rights to modify SSH users.
  • Date Format Issues: The Expires At field should be in a valid date-time string format. Incorrect formats might cause validation errors.

Links and References

Discussion