WSO2 deployment.toml: production readiness check
Paste your deployment.toml (API Manager, Micro Integrator or Identity Server) to find well-known settings that should not reach production. Everything runs in your browser and nothing is uploaded. We only count anonymous visits (no cookies, no IP).
Remove passwords and keys first. The file often contains secrets. The check works without them: replace each secret value with x before pasting. Secret values are never displayed in the results, but they should not be pasted at all.
A first look, not a review. It knows a handful of common issues and does not know every setting of every version: confirm each point in the documentation for your version, which each finding links to. A clean result does not mean the deployment is ready.
How to use this tool
- Open your
deployment.tomland replace every password, key and secret value withx. - Paste it and press Check.
- Go through the findings; each has a line number and, where we could confirm it, a link to the WSO2 documentation.
Example
Press "Try an example": a file with hostname = "localhost", the default admin password, the embedded H2 database and the default wso2carbon.jks keystore is reported on each of those lines.
Limits
It knows a handful of common production issues, not every setting of every version. Confirm each point in the documentation for your product and version. A clean result does not mean the deployment is ready.
Privacy and security of what you enter
The file is checked in your browser and not uploaded or stored. It often contains secrets: remove them before pasting. Secret values are never shown in the results. Ads, if shown, appear only at the bottom of the page and are loaded only after your consent choice; what you paste is never sent to us or to ad providers. See the privacy notice.
We review WSO2 API Manager, Micro Integrator and Identity Server deployments: topology, security, sizing and upgrade path, by a certified engineer. See the WSO2 services.
Message us on LinkedIn