Unfortunately SE "single object operations" is not the only case when
port 99xx is being used.
I can't check it now, but I'm pretty sure there are more features using
new window and new port.
Sometimes the port is reused, so every new warning reduces the
possibility of next one.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 30.08.2023 o 21:50, Tom Brennan pisze:
In my limited experience I logon to the HMC port 443 as usual, but
then a switch to single-object-operations redirects me to the same URL
but with :995x appended. Can I assume this switch happens when you go
to SOO or perhaps do something else requiring the SE?
Wild guessing: If the OS on this HMC runs something like Apache, then
the httpd parms might have VirtualHost sections, each which could
contain a different port number. The VirtualHost section can also
specify what certificate to use, so potentially, each port could be
using a different certificate, and then yeah, I could see this problem
happening and dependent on port.
Sorry though, I don't know enough about browsers to know if there is a
solution there or not.
On 8/30/2023 11:42 AM, Radoslaw Skorupka wrote:
Unfortunately no. It *is* matter of ports.
I add the self-signed certificate whenever I connects first time
(meaning well known appliances).
And further connects work without warning.
And of course the certificate is on the list of server certificates.
However there are many entries for same IP with different port
values. And every new port means warning.
I would like to have some generic entry like https://10.10.10.10:* or
https://10.10.10.10:1-10000
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
