| Products | Versions |
|---|---|
| Spotfire Analyst | All |
Organizations that develop custom mods often need to deploy them securely within their internal environments. Spotfire requires all mods to be digitally signed to ensure authenticity and integrity.
Spotfire supports standard PKI certificate chains, including certificates issued by Intermediate CAs. However, proper trust configuration is required, especially in offline environments. Additionally, Spotfire enforces that the certificate used for signing must be an end-entity (leaf) code-signing certificate.
All
Prepare your mod manifest and source files according to the Spotfire Mod Development documentation.
Obtain a code-signing certificate (.pfx) from your internal CA.
⚠️ Self-signed certificates created in Spotfire Analyst are intended for local testing only and are not recommended for production deployments.
Download the Spotfire Developer SDK to access Spotfire.Dxp.PackageBuilder-Console.exe.
The SDK file (SPOT_sfire_dev_x.x.x_.zip) is available from the Spotfire Download site.
Open a command prompt in the Package Builder directory and execute the following command:
Spotfire.Dxp.PackageBuilder-Console.exe ^
/targettype:mod ^
/mod-manifest:"[Path_to_manifest.json]" ^
/target:"[Output_Path\mod_name.mod]" ^
/cert:"[Path_to_certificate.pfx]" ^
/password:"[Your_Password]"
After packaging, the .mod file already contains the digital signature, including:
Validation does not require the private key after signing. The .pfx file is not required during runtime.
This extracts the public portion of the code-signing certificate (.cer) that was used to sign the mod. The .cer file contains only the public certificate and does not include the private key.
You can also download the .cer file when you click View all trusted signers to open the My Account page on the server, where users with trust permissions can:
To ensure Spotfire can validate the complete certificate chain (Root CA → Intermediate CA → Code-Signing Certificate), all certificates must be deployed to the appropriate trust stores.
Ensure these certificates are available on:
To automatically trust mods for end users, an administrator should add the signer certificate to the appropriate Spotfire group.
Mods signed with this certificate will now be automatically trusted for all users in that group.
Restart the following services to ensure all trust configurations are applied globally:
Once restarted, signed mods should validate successfully across the environment.
This article explains how to package and digitally sign Spotfire custom visualization mods using an internal Certificate Authority (CA). It also clarifies the trust-chain requirements when using an internal Public Key Infrastructure (PKI).
Doc: Trusting Custom Content in Spotfire
KB: How to Ensure Mod Trust Certificates are Valid
Doc: Signing a Visualization Mod using Package Builder
Doc: Exporting Code‑Signing Root Certificates
Doc: Importing Code‑Signing Certificates
Doc: Adding Trusted Signers to a Group
Community: Troubleshooting Certificate Verification Issues
Community: Spotfire Mods – Working with Trust and Certificates