Re: Another angle... Client Authentication with SSL?

I don't know the steps you go through to write your own, but if you use 
client authentication with iSeries Access you need to create a certificate 
for the client, which can be done on the iSeries itself using the *ADMIN 
http server.  Then you install it on the client.  It was fairly 
straightforward, and works well, but there were several steps to getting 
it installed & operational.  I know I found instructions somewhere, if I 
can find them, I'll post a link.




"Brad Stone" <brad@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/12/04 02:22 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Another angle... Client Authentication with SSL?






In working with my problem I'm having a hard time finding
information that deals with the client end of doing SSL
communications using Client Authentication.

Would anyone care to explain the difference between Client
Authentication and "normal" SSL from the client end?

I've received a set of public keys from the TP, installed
them, and now when we do "normal" SSL everything works
great.  When we use what they call "SSL with client
authentication" it errors out with the "Bad Peer" error on
the client end.

I'm using the SSL APIs which have worked great until this
point.  I just can't find what is different with Client
Authentication SSL and what I may need to do differently
with my application.  Seems like it should work just fine.

TIA!
_______________________________________________
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.