Enforce production TLS certificate verification | Pixie CRM Help Centre
Canonical: https://pixiecrm.com/help-centre/enforce-production-tls-certificate-verification
Publisher: Pixie Technologies LLC

Core CRM security hardening
Enforce production TLS certificate verification

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains mandatory certificate and hostname verification for production outbound connections.

Audience: Administrators and deployment engineers; Permission: Core release / deployment authority; 

Where to goAutomatic core protection — no separate staff menu route

What this guide helps you do

Understand mandatory certificate and hostname verification for production outbound connections. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

- Use the supported Pixie CRM release or workflow that produces this security control.

- Check the expected protection through an authorised test.

- Record the result in the deployment or security audit evidence.

Fields and options

- Certificate chain

- Hostname

- Validity period

- Trusted CA store

Rules and limits

- Production connections require a valid hostname, validity period and trusted certificate chain.

- Correct the endpoint, CA chain or certificate rather than disabling verification.

- Self-signed certificates require an approved private-CA deployment, not a code bypass.

Check it worked

- The protection is active without weakening another security control.

Security, audit and troubleshooting checks

- Use the exact authorised account, role and record before saving or sending.

- Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.

- Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.

- Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Related guides

Configure trusted reverse-proxy handling safely (https://pixiecrm.com/help-centre/configure-trusted-reverse-proxy-handling-safely)Review security headers and CSP report-only mode (https://pixiecrm.com/help-centre/review-security-headers-and-csp-report-only-mode)Manage API-token expiry, revocation, rotation and usage metadata (https://pixiecrm.com/help-centre/manage-api-token-expiry-revocation-rotation-and-usage-metadata)Use central security audit logging (https://pixiecrm.com/help-centre/use-central-security-audit-logging)