Scheduled Service Change: CornellC Mainframe Prod MVS SSL Server Certificate
Effect depends on how telnet or ftp client is configured. If client is configured to accept self-signed certificates there will be no impact. If client is configured to reject self-signed certificates the telnet or ftp will fail. If client is configured to ask about self-signed certificates user will likely see a pop-up window asking whether to accept the certificate.\n\nSSL access to CornellC production MVS (SSL telnet and SSL ftp)
There is no workaround for this issue
By error the SSL Server Certificate on the production MVS system was replaced with a self-signed certificate. This will potentially affect anyone connecting to this system using an SSL protected connection. To the best of our knowledge there are very few users that do that.\n\nThe effect on the user will depend on how their telnet or ftp client is configured. If the client is configured to acc...