This is for sure covered in the documentation (I know it doesn't help
that the documentation stinks). I'm pretty sure that creating a
certificate authority is only required if you'll be self-signing
certificates and the *SYSTEM certificate store (you may see this called
a key store) should be there already. If the certificate store isn't
there, there is an option in DCM to create it. You really need to take
the time to understand what you're doing. It is very easy to do this
wrong which will cause problems for people accessing the site.

Take another look at the documentation. Start with looking for how to
create the *SYSTEM certificate store. Once that's done, look for how to
create a certificate authority.

The good news with all of this is that once you do it the first time,
the documentation will make sense. FWIW, setting up SSL on OS/400 is
much easier than I've seen on other platforms. IBM did a good job of
providing easy to use tools, they just fell short on the documentation.


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Pugazh
Sent: Wednesday, August 02, 2006 10:53 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Book to implement SSL

"It is assumed that a certificate authority (and
certificate store) is already established for the
iSeries Digital Certificate Manager" 

- How do I do this?

--- Bryan Dietz <BDietz@xxxxxxxxxx> wrote:

maybe the manuals will help:

Bryan Dietz
Aktion Associates

"i want an i"

web400-bounces@xxxxxxxxxxxx wrote on 08/02/2006
10:12:48 PM:

-> Guys,
-> Can any of you recommend any easy to follow books
-> will help me implement SSL for my website, I need
-> start completely from scratch?
-> Thnx

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].