RE: Configure Telnet to require a certificate that I send to users

Mochasoft does not support certificates.

Christopher Bipes
Information Services Director
CrossCheck, Inc.

707.586.0551, ext. 1102
707.585.5700 FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Art Tostaine, Jr.
Sent: Tuesday, January 30, 2007 12:39 PM
To: Midrange Systems Technical Discussion
Subject: Re: Configure Telnet to require a certificate that I send to
users

We are trying to use Mochasoft or Newlook ATM.  Client Access will be a
fallback.

Thanks for the great info!

Art Tostaine

On 1/30/07, Sean Porterfield <sporter@xxxxxxxxxxxx> wrote:

Art Tostaine, Jr. wrote:

Any tips on where to import?

With the latest versions of iSeries Access, you need to have the Java 
Toolbox installed as well as (obviously) SSL.  Now, I realize I also 
"assumed" you were using iSeries Access.

I believe iSeries Navigator can actually import the server 
certificate, but I have not done that.  I'm fairly certain I exported 
that from DCM or got it in my browser as Chris Bipes suggested, 
https://iseries:992 then exported then imported with iSeries Access

Key Management.

Once I had the .kdb file with the server cert, I gave that out to all 
clients upon install.  That way they would be able to import their own

certificate anytime.  Key Management is the way to manage the user 
certificate on each client PC.

Here is a snippet from my directions that should still be fairly

accurate:

Click Start --> Programs --> IBM iSeries Access for Windows --> 
iSeries Access for Windows Properties.
  Note: Older versions may say Client Access or Client Access Express 
instead of iSeries Access for Windows.
Click on the Secure Sockets tab.
Click IBM Key Management.

You will be prompted for your key database password. Unless you have 
previously changed the password from the default, enter ca400. A 
confirmation message displays. Click OK.

From the drop-down menu in the middle of the window, select Personal

certificates. (It probably will say "Signer Certificates" there
initially.)

Click Import.

In the Import key display, enter the file name and path for the 
certificate. Click OK.
  (Note: default at this point shows *.p12 files, change that to read 
*.pfx to browse for your file.)

--
Sean Porterfield
--
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.

--
Art Tostaine (GMAIL)
--
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.