Data Plane Certificates
Data Plane certificates play a critical
role in securing communication between SmartZone (SZ) controllers, Access Points (APs),
and
Data Planes (DPs). These certificates ensure that only trusted devices can participate
in
the network, protect sensitive data in transit, and support compliance with industry
security standards.
Terminology
Consider the following terminology regarding DP certificates:
- Trusted CA Certificate/Chain: A Certificate Authority (CA) certificate or a chain of certificates that establishes a trust anchor for validating the authenticity of the SZ server certificate. The chain may include intermediate and root CA certificates, and must be in PEM format.
- Certificate Chain: A sequence of certificates, where each certificate in the chain is signed by the subsequent certificate, ending with a trusted root CA: Used to establish a chain of trust from the SZ server certificate to a trusted authority.
- Self-signed Certificate: A certificate signed by its own private key, typically used as a root CA in private deployments.
- Third-party CA Certificate: A certificate issued and signed by a recognized external Certificate Authority, used for public trust and interoperability.
- Import: The action of uploading a new CA certificate or certificate chain to the SmartZone trust store for AP/DP validation purposes.
- Delete: The action of removing a CA certificate or chain from the trust store. Removing all entries disables certificate validation.
- Validation enabled: AP/DP devices require the SZ server certificate to be signed by a trusted CA from the uploaded list.
- Validation disabled: AP/DP devices do not validate the SZ server certificate.
- TLS handshake: A Transport Layer Security (TLS) handshake is the initial process that establishes a secure communication channel between two parties—typically a client and a server—before any actual data exchange occurs.
Intra‑system (AP/DP) Trusted CA Certs/Chain (Internal)
This internal trust store enables
Access Points (APs) and Data Planes (DPs) to validate the SmartZone (SZ) server
certificate for intra‑device
communications—that is, AP↔SZ and DP↔SZ control and service APIs over Transport
Layer Security (TLS). When enabled, the AP/DP acts as the TLS client and verifies
the SZ
server identity against a trusted CA chain you manage on the controller. You then
map
the server certificate in the Ruckus
Intra‑device Communication field in the Certificate Mapping
page to ensure that SZ presents the right certificate during controller‑side
handshakes.
Managing Intra System (AP/DP) Trusted CA Certificates and Certificate Validation
The Intra System
(AP/DP) Trusted CA Certs/Chain (internal) page allows you to securely
manage CA certificates and certificate chains that APs and DPs use to validate the
SmartZone (SZ) server certificate during intra-system communications.
Note: This configuration applies only to intra-system
communications between SmartZone controllers, Access Points, and Data
Planes. Enabling certificate validation is a system-wide setting and may
impact AP/DP connectivity if certificates are not properly
configured.
- In the controller web UI, select .
- To add a new trusted CA
certificate or certificate chain, click Import to open
the Import CA Certs (Chain) window and complete the
following steps to upload the required PEM-encoded CA certificate or
certificate chain file.Note: For self-signed deployments, generate a root CA and use it to sign the SZ server certificate. For third-party CA deployments, upload the CA certificate chain that issued the SZ server certificate.
- In Name, enter a descriptive name for
this CA chain (for example,
vDP-RootCA-ChainorRuckusDP-TrustChain). - (Optional) In Description, add context such as the purpose or source of the CA.
- (Optional) In
Intermediate CA Certificates, if your
SZ server certificate is signed by an intermediate CA, upload
the full chain here in the correct order (from leaf to
root).Note: Missing intermediate certificates will cause validation failures even if the root CA is present. TLS handshakes will fail because SZ cannot build a complete trust path.
- In Root CA Certificate, browse and select the PEM-encoded root CA that issued the SZ server certificate.
- Click Validate. This checks the uploaded files for format correctness and chain integrity.
- Click OK to confirm the import and add
the CA chain to the SZ trust store.Note: Once saved, SZ applies this trust configuration to NGINX for DP certificate verification. Any DP without a matching chain will be rejected when validation is enabled.
- In Name, enter a descriptive name for
this CA chain (for example,
- (Optional) To remove an
existing CA certificate or chain, select the entry in the list and click
Delete.Attention: Deleting all trusted CA certificates from this store will prevent AP and DP devices from validating the SZ server certificate, which may disrupt device connectivity.
- To enable or disable AP
and DP validation of the SZ server certificate, use the
Validate SZ server certificate toggle.Attention: Enabling validation without uploading the correct CA certificate or chain may cause AP and DP devices to lose connectivity with the controller.
SZ Trusted CA Certs/Chain (DP)
The SZ Trusted CA
Certs/Chain (DP) store on the SmartZone controller enables SmartZone to
validate incoming DP client certificates during TLS mutual authentication. Upload
the CA
certificates that issued DP client certificates—including self-signed vDP root CAs—into
this trust store.
- During initial registration and subsequent API calls, the DP presents its client certificate, which must chain to a CA trusted by SZ.
- Virtual DPs (vDPs) typically generate a self‑signed root CA and use it to sign their client certificate. SZ must import this root CA into its trust store to accept the DP connection.
Managing SZ Trusted CA Certs/Chain (DP)
The SZ Trusted CA Certs/Chain
(DP) page enables secure management of trusted Certificate Authority (CA)
certificates and certificate chains for validating Data Plane (DP) client
certificates during TLS mutual authentication.
Note: This configuration applies to controller‑side
validation of DP devices in SmartZone. When enabled, the controller
verifies that each DP presents a client certificate chaining to one of the
trusted CAs before allowing secure communication. Improper configuration may
prevent DPs from connecting to the controller.
- In the controller web UI, select .
- To add a new trusted CA certificate or certificate chain, click
Import to open the Import CA Certs
(Chain) window and complete the following steps to upload
the required PEM-encoded CA certificate or certificate chain file.Note: For self-signed deployments, generate a root CA and use it to sign the DP client certificate. For third-party CA deployments, upload the CA certificate chain that issued the DP client certificate.
- In Name, enter a descriptive name for
this CA chain (for example,
vDP-RootCA-ChainorRuckusDP-TrustChain). - (Optional) In Description, add context such as the purpose or source of the CA.
- (Optional) In
Intermediate CA Certificates, if your
DP client certificate is signed by an intermediate CA, upload
the full chain here in the correct order (from leaf to
root).Note: Missing intermediate certificates will cause validation failures even if the root CA is present. TLS handshakes will fail because SZ cannot build a complete trust path.
- In Root CA Certificate, browse and select the PEM-encoded root CA that issued the DP client certificate.
- Click Validate. This checks the uploaded files for format correctness and chain integrity.
- Click OK to confirm the import and add
the CA chain to the SZ trust store.Note: Once saved, SZ applies this trust configuration to NGINX for DP certificate verification. Any DP without a matching chain will be rejected when validation is enabled.
- In Name, enter a descriptive name for
this CA chain (for example,
- (Optional) To remove an
existing CA certificate or chain, select the entry in the list and click
Delete.Attention: Deleting all trusted CA certificates from this store will prevent SmartZone from validating DP client certificates, which may block DP onboarding and runtime TLS sessions.
- To enable or disable
SmartZone validation of DP client certificates, use the Validate DP
certificate toggle.Attention: Enabling validation without uploading the correct CA certificate or chain will cause DP devices to lose connectivity with the controller.