22.10.2013 Views

System i: Programming Secure Sockets APIs - IBM

System i: Programming Secure Sockets APIs - IBM

System i: Programming Secure Sockets APIs - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Service Program Name: QSYS/QSOSSLSR<br />

Default Public Authority: *USE<br />

Threadsafe: Yes<br />

The gsk_attribute_get_cert_info() function is used to obtain specific information about either the server<br />

or client certificate for a secure session or an SSL environment.<br />

Parameters<br />

my_gsk_handle (Input)<br />

Indicates one of the following handles:<br />

v The handle for the secure session. (my_session_handle)<br />

v The handle for the SSL environment. (my_env_handle)<br />

certID (Input)<br />

Indicates one of the following:<br />

v GSK_LOCAL_CERT_INFO (701) - Retrieve certificate data information for the local certificate<br />

that may be sent to the remote connection. This can be retrieved using the SSL environment<br />

handle or the secure session handle.<br />

v GSK_PARTNER_CERT_INFO (700) - Retrieve certificate data information for the partner<br />

certificate that may have been received during the SSL handshake. This can only be retrieved<br />

using the secure session handle.<br />

certDataElem (Output)<br />

The address of a pointer to the certificate information returned from this function call. On output,<br />

certDataElem will contain the pointer to the information. The storage for this information was<br />

allocated by the system from user heap storage and will be freed by the gsk_secure_soc_close()<br />

API or the gsk_environment_close() API.<br />

certDataElemCount (Output)<br />

A pointer to an integer that will contain the number of certificate data elements returned from<br />

this function call.<br />

Authorities<br />

No authorization is required.<br />

Return Value<br />

gsk_attribute_get_cert_info() returns an integer. Possible values are:<br />

[GSK_OK]<br />

gsk_attribute_get_cert_info() was successful.<br />

[GSK_ATTRIBUTE_INVALID_ID]<br />

The specified certID was not valid.<br />

[GSK_INVALID_HANDLE]<br />

The handle passed in to this function was not valid.<br />

[GSK_INVALID_STATE]<br />

One of the following occurred:<br />

v A SSL environment handle was specified with a certID of GSK_LOCAL_CERT_INFO before a<br />

gsk_environment_init() has been issued.<br />

v A secure session handle was specified before a gsk_secure_soc_init() has been issued.<br />

[GSK_AS400_ERROR_INVALID_POINTER]<br />

The certDataElem or certDataElemCount pointer is not valid.<br />

<strong>Secure</strong> <strong>Sockets</strong> <strong>APIs</strong> 7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!