Communicating with an SSL-enabled HTTP server
 
note
Due to export restrictions, the SSL_connect OPI is only available upon request.
The SSL_connect OPI allows PV-WAVE sessions to communicate and exchange data with an SSL-enabled HTTP server (HTTPS). The PV-WAVE SSL_connect OPI uses the OpenSSL library to support the client side of an SSL connection. There is currently no support for PV-WAVE to act as an SSL-enabled server. If you wish to have two PV-WAVE sessions communicate with each other you should use the PV-WAVE socket OPI.
The basic steps for exchanging data with an HTTPS server are:
*Load the SSL_connect OPI into your PV-WAVE session.
*Establish a connection with the remote server.
*Optionally validate the server as a trusted source.
*Send your command to the server as a PV-WAVE STRING.
*Read and parse the response, returned as a PV-WAVE BYTE array.
*Close the connection.
Table 2-4: SSL_connect OPI Routines lists the SSL_connect OPI routines.
 
SSL_connect OPI Routines
Function/Procedure
Purpose
Closes an SSL connection and frees the local resources.
Initializes the OpenSSL library and establishes a connection with a remote HTTPS server.
Reads a BYTE array from a connection with an SSL-enabled HTTP server.
Writes a PV-WAVE STRING to an established SSL connection.
Loads the SSL_connect OPI into your PV-WAVE session.
A working example of this process is found in the ssl_demo.pro procedure in the SSL_connect lib directory.
The OpenSSL library is statically linked to the SSL_connect shared objects, so you do not need to have it present on your system. The OpenSSL version for your product can be found in the file SSL_Connect<version>\SSL_version in the product distribution.