|
This provides secure communication for web services. SSL is commonly
used with HTTP and so can be used with SOAP services. SSL optionally
allows the communicating parties (client <-> server) to ensure the
identity of the other party. Once this has been established, SSL
provides an encrypted connection between the client and server. The
connection includes a secure hash function (silimlar to a checksum)
so that data is not modified during the transit. This then allows
sensitive information to be transmitted over the internet. Jemboss
uses Java Secure Socket Extension (JSSE - now in J2SDK, v.1.4) to
implement SSL.
To find exactly when a certificate expires use the command:
keytool -printcert -file /usr/local/emboss/share/EMBOSS/jemboss/resources/client.cer
SSL (Secure Socket Layer) can be chosen to provide data transfer
encryption. This will make the initial connection time of the client
to the server a few seconds longer whilst the client certificate is
verified. If SSL is used then the certificate for the client (in
client.keystore) needs to be in the resources directory; if Jemboss
is distributed as a jar file (e.g. when using java web start) then
this needs to wrapped in a client.jar file in the same directory.
The BioBind installation will do this for you.
|
