mittwald icon

mittwald

Interact with mittwald mStudio API

Actions100

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 you need to manage access control for SSH users dynamically, for example, enabling or disabling user accounts, updating credentials, or changing user metadata without manual intervention.

Practical examples include:

  • Automatically deactivating SSH users after a certain period.
  • Rotating passwords or updating public keys for enhanced security.
  • Adding descriptive information to SSH user accounts for easier identification.

Properties

Name Meaning
Ssh User Id The unique identifier of the SSH user to be updated.
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 to set for the SSH user.
Public Keys JSON array containing one or more public SSH keys associated with the user.

Output

The node outputs JSON data representing the updated SSH user object as returned by the API. This typically includes all current properties of the SSH user after the update, such as ID, active status, description, expiration, password (likely omitted or masked), and public keys.

If the node supports binary data output, it would generally relate to key files or certificates, but based on the provided code and properties, this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authentication with the mittwald mStudio API.
  • The node uses the mittwald API base URL: https://api.mittwald.de.
  • The node depends on the @devlikeapro/n8n-openapi-node package for OpenAPI integration.
  • Proper configuration of the API credential within n8n is necessary for successful requests.

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 is correctly configured.
  • Malformed Public Keys JSON: The Public Keys property expects valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
  • Date Format Issues: The Expires At field should be in a valid date-time string format (e.g., ISO 8601). Incorrect formats may lead to API rejection.
  • Permission Denied: The API user must have sufficient permissions to update SSH users; otherwise, the request will fail.

Links and References

Discussion