RE: Problem with SSL

["Mark Villa" <markvilla@xxxxxxxxxxx>]

~~~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?
~~~

Justin,
The indicator: *COMPATIBLE is normal
it will say *ERROR if not okay.
SSL is pretty tricky.
Can you get a telnet session on port 992?
I would not trust an install until successful secure connect on some port.
The other guys are right, you will see the prerequisite port listening using
NETSTAT *CNN command.
If you do not resolve, you may want to start looking at job logs for the
socket refusal errors, to pin down what is failing.
I am no expert at it, but the logs told me more than once that I was not
trusted, because I did something out of step or it failed to save my
certificate settings, etc.

Also, can you turn your lock on and connect via Client Access?
The older the OS/400 version the more PTF's are needed.
My experience is with internal trust so I do not know how 3rd party
certificates may fail in this context.


Hope this is helpful,

Mark Villa in Charleston SC