Re: Assorted questions and musings, Re: So has anybody come up with a solution for certificate automation that will work on a Midrange box?

On 4/3/26 12:25 PM, Tim Rowe wrote:

The Navigator team has been working to help this situation. Within
Navigator, under the Network -> Servers -> TLS Configuration

Interesting. But we're not a Navigator shop. I followed the link at the end of Mr. Rowe's posting, and tried accessing our cloud V7R5 box. Results were not encouraging. The article listed unsecured on ports 2002 and 2001, and secured on 2003 and 2010.

2003 failed immediately. When I opened a terminal session and did a WRKTCPSTS, I found out it wasn't listening. 2010 just sat there until it timed out, but at least the WRKTCPSTS showed traffic. Ditto for the unsecured ports. I then noticed the part about hostname:xxxx/Navigator, and tried that, on all the ports that were actually listening. The only one where I even got a sign-on screen was unsecured 2002, and when I tried to sign on, I got "NAV_300013: Connection to node that the GUI is running on is not available or host servers cannot be connected. Fix the network problem and retry."

I'm not averse to learning at least the rudiments of Navigator (although an entirely terminal-based solution would almost certainly be better for our purposes, given that it could then be put into a CL program, and besides, I can't imagine too many of our customers giving us Navigator access to their boxes), but at this point, I'm facing a brick wall, without any clue about where exactly the brick wall is.

--
JHHL