RE: Problem with SSL

["Justin Houchin" <justin@xxxxxxxxxxxx>]

<snip>When you configured SSL, was it for your admin instance
or for your primary instance?</snip>

No, I just wanted to test it.

<snip>2. I assigned a self-signed certificate to my HTTP instance
application (and NOT to my administration server!).</snip>

Do I do this by going into Work with secure applications, click on
QIBM_HTTP_SERVER_RTEKWEB, click Work with system certificate, click
*dftsvr, and click assign new certificate? If so, I tried
https://192.168.0.6, page cannot be displayed. I also shutdown and
restarted the server instance before doing this. I have to have
something setup incorrectly.


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com] On Behalf Of Joe Pluta
Sent: Tuesday, July 16, 2002 8:41 AM
To: midrange-l@midrange.com
Subject: RE: Problem with SSL

> From: Justin Houchin
>
> I have gone into the "Security configuration" and setup the SSL
> connection, SSL Port 2010, SSl Client Authentication-Optional. I have
> gone into the Digital Certificate Manager and did a "work with secure
> applications". I assigned my VeriSign certificate to
> QIBM_HTTP_SERVER_ADMIN. I shutdown and restarted the *admin server
> instance. I downloaded the test CA certificate to my web browser from
> VeriSign. I pass port 2001 and port 2010 through the firewall to the
> 400. I connect to my home computer using PcAnywhere to simulate being
on
> a machine outside of the firewall. I pull up a web browser and type
> https://www.reliatek.com:2001...the
> <https://www.reliatek.com:2001...the/>  machine sits there like it is
> trying to load. I check the netstat on the 400 and it shows
> 24.216.***.**    2035       as-admi >  000:00:06  Established, but
> nothing happens. When I type in https://www.reliatek.com:2010
> <https://www.reliatek.com:2010/> , it says page cannot be displayed.
Any
> Suggestions????

Okay, I'm a little confused here, but let me tell you what I got to
work:

1. I enabled SSL on my HTTP server.  I used port 443, by the way, which
is
the standard SSL port.

2. I assigned a self-signed certificate to my HTTP instance application
(and
NOT to my administration server!).

That was it.  I could now access my primary instance using
https://my400.  I
didn't even need to identify a port.

The glaring issue I see in your case is that you assigned your
certificate
to your ADMIN instance application, as if you wanted to access your
admin
instance via SSL.  When you configured SSL, was it for your admin
instance
or for your primary instance?

Second, I would test from within my firewall until I got it working (and
working means the little lock shows up in your browser), then try from
outside.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.