Inbound Ports
Pulse One/Workspace uses the following inbound ports when communicating.
|
Endpoint |
Ports |
Authentication |
Comments |
|
Browser / Admin UI |
443 |
Password / HAWK |
Password is used to initiate a session. The browser client then uses its session to upgrade to HAWK credentials. |
|
PCS/PPS |
443 |
HAWK |
|
|
Apple iOS MDM agent |
443 |
Device Cert |
Inbound MDM requests are signed with the device certificate, which is verified by the server. |
|
Pulse iOS PWS client |
443 |
OTP/SAML then HAWK |
Once the user authenticates with OTP or SAML, the server generates HAWK credentials for the client. |
|
Pulse iOS VPN client |
|
|
Does not connect to PWS servers. Connects only to VPN servers. |
|
Android Work client |
|
|
Does not connect to PWS servers. Connects only to Google. |
|
Android Pulse DPC client |
443 |
OTP/SAML then HAWK |
Once the user authenticates with OTP or SAML, the server generates HAWK credentials for the client. |
|
|
80 |
n/a |
HTTP access. Incoming traffic on this port is automatically redirected to port 443 over HTTPS. |
|
|
22 |
Username / Password |
Admin access via SSH to MGMT interface. |
|
|
514 |
No authentication |
514 is syslog without authentication/encryption. Pulse Secure advises that you always enable TLS (see below) to use port 6514 with authentication and encryption. |
|
|
6514 |
Certificate |
6514 is syslog over TLS. Pulse Secure advises that you always enable TLS to ensure authentication and encryption. |