The SSL APIs used in the agent should handle all that. If you have TLS set
up properly and your QSSL* system values set up right and are on V7R3 or
above, the only thing you may need to do is import the CA chain used by the
certificate on the server.

On Wed, Nov 26, 2025 at 11:10 AM <smith5646midrange@xxxxxxxxx> wrote:

I have a client that has a custom server / agent software package. The
server runs on windows. The agent runs on the IBMi and some other
platforms. They want to add TLS1.2 protocol to the communication and I
have
to do the IBMi side. I'm apparently not googling with the right keywords
because I'm not finding any details on how to implement it. Are there code
changes that need to be made? It is just a different port and the
encryption / decryption automatically happens? I'm lost. Can someone
point
me in the right direction for what changes have to be made to the IBMi
agent
for TLS1.2? I'll take web links, keywords for google searches, of anything
else that get me heading in the right direction. I am open to doing a
teams
meeting if that would be easier. Just send me an offline request with
times
that you are available.



Thanks in advance.

--
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://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.