Re: RDi Secure Connection?

[Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>]

Jack,

You can use a self-signed certificate with RDi... however, it will not work with the debugger.  You'll have to turn off the secure connection to debug.

Greg

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack Woehr via WDSCI-L
Sent: Sunday, July 25, 2021 10:23 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi Secure Connection?

Never mind ... It said "restart the workspace" so I restarted RDi and that
did not work.
However, then I reloaded the workspace and secure connection did work.
Silly me. Must change some persistent setting when you restart the
workspace.

On Sun, Jul 25, 2021 at 7:57 PM Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

> On Sun, Jul 25, 2021 at 7:33 PM Jack Woehr <
> jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> > RDi won't make a Secure Connection to my servers.
> > I suspect it doesn't like the self-signed certs.
> > If this is the problem, how do I store the certs so it will accept them?
> > I tried searching help, but the Search says, "Indexing, please wait" and
> > hangs forever at 50%.
> Found this link:
> https://www.ibm.com/docs/en/rdfi/9.6.0?topic=ssl-registering-host-certificate-client
> and followed the procedure. RDi accepted the certs but RDi still won't
> make the secure connection.
>
> --
Jack Woehr, IBM Champion 2021
<https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/public_url>
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE:  This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information.  If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited.  If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.