Ports Configuration

From idenprotect Knowledge Base
Jump to: navigation, search


In order to test an idenprotect Core Platform installation, you may need to make some changes to your server's firewall configuration surrounding Port access.

If these ports have already been configured, please continue with the rest of the Idenprotect Core Platform Prerequisites checks

Note that most of the port numbers listed here can be reconfigured, these are just the defaults which will be used during installation. Some of the ports described here may not be used, for example, usually, only either MySQL or Oracle database connection is in use, not both.

All used ports must be opened in the server firewall. Exceptions are those components which are running on the same server machine as idenprotect Core Platform. For example, if your database is running on the same server as the idenprotect Core Platform, there will be no need to open the firewall ports since all connections are local and internal.

Inbound TCP Ports

Default port Description Where to change
22 (optional) SSH port for incoming terminal connections /etc/ssh/sshd_config
443 HTTPS port for all idenprotect Core Platform communications /etc/nginx/nginx.conf
8443 (optional) Secure port for accessing EJBCA /etc/nginx/nginx.conf
8444 (optional) Port for connecting a WebSocket client Cannot be changed

Outbound TCP Ports

Default port Description Where to change
25 SMTP port for outgoing emails /etc/idenprotect/email.properties,

parameter email.gateway.port

53 DNS service port Cannot be changed
443 Push Notifications Cannot be changed
18084 UEM API calls Cannot be changed
389 or 636 (optional) LDAP communications port /etc/idenprotect/ldap.properties,

parameter ldap.server

1521 (optional) Oracle database server default network port /etc/idenprotect/database.properties,

parameter db.jdbc.url. Other databases may use other ports

3306 (optional) MySQL server default network port /etc/idenprotect/database.properties,

parameter db.jdbc.url