At the highest level, regardless of deployment:
- Salesforce needs to talk to your instance of GRAX
- Your users need to talk to your instance of GRAX
- Your instance of GRAX needs to talk to Salesforce
- Your instance of GRAX needs to talk to hq.grax.com
- hq.grax.com needs to talk to Salesforce
- Your instance of GRAX needs to talk to your database
- Your instance of GRAX needs to talk to your storage
Lightning Web Components and Embedded Pages are all driven by Salesforce-to-GRAX traffic. Salesforce publishes their global IP ranges. Allow, at a minimum, the IP ranges for your Salesforce instance region to access the GRAX application API.
Connecting to GRAX from Salesforce requires a Remote Site Setting in Salesforce.
The GRAX webapp user interface depends on traffic between the browsers of user and GRAX. Allow, at a minimum, your corporate network/VPN to access the GRAX application APIs.
To query, update, or insert information in Salesforce, GRAX utilizes the REST and Composite APIs. Allow, at a minimum, at least one static IP for your GRAX application to communicate out to Salesforce.
This must include allowing SFDC Login Access from this IP, as well as allowing the traffic to leave the VPC or other infrastructure network.
For software updates, telemetry, and license monitoring, GRAX communicates with GRAX HQ. Allow the GRAX application to access hq.grax.com over HTTPS on port 443. A static IP for this communication is not currently available.
For more information on this communication, see here.
For processing of OAuth sessions and logins, GRAX HQ must authenticate against your Salesforce org. Allow hq.grax.com (126.96.36.199) to communicate with your org.
For metadata storage, search indexing, and storage optimizations, GRAX uses Postgres. Allow the GRAX application to access your configured Postgres database.
For longterm storage and History Stream, GRAX uses blob storage platforms. Allow the GRAX application to access your chosen blob storage bucket/platform.
Updated 3 days ago