Communication Ports and Network Flow
This section describes the network communication paths and required ports between components involved in the certificate enrollment workflow for BigFix MCM.
Ensure that all required ports are open and accessible between the respective components.
Communication Flow Overview
The certificate enrollment process involves communication between:
- Managed devices
- BigFix MCM server
- NDES Proxy
- NDES server
- LDAP Proxy
- Active Directory
- Certificate Authority
| Source | Destination | Port | Protocol | Purpose |
| Device | BigFix MCM Server | 443 | HTTPS | Device management, policy delivery and SCEP certificate enrollment |
| BigFix MCM Server | NDES Proxy | 443 | HTTPS | SCEP certificate requests and challenge password flow |
| BigFix MCM Server | LDAP Proxy | 636 (or 389) | LDAPS / LDAP | Directory queries |
| NDES Proxy | NDES Server | 443 | HTTPS | Forward SCEP requests and Challenge Password Requests |
| LDAP Proxy | Active Directory | 636 (or 389) | LDAPS / LDAP | Directory lookup |
| NDES Server | Certificate Authority | Dynamic RPC / 135 | RPC | Certificate issuance |
- MDM Server receives SCEP profile from BigFix to deliver to the target device.
- MDM Server sends a request for a challenge password to the NDES Proxy.
- NDES Proxy forwards request to NDES server.
- NDES generates a challenge password and returns it to the MDMServer.
- MDM Server injects the challenge password and other parameters into the SCEP Profile and delivers the profile to the device through MDM.
- Device processes the SCEP policy and as a result sends a certificate request to MCM Proxy service.
- MCM Proxy service forwards request to NDES Proxy
- NDES Proxy forwards request to NDES server
- NDES communicates with Certificate Authority
- CA issues certificate
- Certificate is returned to device