- Roland Smith
- PowerBuilder
- Monday, 5 June 2023 09:06 PM UTC
PB 2022 1872
I'm working on changing our app to use HttpClient instead of WinHttp.WinHttpRequest for web api calls.
My question has to do with client side certificates. Our current code has this:
io_winhttpRequest.SetClientCertificate(is_certificate)
The HttpClient function is quite different:
SetClientCert(string p12cert, string password)
p12cert - The client's private key and public key p12 or PFX certificate file path.
password - Password of p12 or PFX certificate.
SetClientCert(string storeName, string certIssue, string certSN)
storeName - A string that specifies the name of the certificate store. Valid values are: MY, Root, Trust, CA.
certIssue - A string that identifies the entity that has signed and issued the certificate.
certSN The serial number of the certificate.
What we are passing to SetClientCertificate is a registry key. Whether any customers are using this feature, I don't know. The web api is usually one of our servers on the same network.
Any ideas would be helpful.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.