In today’s data-driven world, secure data transmission is essential to any enterprise integration strategy. Whether using HTTPS, SFTP, FTPS, or AS2, certificates are the backbone of encryption, authentication, and trust in Boomi.
This comprehensive guide combines conceptual clarity with practical implementation to help you understand, configure, deploy, and manage certificate components in Boomi like a pro.
What Are Certificates in Boomi?
Certificates are digital credentials that enable secure communication between systems. They serve three primary purposes:
- Encrypt data and communication channels
- Authenticate systems, users, and partners
- Digitally sign data for tamper-proof assurance
Boomi supports both Certificate Authority (CA)-issued and self-signed certificates.
🧾 Types of Certificates in Boomi
- Certificate Authority (CA) Certificates
- Not Boomi components
- Imported manually into the Atom’s trust store using Java’s keytool
- Stored in: jre/lib/security/cacerts (location may vary)
- Boomi User Certificates
- Managed within the Boomi Build tab
- Can be self-signed
- Packaged as Boomi components
- Reusable across processes
🔐 Subtypes
| Type | Key Content | File Extensions |
| Public X.509 | Public key only | .cer, .der |
| Local X.509 | Public + Private key | .pfx, .p12 |
| Public PGP | Public key only | _pub.asc |
| Local PGP | Public + Private key | _priv.asc |
🏗️ Creating Certificates in Boomi
🔧 Generate a Certificate (X.509 or PGP)
- Go to Build > New > X.509 Certificate or PGP Certificate
- Click Generate
- Fill in certificate details:
- CN, Organization, Location, etc.
- Algorithm: SHA2-512 (default)
- Key length: 2048 bits (default)
- Validity: 365 days (default)
- Set a password for local keys
- Click Finish and Save
📥 Import an Existing Certificate
- Open a new/existing certificate component
- Click Import
- Choose file: .pfx, .p12, .cer, etc.
- Enter password if required
- Complete import (Boomi scans for viruses automatically)
🔄 Modifying, Exporting, and Managing Certificates
🔁 Regenerate Keys or Import Updated Versions
- Helpful for rotating keys without disrupting integrations
🔑 Change Password (Local X.509 only)
- Option available under the certificate settings
📤 Export Keys
| Certificate Type | Export Options |
| Public | Export public key only |
| Local | Export public + private (password required) |
🚀 Deploying Certificates in Boomi
✅ Default Behavior:
- Certificates used in a process are automatically deployed with the process.
🔒 Recommended: Independent Deployment
- Available for Public X.509 and Public PGP
- Deployed via: Deploy > Certificates
- Loaded into the Atom’s trust store
- Avoids re-deploying all processes when certificates change
⚠️ Note: The “Use Trusted SSL Certificate” option in a connector overrides independent deployments.
💼 Real-World Use Cases
🔁 Use Case 1: HTTPS API with Mutual TLS
- Goal: Authenticate client to server using a certificate
- Cert Type: Local X.509 (.pfx)
- Steps:
- Import .pfx into Boomi
- Assign it in the HTTP Client connection
- Deployment: Certificate deployed with the process
🔐 Use Case 2: Accepting Self-Signed Server Cert
- Goal: Trust a server using a self-signed cert
- Cert Type: Public X.509 (.cer)
- Steps:
- Import .cer
- Enable Use Trusted SSL Certificate
- Deployment: Deploy certificate independently
🧭 Best Practices
✅ Use CA certificates for trusting external systems
✅ Use Boomi user certs for signing, encrypting, or authenticating
✅ Always set strong passwords for local certificates
✅ Use independent deployment for shared certs
✅ Rotate certificates before expiry and automate monitoring
✅ Match certificate format to connector requirements (e.g., .pfx for HTTPS)
📌 Conclusion
Boomi Certificate Components are a cornerstone of integration security. With support for both X.509 and PGP, and flexible deployment options, Boomi gives you the tools to securely manage encrypted data exchange, authentication, and compliance.