RE: Change port for IBMi Access Client

Hi Patrick,
Yes, we are using TLS1.2 protocol. I have seen this link and been following the instructions. I am trying to follow the instruction to create the certificate and seems I am having a little problem. The very beginning step mentions to create a "Certificate Authority (CA)" I do not see the link to perform this option and it mentions in the documentation that if I don't see it, then one is already created. I am pretty sure it is created it but I am not sure what I should do. Thank you.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Friday, March 10, 2023 5:35 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Change port for IBMi Access Client

External eMail: Do not open attachments or click on links unless you expected to receive them from a trusted sender.


Hello Reggie,

Am 10.03.2023 um 13:29 schrieb Reggie Monroe <RMonroe@xxxxxxxxxxxxxxxxxxxx>:

Currently we are using IBMi Access Client to connect to our AS400 systems and it is doing it via port 23. Per our security group. We need to change this to use a more secure port i.e. port 992. We have read some documentations that we need to make this change by updating certificate information. We are using some sort of certificate but from what I can tell, they all are expired and not maintained and not sure how to make this change to use port 992 instead of port 23. Would anyone have any suggestions? Thank you.

It's not only the port but the protocol that is changed: From plaintext telnet to TLS.

A quick Google search brought up this:

https://urldefense.com/v3/__https://www.ibm.com/support/pages/configuring-telnet-and-host-servers-server-authentication-tls-first-time__;!!Fat92My4sJ5u0kQe!yASLzntc3ht3nllwMC2bLbilBd5u-KmmwlzY_kiQOndGU4YiHwsd5U_jPmGQ2ujb_I0zD7XYOmiByL6D$

Should help as a starting point.

:wq! PoC

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!Fat92My4sJ5u0kQe!yASLzntc3ht3nllwMC2bLbilBd5u-KmmwlzY_kiQOndGU4YiHwsd5U_jPmGQ2ujb_I0zD7XYOq1eRJUD$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!Fat92My4sJ5u0kQe!yASLzntc3ht3nllwMC2bLbilBd5u-KmmwlzY_kiQOndGU4YiHwsd5U_jPmGQ2ujb_I0zD7XYOpbizIr6$ .

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient, and may contain material that is privileged or confidential and legally protected from disclosure. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments.