Configure

First-Generation Managed Package (Deprecated)

Existing installations of the first-generation Managed Package may occasionally require reconfiguration based on sandbox refreshes or GRAX application migrations. The main forms of configuration are covered below.

Trusted URLs

The components included in the package include remote callouts and iframed pages retrieved from your GRAX application server. Due to browser security restrictions, additional configuration is necessary to tell Salesforce that you trust the GRAX server to serve content in your org.

Open the "Trusted URLs" menu from the "Setup" menu, and create a new Trusted URL. Name it anything you'd like, and use the https://[...].com formatted domain name of your GRAX application as the URL value. Ensure the frame-src and img-src checkboxes are selected, and click "Save."

Due to enhanced default Content Security Policy settings in recent Salesforce releases, it's necessary to also flag GRAX's centralized authentication server as trusted. Repeat the steps above to create another Trusted URL, but use https://hq.grax.com as the URL.

GRAX API Tokens

Any time you change your GRAX application's URL or your application is migrated by GRAX, your package settings will need to be updated to point to the new location and use the right secrets.

To find the correct URL and token values for your application, open "Settings" and click "Reveal Legacy Tokens" under "API Tokens." From there, values can be copied into the package directly.

To expose the token form in the package, click "Unlock" in the bottom right of the main package page.

Remote Site Setting

Due to Apex callouts within the first-generation package code, a Remote Site Setting must be created for your GRAX application domain. Clicking the "Add Remote Site Setting" on the main package page will auto-populate the form for adding a new setting, at which point you can hit save and refresh the package page.