Skip to content
Cockpit
Open product menu

Docs

Integrations

Per-Project connections for MuleSoft / Anypoint, Salesforce, Postman, GitHub, and Cursor.

Connected apps live on the Project

Open Integrations (app.orcaesb.com/integrations) and pick a Project. Credentials never cross Projects. Settings is for password and app preferences — not the integrations editor.

  • Required for Ask: Cursor API key plus Anypoint Connected App client ID, client secret, and organization ID.
  • Optional Salesforce: Connected App consumer key, secret, and instance URL.
  • Optional loop: GitHub token and Postman API key.
  • Optional Mule EE: enable EE on the Project (t3.large+), store mule_ee_license (license.lic or base64:…), hydrate to /opt/orca-mule-runtime/license.lic, then install EE standalone on that VM. After edition=ee and licensed=true, the EE smoke gate (mule-ctl smoke-ee) can run a verify or documented mvn -P orca-ee-smoke test. Integrations and Projects show read-only Kernel vs EE, version, and licensed badges from the Project VM. Kernel stays on the AMI — the license and EE zip are never baked in. Hosted EE-class deploys stay on CH2.

How to write secrets

Paste fields on Integrations, or import orca-cockpit-vault.biscuit.yaml from Setup. Download /vault-template.yaml, fill the known keys, then import. Empty strings are skipped; unknown keys are ignored. Treat the file like a password and delete it after import.

Storage

Secrets are AES-256-GCM sealed into Clerk private metadata as per-Project maps. They are never written to public metadata. Cookie GET stays metadata-only (which keys are set). Values are not shown again on the website after save.