Re: Outgoing HTTP--Can it be done???

David,

we use SSL on our websites.

I believe we have all of those apart from IBM Client Encrytion.

I think all of the first three are no-charge options. Dont know about Client
Encryption, and dont know if you need it, but we dont have it?

cheers
Colin.W
----- Original Message ----- 
From: "David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 24, 2004 8:28 PM
Subject: Re: Outgoing HTTP--Can it be done???


>
> Thanks to everybody for the replies.  I've downloaded Scott's API and have
> started the setup.  It says that SSL support requires the IBM Global
Secure
> Toolkit which in turn requires:
> Digital Certificate Manager
> IBM HTTP server for AS/400
> IBM Cryptographic Access Provider
> IBM Client Encryption
>
> I've got the Digital Certificate Manager and HTTP server installed on my
> system.  What are the IBM Global Secure Toolkit, IBM Cryptographic Access
> Provider, and IBM Client Encryption?  If I do a GO LICPGM and select
option
> 11 which looks to be the what I need for one of them.  Are the others part
> of other options, something to get via PTF, or should I be looking
> somewhere else?
>
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
>
>
>
>
>
>                       michaelr_41@myfas
>                       tmail.com                To:       Midrange Systems
Technical Discussion
>
<midrange-l@xxxxxxxxxxxx>@SMTP@CTB
>                       05/24/2004 11:41         cc:
>                       AM                       Subject:  Re: Outgoing
HTTP--Can it be done???
>                       Please respond to
>                       Midrange Systems
>                       Technical
>                       Discussion
>                       <midrange-l@midra
>                       nge.com>
>
>
>
>
>
> I don't know the fdx utility, but I know you can do this with the HTTP
> API. You can get more information at
> http://www.scottklement.com/httpapi/.
>
> On Mon, 24 May 2004 11:35:31 -0500, "David A Parnin"
> <daparnin@xxxxxxxxxxxxxxxxxx> said:
> > Good morning,
> >
> > Every time I look for references about HTTP in the archives or the
> > Infocenter it seems to be in the context of using the iSeries as a HTTP
> > server but what I would like to know is if such a connection can be made
> > *from* the iSeries to another system.  If it can't be done with a native
> > command how about via QShell or something else?
> >
> > Ultimately what I want to do is transmit a file using a digital
> > certificate.  Since this is a routine transmission I would like to
> > automate
> > it either with a CL program or with a file containing the commands that
> > can
> > be used as redirected input to another command.  I've done something
> > similar with FTP (without the digital certificate) in the past but so
far
> > I
> > haven't seen anything about how this might be possible with HTTP.  The
> > recipient wants this to be sent via their web site.
> >
> > The entity that we will be sending to has provided an example of how to
> > do
> > this manually from Windows as well as providing the sample Unix script
> > below.  Thanks for any ideas or advice.
> >
> > Dave Parnin
> > Nishikawa Standard Company
> > Topeka, IN  46571
> > daparnin@xxxxxxxxxxxxxxxxxx
> >
> >
> > #!/bin/ksh
> > SSL_PKEY_FILE="/{path_to_your_certs}/{user_id.perm}";export
SSL_PKEY_FILE
> > SSL_X509_FILE="/{path_to_your_certs}/{user_id.perm}";export
SSL_X509_FILE
> > echo Beginning SSL Digital Cert Auth Login
> > ## The following syntax will depend on the client location being used.
> > /bin/fdx https://www.abc/com
> >
> > [SSLv3 Cipher DES-CBC3-SHA]
> >
> > Virtual user user_id logged in.
> >
> > fdx>
> > ### Refer to the client's documentation for further available commands
> >
> >
> >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> --
>
>   michaelr_41@xxxxxxxxxxxxxx
>
> --
> http://www.fastmail.fm - Send your email first class
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WG. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.