causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

causes users to be assigned a username and role corresponding to the subject DN from their SSL certificate. In these kinds of situations the broker will use this assigned (i.e. validated) username for that core clients will now expect the CN or Subject Alternative Name values of the broker’s SSL certificate to match the hostname in the client’s URL. This impacts all core-based clients including core • Exclusive consumers. • Equivalent ActiveMQ "Classic" Virtual Topic naming abilities. • SSL Certificate revocation list. • Last-value queue support for OpenWire. • Support masked passwords in bootstrap

is the path to the SSL key store on the server which holds the server's certificates (whether self-signed or signed by an authority). When used on a connector this is the path to the client-side SSL handling multiple values. The JAAS certificate authentication login module must be used in combination with SSL and the clients must be configured with their own certificate. In this scenario, authentication authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is as follows: To further constrain the set of acceptable

is the path to the SSL key store on the server which holds the server's certificates (whether self-signed or signed by an authority). When used on a connector this is the path to the client-side SSL handling multiple values. The JAAS certificate authentication login module must be used in combination with SSL and the clients must be configured with their own certificate. In this scenario, authentication authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is as follows: To further constrain the set of acceptable