Re: IBM Access Client Solutions over TLS versus self-signed server certificate renewal

If it's a self-signed cert and the new one has the same signer (or CA)
which it should, it should be seamless.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #13 <https://www.bvstools.com/mailtool.html>: The ability
to use an IFS stream file as the body of the email (either text or html).

On Wed, Jan 23, 2019 at 9:16 AM Jack Callahan <jjcllhn@xxxxxxxxx> wrote:

Last year, I created a self signed server certificate, built a network
deployment of ACS over TLS to secure connections. Very happy to close a
large vulnerability- old Client Access installs configured to pass
credentials in plain text.

Said server certificate will expire in February. I can renew the
certificate in DCM, and assign it the the corresponding ACS services.

What can I expect to happen when the current ACS clients attempt to connect
using the old server certificate?

Will the user be prompted to accept the new certificate?

Will the connections just fail?

Do I need to rebuild the ACS network deployment configuration to include
the new server certificate?

Appreciate anyone willing to share their experience in a similar situation
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com