User Tools

Site Tools


gateway:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
gateway:start [2022/08/26 07:10] dmitrygateway:start [2022/10/30 18:00] (current) dmitry
Line 16: Line 16:
 =====End-to-end encryption===== =====End-to-end encryption=====
 All incoming messages that are stored in EasyMorph Gateway are asymmetrically encrypted using a public/private key pair. The keys are managed on EasyMorph Server. The private keys are stored on EasyMorph Server in an encrypted vault. Webhook messages arrive at EasyMorph Server encrypted and are decrypted only in the Server when processed in a task. All incoming messages that are stored in EasyMorph Gateway are asymmetrically encrypted using a public/private key pair. The keys are managed on EasyMorph Server. The private keys are stored on EasyMorph Server in an encrypted vault. Webhook messages arrive at EasyMorph Server encrypted and are decrypted only in the Server when processed in a task.
 +
 +\\
 +=====Authentication=====
 +===Webhook endpoint (URL) authentication===
 +For any HTTP request sent to the public webhook URL, the Gateway always returns "OK" (200). Custom webhook authentication protocols that require returning a particular token or signature in response are not supported.
 +
 +===Request authentication===
 +Requests can be protected by adding authentication using a secret passed via a request header or query parameter. In this case, any request that doesn't have the specified secret will be rejected with the response code 401 "Unauthorized".
 +
  
 \\ \\
Line 37: Line 46:
 ^ Description ^ Value ^ Notes ^ ^ Description ^ Value ^ Notes ^
 | Average task triggering latency  | ~3 seconds  | The time required to trigger a Server task after a webhook message is received. | | Average task triggering latency  | ~3 seconds  | The time required to trigger a Server task after a webhook message is received. |
-| Max payload size  | 300KB  | The max size of the incoming HTTP request body ((For large data objects use webhooks as a notification mechanism and retrieve large objects using an API request.)). |+| Max payload size  | 300KB  | The max size of the incoming HTTP request body ((For large data objects use webhooks as a notification mechanism and retrieve large objects using an API request. See also [[transformations:webrequest|action "Web request"]])). |
 | Max throughput  | up to 100 requests/second | If higher throughput is necessary, please contact technical support. | | Max throughput  | up to 100 requests/second | If higher throughput is necessary, please contact technical support. |
 | Max message processing time | 24 hours | If a message was retrieved by Server for processing but wasn't processed in that time it will be returned to the queue.| | Max message processing time | 24 hours | If a message was retrieved by Server for processing but wasn't processed in that time it will be returned to the queue.|
 | Max messages in batch | 10 | The number of messages a Server task can retrieve and process in one run. | | Max messages in batch | 10 | The number of messages a Server task can retrieve and process in one run. |
  
- 
-===Webhook URL authentication=== 
-For any HTTP request sent to the public webhook URL, the Gateway always returns "OK" (200). Custom webhook authentication protocols that require returning a particular token or signature in response are not supported. 
  
 ===HEAD requests=== ===HEAD requests===
 For any request made with the HTTP HEAD method, the Gateway always returns "OK" (200) without storing the message in the queue. For any request made with the HTTP HEAD method, the Gateway always returns "OK" (200) without storing the message in the queue.
gateway/start.txt · Last modified: 2022/10/30 18:00 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki