Plan how GlobalForms is reached on your network, including making forms available to people outside your organization.
Ports
|
Setting |
Default |
Used for |
|---|---|---|
|
|
3001 |
HTTP |
|
|
5454 |
HTTPS, once a certificate is configured |
To change a port, set it in config\local.json, update domain to match, and restart the GlobalForms service:
{
"domain": "https://forms.example.com",
"sslPort": 443
}
Then update firewall rules and any links, bookmarks and GlobalCapture connections that use the old address. See Configuration Files.
Server placement
GlobalForms can run on the same server as GlobalCapture and GlobalSearch, or on its own server. To make forms available outside your network, you can place GlobalForms on a separate server in a DMZ or another network segment.
-
GlobalCapture must be able to reach GlobalForms at its HTTPS address, for example
https://forms.example.com. -
GlobalForms must be able to reach MongoDB and any SQL servers or APIs your forms use.
-
GlobalForms needs outbound HTTPS to
update.square9.cloudand the npm registry for updates. See System Requirements.
Checklist for forms used outside your network
|
Check |
See |
|---|---|
|
Serve GlobalForms over HTTPS with a certificate from a trusted certificate authority. Never run production workloads without HTTPS. |
|
|
Expose only the HTTPS port to the internet. Block HTTP (3001) at the firewall. |
Your firewall |
|
Review form and submission permissions, especially for the Anonymous role. |
|
|
Restrict file uploads. |
|
|
Keep the default security headers, and allow only the sites you need. |
|
|
Protect SQL lookups with tokens and minimal queries. |
|
|
Work through the submission security checklist. |