2021-09-16 / System Settings
Overview

The IP address of the client that can access to Questetra is filtered. Register IP addresses that to allow access the entire system, each Event type, each Event type of a specific workflow App, etc.

Configs
  • Enable IP Address Filtering
Global Configuraton (Display when IP Address Filtering is enabled)
  • Allowed Hosts/Networks
Message Start Event/Catching Message Intermediate Event/Receive Task Configuration
  • Path Prefix
      • All
      • Message Start Event (HTTP) – all apps
      • Message Start Event (HTTP)- a specific app
      • Message Start Event (HTTP)- a specific node
      • Message Start Event (Webhook)- all apps
      • Message Start Event(Webhook)- a specific app
      • Message Start Event (Webhook)- a specific node
      • Message Start Event (form)- all apps
      • Message Start Event (form) – a specific app
      • Message Start Event (form) – a specific node
      • Catching Message Intermediate EventHTTP) – all apps
      • Catching Message Intermediate Event (HTTP) – a specific app
      • Catching Message Intermediate Event (HTTP) – a specific node
      • Receive Task (Webhook) – all apps
      • Receive Task (Webhook) – a specific app
      • Receive Task (Webhook) – a specific node
      • Receive Task (form) – all apps
      • Receive Task (form) – a specific app
      • Receive Task (form) – a specific node
  • Allowed Hosts/Networks

Capture

Notes

  • By checking the Enable IP Address Filtering box the configuration fields are revealed
  • In Global Configuration, you can specify IP addresses for which connecting access to your entire workflow system is permitted
    • You can allow access from any IP address by entering ”0.0.0.0/0” in this field
    • Please use IPv4 as IPv6 is not supported
    • Specify a global IP address in Allowed Hosts/Networks
    • It is possible to specify multiple IP addresses
      • It is only necessary to separate each address with a space, and each one will automatically be given its own line when the configuration is saved
    • When specifying a range of addresses it is better to use a Subnet Mask
    • You can deny access from any IP address by leaving Allowed Hosts/Networks blank
  • In Message Start Event/Catching Message Intermediate Event/Receive Task Configuration section you can specify an Event type (BPMN icon), for example a Message Start Event, on which to allow restricted access by filtering the IP address
    • Access to Message Catch Event API from within the same workflow platform is not subject to IP address filtering
    • To specify an Event type on which to apply filtering, select an option from the dropdown menu then click the button
    • When adding A Specific App option it is necessary to edit the Path Prefix so that the App ID is displayed instead of the text in brackets “(processModelInfoId)”, and for A Specific Node option, the node number instead of “(nodeNumber)” in addition to it
      • (ProcessModelInfoId) is replaced by the number following “m” of “App ID” on the application details screen, and (nodeNumber) is replaced by the number which the event type name following at the top of the property screen of the event icon in the workflow diagram
  • Unchecking the Enable IP Address Filtering box and saving this will result in any details entered being erased
  • Configurations with a longer Path Prefix will take precedence over shorter Path Prefixes and global configuration

See also

%d bloggers like this: