host and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the 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

host and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the 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

and the port of the URL define what host and port the acceptor will bind to. For In VM the Authority part of the URL defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URL define what host and port the acceptor will bind to. For In VM the Authority part of the URL defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

host and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared

and the port of the URI define what host and port the Acceptor will bind to. For In VM the Authority part of the URI defines a unique server id. The acceptor can also be configured with a set 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 key store which holds the connecting client's SSL certificate will be compared to its hostname to verify they match. This is useful only for 2-way SSL. When used on a connector the CN of the server's SSL certificate will be compared