HTTPS Transport Elements
The HTTPS transport does not add any further properties to those included
in the HTTP transport, but it does have these additional child elements that
are needed:
tls-client refers to client key stores that contain certificates necessary for
identification. It has a path attribute that indicates a relative or fullyqualified
path to the store; a storePassword attribute is the password
needed to unlock it.
tls-key-store refers to key stores needed for the server. It has a path
attribute that indicates a relative or fully-qualified path to the store. The
storePassword attribute is the password needed to unlock it, and the
keyPassword attribute is the password that unlocks the private key.
tls-server refers to the key store that contains the public certificates of
trusted servers. Its path attribute indicates a relative or fully-qualified path to
the store and its storePassword attribute is the password needed to unlock
it.
Example
Here’s an example using an HTTPS connector called
partnerCommunication:
https:connector name="partnerCommunication">
https:tls-key-store path="bin/serverKeyStore" keyPassword="pr1vateKey" storePassword="passw0rd"/>
https:tls-client path="bin/clientStore" storePassword="cl1entPassword"/>
https:tls-server path="bin/trustedServers" storePassword="trustPassw0rd"/>
/https:connector>
It uses three key stores:
Its main key store is stored in a file called serverKeyStore under the bin
directory, which can be unlocked using a password of passw0rd and whose
private key is accessible using a password of pr1vateKey.
Its client key store is in a file called clientStore in the same directory and
can be accessed using the password cl1entPassword.
Its collection of trusted server certificates is in a file called
trustedServers in the same directory and can be accessed using a
password of trustPassw0rd.
HTTP and HTTPS Endpoints
Following are some examples of HTTP and HTTPS endpoints:
https:inbound-endpoint address="localhost:1234"/>
This first endpoint is an inbound HTTPS endpoint that will read from the
localhost on port 1234.
http:outbound-endpoint
address="user:password@mycompany.com/x1"/>
This second endpoint, on the other hand, is an outbound HTTP endpoint
that will send messages to http://mycompany.com/x1. This connection
is meant to be secure; the credentials are encoded on the endpoint in the
form of username:password and are set on the message using Basicauthentication
encoding.
