files.com 1.2.288 → 1.2.290

package/_VERSION

@@ -1 +1 @@
-1.2.288
+1.2.290

package/docs/models/Site.md

@@ -171,7 +171,6 @@
     "site_id": 1,
     "ssl_required": true,
     "timeout_at": "2000-01-01T01:00:00Z",
-    "tls_disabled": false,
     "two_factor_setup_needed": false,
     "allowed_2fa_method_sms": true,
     "allowed_2fa_method_totp": true,
@@ -211,7 +210,6 @@
   "ssl_required": true,
   "subdomain": "mysite",
   "switch_to_plan_date": "2000-01-01T01:00:00Z",
-  "tls_disabled": true,
   "trial_days_left": 1,
   "trial_until": "2000-01-01T01:00:00Z",
   "use_dedicated_ips_for_smtp": true,
@@ -457,7 +455,6 @@
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.
 * `subdomain` (string): Site subdomain
 * `switch_to_plan_date` (date-time): If switching plans, when does the new plan take effect?
-* `tls_disabled` (boolean): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
 * `trial_days_left` (int64): Number of days left in trial
 * `trial_until` (date-time): When does this Site trial expire?
 * `use_dedicated_ips_for_smtp` (boolean): If using custom SMTP, should we use dedicated IPs to deliver emails?
@@ -547,7 +544,6 @@ await Site.update({
   'migrate_remote_server_sync_to_sync': false,
   'session_expiry': 1.0,
   'ssl_required': false,
-  'tls_disabled': false,
   'sftp_insecure_ciphers': false,
   'sftp_insecure_diffie_hellman': false,
   'disable_files_certificate_generation': false,
@@ -709,7 +705,6 @@ await Site.update({
 * `migrate_remote_server_sync_to_sync` (boolean): If true, we will migrate all remote server syncs to the new Sync model.
 * `session_expiry` (double): Session expiry in hours
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.
-* `tls_disabled` (boolean): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
 * `sftp_insecure_ciphers` (boolean): If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
 * `sftp_insecure_diffie_hellman` (boolean): If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
 * `disable_files_certificate_generation` (boolean): If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.

package/docs/models/UserCipherUse.md

@@ -5,22 +5,24 @@
 ```
 {
   "id": 1,
+  "user_id": 1,
+  "username": "example",
   "protocol_cipher": "TLSv1.2; ECDHE-RSA-AES256-GCM-SHA384",
   "created_at": "2000-01-01T01:00:00Z",
   "insecure": true,
   "interface": "restapi",
-  "updated_at": "2000-01-01T01:00:00Z",
-  "user_id": 1
+  "updated_at": "2000-01-01T01:00:00Z"
 }
 ```
 
 * `id` (int64): UserCipherUse ID
+* `user_id` (int64): ID of the user who performed this access
+* `username` (string): Username of the user who performed this access
 * `protocol_cipher` (string): The protocol and cipher employed
 * `created_at` (date-time): The earliest recorded use of this combination of interface and protocol and cipher (for this user)
 * `insecure` (boolean): Is this cipher considered insecure?
 * `interface` (string): The interface accessed
 * `updated_at` (date-time): The most recent use of this combination of interface and protocol and cipher (for this user)
-* `user_id` (int64): ID of the user who performed this access
 
 ---
 

package/lib/Files.js

@@ -12,7 +12,7 @@ var apiKey;
 var baseUrl = 'https://app.files.com';
 var sessionId = null;
 var language = null;
-var version = '1.2.288';
+var version = '1.2.290';
 var userAgent = "Files.com JavaScript SDK v".concat(version);
 var logLevel = _Logger.LogLevel.INFO;
 var debugRequest = false;

package/lib/models/Site.js

@@ -636,10 +636,6 @@ var Site = /*#__PURE__*/(0, _createClass2.default)(function Site() {
   (0, _defineProperty2.default)(this, "getSwitchToPlanDate", function () {
     return _this.attributes.switch_to_plan_date;
   });
-  // boolean # This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
-  (0, _defineProperty2.default)(this, "getTlsDisabled", function () {
-    return _this.attributes.tls_disabled;
-  });
   // int64 # Number of days left in trial
   (0, _defineProperty2.default)(this, "getTrialDaysLeft", function () {
     return _this.attributes.trial_days_left;
@@ -820,7 +816,6 @@ _Site = Site;
 //   migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
 //   session_expiry - double - Session expiry in hours
 //   ssl_required - boolean - Is SSL required?  Disabling this is insecure.
-//   tls_disabled - boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
 //   sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
 //   sftp_insecure_diffie_hellman - boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
 //   disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.

package/lib/models/UserCipherUse.js

@@ -36,6 +36,14 @@ var UserCipherUse = /*#__PURE__*/(0, _createClass2.default)(function UserCipherU
   (0, _defineProperty2.default)(this, "getId", function () {
     return _this.attributes.id;
   });
+  // int64 # ID of the user who performed this access
+  (0, _defineProperty2.default)(this, "getUserId", function () {
+    return _this.attributes.user_id;
+  });
+  // string # Username of the user who performed this access
+  (0, _defineProperty2.default)(this, "getUsername", function () {
+    return _this.attributes.username;
+  });
   // string # The protocol and cipher employed
   (0, _defineProperty2.default)(this, "getProtocolCipher", function () {
     return _this.attributes.protocol_cipher;
@@ -56,10 +64,6 @@ var UserCipherUse = /*#__PURE__*/(0, _createClass2.default)(function UserCipherU
   (0, _defineProperty2.default)(this, "getUpdatedAt", function () {
     return _this.attributes.updated_at;
   });
-  // int64 # ID of the user who performed this access
-  (0, _defineProperty2.default)(this, "getUserId", function () {
-    return _this.attributes.user_id;
-  });
   Object.entries(attributes).forEach(function (_ref) {
     var _ref2 = (0, _slicedToArray2.default)(_ref, 2),
       key = _ref2[0],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "files.com",
-  "version": "1.2.288",
+  "version": "1.2.290",
   "description": "Files.com SDK for JavaScript",
   "keywords": [
     "files.com",

package/src/Files.js

@@ -6,7 +6,7 @@ let apiKey
 let baseUrl = 'https://app.files.com'
 let sessionId = null
 let language = null
-const version = '1.2.288'
+const version = '1.2.290'
 let userAgent = `Files.com JavaScript SDK v${version}`
 
 let logLevel = LogLevel.INFO

package/src/models/Site.js

@@ -481,9 +481,6 @@ class Site {
   // date-time # If switching plans, when does the new plan take effect?
   getSwitchToPlanDate = () => this.attributes.switch_to_plan_date
 
-  // boolean # This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
-  getTlsDisabled = () => this.attributes.tls_disabled
-
   // int64 # Number of days left in trial
   getTrialDaysLeft = () => this.attributes.trial_days_left
 
@@ -603,7 +600,6 @@ class Site {
   //   migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
   //   session_expiry - double - Session expiry in hours
   //   ssl_required - boolean - Is SSL required?  Disabling this is insecure.
-  //   tls_disabled - boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP.  See our documentation for more information.  Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
   //   sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections.  Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
   //   sftp_insecure_diffie_hellman - boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list.  This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients.  Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
   //   disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.

package/src/models/UserCipherUse.js

@@ -31,6 +31,12 @@ class UserCipherUse {
   // int64 # UserCipherUse ID
   getId = () => this.attributes.id
 
+  // int64 # ID of the user who performed this access
+  getUserId = () => this.attributes.user_id
+
+  // string # Username of the user who performed this access
+  getUsername = () => this.attributes.username
+
   // string # The protocol and cipher employed
   getProtocolCipher = () => this.attributes.protocol_cipher
 
@@ -46,9 +52,6 @@ class UserCipherUse {
   // date-time # The most recent use of this combination of interface and protocol and cipher (for this user)
   getUpdatedAt = () => this.attributes.updated_at
 
-  // int64 # ID of the user who performed this access
-  getUserId = () => this.attributes.user_id
-
   // Parameters:
   //   user_id - int64 - User ID. If provided, will return uses for this user.
   //   cursor - string - Used for pagination.  When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`.  Send one of those cursor value here to resume an existing list from the next available record.  Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.