files.com 1.2.256 → 1.2.257

package/_VERSION

@@ -1 +1 @@
-1.2.256
+1.2.257

package/docs/models/As2Partner.md

@@ -30,7 +30,7 @@
 * `as2_station_id` (int64): ID of the AS2 Station associated with this partner.
 * `name` (string): The partner's formal AS2 name.
 * `uri` (string): Public URI where we will send the AS2 messages (via HTTP/HTTPS).
-* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
@@ -99,7 +99,7 @@ await As2Partner.create({
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `http_auth_password` (string): Password to send to server for HTTP Authentication.
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
 * `as2_station_id` (int64): Required - ID of the AS2 Station associated with this partner.
@@ -133,7 +133,7 @@ await as2_partner.update({
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `http_auth_password` (string): Password to send to server for HTTP Authentication.
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+* `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
 * `name` (string): The partner's formal AS2 name.

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.256';
+var version = '1.2.257';
 var userAgent = "Files.com JavaScript SDK v".concat(version);
 var logLevel = _Logger.LogLevel.INFO;
 var debugRequest = false;

package/lib/models/As2Partner.js

@@ -60,7 +60,7 @@ var As2Partner = /*#__PURE__*/(0, _createClass2.default)(function As2Partner() {
   (0, _defineProperty2.default)(this, "setUri", function (value) {
     _this.attributes.uri = value;
   });
-  // string # Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+  // string # Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
   (0, _defineProperty2.default)(this, "getServerCertificate", function () {
     return _this.attributes.server_certificate;
   });
@@ -170,7 +170,7 @@ var As2Partner = /*#__PURE__*/(0, _createClass2.default)(function As2Partner() {
   //   http_auth_username - string - Username to send to server for HTTP Authentication.
   //   http_auth_password - string - Password to send to server for HTTP Authentication.
   //   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
   //   default_mime_type - string - Default mime type of the file attached to the encrypted message
   //   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
   //   name - string - The partner's formal AS2 name.
@@ -471,7 +471,7 @@ _As2Partner = As2Partner;
 //   http_auth_username - string - Username to send to server for HTTP Authentication.
 //   http_auth_password - string - Password to send to server for HTTP Authentication.
 //   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-//   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+//   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 //   default_mime_type - string - Default mime type of the file attached to the encrypted message
 //   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
 //   as2_station_id (required) - int64 - ID of the AS2 Station associated with this partner.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "files.com",
-  "version": "1.2.256",
+  "version": "1.2.257",
   "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.256'
+const version = '1.2.257'
 let userAgent = `Files.com JavaScript SDK v${version}`
 
 let logLevel = LogLevel.INFO

package/src/models/As2Partner.js

@@ -56,7 +56,7 @@ class As2Partner {
     this.attributes.uri = value
   }
 
-  // string # Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+  // string # Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
   getServerCertificate = () => this.attributes.server_certificate
 
   setServerCertificate = value => {
@@ -166,7 +166,7 @@ class As2Partner {
   //   http_auth_username - string - Username to send to server for HTTP Authentication.
   //   http_auth_password - string - Password to send to server for HTTP Authentication.
   //   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
   //   default_mime_type - string - Default mime type of the file attached to the encrypted message
   //   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
   //   name - string - The partner's formal AS2 name.
@@ -321,7 +321,7 @@ class As2Partner {
   //   http_auth_username - string - Username to send to server for HTTP Authentication.
   //   http_auth_password - string - Password to send to server for HTTP Authentication.
   //   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates.
-  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS?
+  //   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
   //   default_mime_type - string - Default mime type of the file attached to the encrypted message
   //   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
   //   as2_station_id (required) - int64 - ID of the AS2 Station associated with this partner.