Thanks Arno, for the example. I'll give it a try.
> Private Key and certificate may exist in the same file.
> It's not a method in TX509Base, however you can derive your
> own class and add this functionality. Something like below
> should do the trick:
--
To unsubscribe or change your settin
Arno Garrels wrote:
> jlist wrote:
>> What I want to do is to avoid providing the two .pem files as
>> separate files. Instead, I'd like to read the content of the two
>> files and hard-code them in a string variable, or in resource.
>
> Private Key and certificate may exist in the same file.
> It
jlist wrote:
> What I want to do is to avoid providing the two .pem files as
> separate files. Instead, I'd like to read the content of the two
> files and hard-code them in a string variable, or in resource.
Private Key and certificate may exist in the same file.
It's not a method in TX509Base, h
Hello Arno,
> Usually you do not need a certificate to connect to a SSL server.
> Your client might however communicate with multiple servers requesting
> a client certificate. If that is case leave both properties unassigned
> and handle event OnSslCliCertRequest instead, this is demonstrated in
Arno Garrels wrote:
> jlist wrote:
>> Hello Arno,
>>
>> Thanks for the reply.
>>
3. After I generated the cert files, HttpsTst demo worked fine. My
question here is, is there an easy way to use an embedded cert and
key string, as opposed to external files? I notice that the
Ss
jlist wrote:
> Hello Arno,
>
> Thanks for the reply.
>
>>> 3. After I generated the cert files, HttpsTst demo worked fine. My
>>> question here is, is there an easy way to use an embedded cert and
>>> key string, as opposed to external files? I notice that the
>>> SslContext class takes file name
