@celigo/api-specs 0.2.107 → 0.2.108

package/dist/api.yml

@@ -5634,14 +5634,20 @@ components:
           x-celigo-ui-override: 'Required by the connection form: a password for ftp/ftps, or a password or SSH key (authKey) for sftp (see the if/then/else rule below). Encoded here to mirror the form so builders produce complete, connectable configurations.'
           x-celigo-ai-guidance:
             - For ftp/ftps set password; for sftp set password or authKey. The connection cannot authenticate without credentials.
+            - For key-only sftp, omit password rather than filling it with a stand-in value — the form's required marker on Password does not apply once authKey is set, and the Help Center notes that servers enforcing a strict authentication order (public key first, then password) are not compatible with supplying both.
           examples:
             - s3cr3t-ftp-passw0rd
         authKey:
           type: string
-          description: |
+          description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
-            Only used when type is "sftp". Provide the full PEM-encoded private key.
-            Can be used alone or alongside a password for two-factor auth.
+            Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
+            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            are not supported and must be converted to an unencrypted PEM key first.
+          x-celigo-ai-guidance:
+            - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
+            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean

package/dist/connection.yml

@@ -4745,14 +4745,20 @@ components:
           x-celigo-ui-override: 'Required by the connection form: a password for ftp/ftps, or a password or SSH key (authKey) for sftp (see the if/then/else rule below). Encoded here to mirror the form so builders produce complete, connectable configurations.'
           x-celigo-ai-guidance:
             - For ftp/ftps set password; for sftp set password or authKey. The connection cannot authenticate without credentials.
+            - For key-only sftp, omit password rather than filling it with a stand-in value — the form's required marker on Password does not apply once authKey is set, and the Help Center notes that servers enforcing a strict authentication order (public key first, then password) are not compatible with supplying both.
           examples:
             - s3cr3t-ftp-passw0rd
         authKey:
           type: string
-          description: |
+          description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
-            Only used when type is "sftp". Provide the full PEM-encoded private key.
-            Can be used alone or alongside a password for two-factor auth.
+            Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
+            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            are not supported and must be converted to an unencrypted PEM key first.
+          x-celigo-ai-guidance:
+            - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
+            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean

package/dist/enduser.yml

@@ -2846,14 +2846,20 @@ components:
           x-celigo-ui-override: 'Required by the connection form: a password for ftp/ftps, or a password or SSH key (authKey) for sftp (see the if/then/else rule below). Encoded here to mirror the form so builders produce complete, connectable configurations.'
           x-celigo-ai-guidance:
             - For ftp/ftps set password; for sftp set password or authKey. The connection cannot authenticate without credentials.
+            - For key-only sftp, omit password rather than filling it with a stand-in value — the form's required marker on Password does not apply once authKey is set, and the Help Center notes that servers enforcing a strict authentication order (public key first, then password) are not compatible with supplying both.
           examples:
             - s3cr3t-ftp-passw0rd
         authKey:
           type: string
-          description: |
+          description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
-            Only used when type is "sftp". Provide the full PEM-encoded private key.
-            Can be used alone or alongside a password for two-factor auth.
+            Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
+            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            are not supported and must be converted to an unencrypted PEM key first.
+          x-celigo-ai-guidance:
+            - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
+            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean

package/dist/mcp-server.yml

@@ -4671,14 +4671,20 @@ components:
           x-celigo-ui-override: 'Required by the connection form: a password for ftp/ftps, or a password or SSH key (authKey) for sftp (see the if/then/else rule below). Encoded here to mirror the form so builders produce complete, connectable configurations.'
           x-celigo-ai-guidance:
             - For ftp/ftps set password; for sftp set password or authKey. The connection cannot authenticate without credentials.
+            - For key-only sftp, omit password rather than filling it with a stand-in value — the form's required marker on Password does not apply once authKey is set, and the Help Center notes that servers enforcing a strict authentication order (public key first, then password) are not compatible with supplying both.
           examples:
             - s3cr3t-ftp-passw0rd
         authKey:
           type: string
-          description: |
+          description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
-            Only used when type is "sftp". Provide the full PEM-encoded private key.
-            Can be used alone or alongside a password for two-factor auth.
+            Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
+            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            are not supported and must be converted to an unencrypted PEM key first.
+          x-celigo-ai-guidance:
+            - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
+            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean

package/dist/tool.yml

@@ -8000,14 +8000,20 @@ components:
           x-celigo-ui-override: 'Required by the connection form: a password for ftp/ftps, or a password or SSH key (authKey) for sftp (see the if/then/else rule below). Encoded here to mirror the form so builders produce complete, connectable configurations.'
           x-celigo-ai-guidance:
             - For ftp/ftps set password; for sftp set password or authKey. The connection cannot authenticate without credentials.
+            - For key-only sftp, omit password rather than filling it with a stand-in value — the form's required marker on Password does not apply once authKey is set, and the Help Center notes that servers enforcing a strict authentication order (public key first, then password) are not compatible with supplying both.
           examples:
             - s3cr3t-ftp-passw0rd
         authKey:
           type: string
-          description: |
+          description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
-            Only used when type is "sftp". Provide the full PEM-encoded private key.
-            Can be used alone or alongside a password for two-factor auth.
+            Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
+            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            are not supported and must be converted to an unencrypted PEM key first.
+          x-celigo-ai-guidance:
+            - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
+            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.107",
+  "version": "0.2.108",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "c1ef5efe",
+		"iasCommit": "79679bbe",
 		"generatedAt": "2026-10-14"
 	},
 	"roots": {