RE: Problem with SSL

I have the following:

5722SS1   *COMPATIBLE  OS/400 - Digital Certificate Manager
5722AC3   *INSTALLED   Crypto Access Provider 128-bit for AS/400
5769CE2   *INSTALLED   Client Encryption 56-bit
5722CE3   *INSTALLED   Client Encryption 128-bit

I finally got my admin server listening on port 2010 again by editing the
config file manually.  I couldn't get the Apache configuration to do what I
needed.  I don't know if my findings will help you since you said you're on
V4R5 and I'm on V5R1.

I would say when you start the HTTP server, find the jobs.  Then after you
connect to https://192.168.x.x check the joblog for each of the server jobs.
I thought they used to be in QUSRWRK or QSYSWRK but mine are in QHTTPSVR.
Use WRKSBSJOB QHTTPSVR to find the jobs.  If the server ends when you
attempt to connect, it should produce a joblog.

HTH

>-----Original Message-----
>From: Justin Houchin
>
>       Yes it is listening on port 443. I have read step by step on how
>to setup the Digital Certificate Manager with the redbook "Building a
>Digital Infrastructure". Before I started this project I had to install
>the Digital Certicate Manager, Crytographic Support, and the
>Crytographic Access Provider 128bit. When I got done installing them,
>the Crytographic Access Privider 128bit showed *INSTALLED while the
>other to showed *COMPATIBLE. Could this be a problem?
>
>-----Original Message-----
>From: Sean Porterfield
>
>>From: Mark Villa
>
>>~~~Scott Wrote,
>>~~~>Did you try accessing it by domain name instead of ip adrress?
>>Interesting conversation. Sorry for jumping in the middle.
>>It would seem that validation could only occur using a registered
>public IP
>>address. Got to put the resolution here for us to read. If
>>192.168.x.x works
>>that means anyone can use your cert.
>
>
>Actually, IE should pop up a security warning if it doesn't like the
>cert.
>It asks if you want to accept (yes/no/view cert) at which point you can
>even
>add it to the cert database on the pc so IE will trust it every time.
>
>Since I've lost the original thread now...  Justin - did you ever verify
>in
>netstat that the AS/400 was listening on port 443?  (Assuming you
>started
>more than just the admin server, that is.)