# Ports

Ports provide TCP/IP connectivity for messaging and management. A port is defined to use a protocol. This can be an AMQP protocol for messaging or HTTP/JMX for management.

A port is defined to have one or more transports. A transport can either be plain (TCP) or SSL. When SSL is in use, the port can be configured to accept or require client authentication.

Any number of ports defined to use AMQP or HTTP protocols can be defined. JMX is limited to a single port instance per JMX protocol type.

Ports can only be managed by the HTTP management channel.

## Attributes

- Name the port.

- Port number.

- Binding address. Used to limit port binding to a single network interface.

- Authentication Provider. The authentication provider used to authenticate incoming connections.

- Protocol(s). A list of protocols to be supported by the port. For messaging choose one or more AMQP protocols. For management choose HTTP or on one the two JMX protocols.

- Transports. A list of transports supported by the port. For messaging or HTTP management chose TCP, SSL or both. For JMX, the TCP/SSL combination is not supported.

- Keystore. Keystore containing the Broker's private key. Required if the SSL is in use.

- Want/Need Client Auth. Client authentication can be either accepted if offered (want), or demanded (need). When Client Certificate Authentication is in use a Truststore must be configured. When using Client Certificate Authentication it may be desirable to use the External Authentication Provider.

  JMX does not support client authentication.

- Truststore. Trust store contain an issuer certificate or the public keys of the clients themselves if peers only is desired.

## Children

None

## Lifecycle

Not supported

When updating an existing port, changes to SSL settings, binding address and port numbers do not become effective until the Broker is restarted.