Hi Scott, I have found this code in the COMMSSLR4 source file (HTTPAPI): c* If peAppId begins with a slash the assume it is the name of the keyring file c if %subst(peAppId:1:1) = ‘/‘ c eval rc = gsk_attribute_set_buffer( c wkEnvh: GSK_KEYRING_FILE: c peAppId: %len(%trim(peAppId))) c if rc <> GSK_OK c callp SetError(HTTP_GSKKEYF: ‘Attempt to use ‘ + c %trim(peAppId) + ‘ cert store: ‘ + c ssl_error(rc)) c callp https_cleanup c return -1 c endif c endif I have been looking for information about GSKit, and I found this: In that website, is explained the use of gsk_attribute_get_buffer… GSK_KEYRING_FILE We can send with https_init(‘/XXXXX’) the name of the keyring file, because it is developed in COMMSSLR4. GSK_KEYRING_PWD Password for the certificate store. NOT developed. GSK_KEYRING_LABEL Certificate label in the certificate store. NOT developed. I think that if the COMMSSLR4 is changed including this last two options, I will be able to connect indicating the certificate I need, and the password of the certificate store. For example this way: (is only an example…). c if %subst(peAppId:1:1) = ‘#‘ c eval rc = gsk_attribute_set_buffer( c wkEnvh: GSK_KEYRING_PWD: c %subst(peAppId:2:(%len(%trim(peAppId))-1): c %len(%trim(peAppId)-1) c if rc <> GSK_OK c callp SetError(’SOME ERROR') c callp https_cleanup c return -1 c endif c endif c if %subst(peAppId:1:1) = ‘@‘ c eval rc = gsk_attribute_set_buffer( c wkEnvh: GSK_KEYRING_LABEL: c %subst(peAppId:2:(%len(%trim(peAppId))-1): c %len(%trim(peAppId)-1) c if rc <> GSK_OK c callp SetError(’SOME ERROR') c callp https_cleanup c return -1 c endif c endif Is possible that it works well? Christian.
|
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi