Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#21 Document HTTPS client-side ceritication support

closed-invalid
nobody
5
2007-10-04
2003-06-02
Pavel Kulchenko
No

(submitted Robert Olson <olson@mcs.anl.gov>)
I didn't see this in your docs, but all it takes is (from the
LWP docs):

# CLIENT CERT SUPPORT
$ENV{HTTPS_CERT_FILE} = 'client-cert.pem';
$ENV{HTTPS_KEY_FILE} = 'client-key.pem';

Discussion

  • Byrne Reese
    Byrne Reese
    2003-07-03

    • labels: --> Documentation
    • status: open --> pending-invalid
     
  • Byrne Reese
    Byrne Reese
    2003-07-03

    Logged In: YES
    user_id=28043

    This is currently documented in the Perl POD comments found
    in SOAP/Transport/HTTP.pm. The text reads:

    __BEGIN
    =head2 SSL CERTIFICATE AUTHENTICATION

    To get certificate authentication working you need to
    specify three
    environment variables: C<HTTPS_CERT_FILE>,
    C<HTTPS_KEY_FILE>, and
    (optionally) C<HTTPS_CERT_PASS>:

    $ENV{HTTPS_CERT_FILE} = 'client-cert.pem';
    $ENV{HTTPS_KEY_FILE} = 'client-key.pem';

    Crypt::SSLeay (which is used for https support) will take
    care about
    everything else. Other options (like CA peer verification)
    can be specified
    in a similar way. See Crypt::SSLeay documentation for more
    details.

    Those who would like to use encrypted keys may check
    http://groups.yahoo.com/group/soaplite/message/729 for details.
    __END

    Paul - if there is another action you wish to take with
    this, i.e. documenting it on the web site, then please
    indicate that in the comments of this bug.

     
    • status: pending-invalid --> open-invalid
     
  • Logged In: YES
    user_id=424802

    I guess it was fixed already exactly as you indicated. Closed.

     
  • Martin Kutter
    Martin Kutter
    2007-10-04

    • assigned_to: paulclinger --> nobody
    • status: open-invalid --> closed-invalid