The Broker supports configuration of Ports to specify the particular AMQP messaging and HTTP management connectivity it offers for use.

Each Port is configured with the particular Protocols and Transports it supports, as well as the Authentication Provider to be used to authenticate connections. Where SSL is in use, the Port configuration also defines which Keystore to use and (where supported) which TrustStore(s) and whether Client Certificates should be requested/required.

Different Ports can support different protocols, and many Ports can be configured on the Broker.

The following AMQP protocols are currently supported by the Broker:

Additionally, HTTP ports can be configured for use by the associated management plugin.

This diagram explains how Ports, Authentication Providers and an Access Control Provider work together to allow an application to form a connection to a Virtualhost.

Figure 4.9. Control flow during Authentication