Here is what I have so far and the error I have encountered.
my $client = IO::Socket::SSL->new( # where to connect PeerHost => "example/gettoken", PeerPort => "https" SSL_cert_file => $cert_file, # typical CA file on BSD SSL_passwd_cb => sub {"secret_key"}, ) or die "failed connect or ssl handshake: $!,$SSL_ERROR"; # send and receive over SSL connection print $client "GET / HTTP/1.0\r\n\r\n"; print <$client>;
The above code give an error failed connect or ssl handshake: Invalid argument,IO::Socket::IP configuration failed When I comment out peerhost and port I nothing happens. Not sure what to do next. When I print dumper is outputs $VAR1 = bless( \*Symbol::GEN0, 'IO::Socket::SSL' ); Any help is greatly appreciated.

In reply to Re^2: How to convert curl authentication method to perl (client certificate) by newperldeveloper
in thread How to convert curl authentication method to perl by newperldeveloper

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.