|
local
And I would point you to these instructions put together by one of my
colleagues
https://www.ibm.com/developerworks/community/blogs/nfrsblog/entry/how_to_
establish_a_ssl_connection_with_rational_developer_for_
power_systems?lang=en
Mike
Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
From: "Mike Hockings" <hockings@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 2017/08/21 08:39
Subject: Re: [WDSCI-L] Unable to connect using SSL in RDI with
certificateRDI.
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Can you try something?
Make sure that the HCE (5250 emulation session) is closed then restart
After RDI restarts try connecting with SSL.with
Mike
Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
From: Arco Simonse <arco400@xxxxxxxxx>
To: wdsci-l <wdsci-l@xxxxxxxxxxxx>
Date: 2017/08/21 04:04
Subject: [WDSCI-L] Unable to connect using SSL in RDI
localTCP/IP
certificate
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Hi all,
I´m having trouble with the use of an SSL certificate for RDI. It is a
local certificate created on the IBM i. The certificate is imported into
the Windows certificate store, under the "Trusted Root Certification
Authorities" and under the "Enterprise Trust". It is also imported in RDI
under "Window, Preferences, Remote Systems & SSL".
However when I check "Use secure communication methods" in the connection
properties, I'm getting the following error:
"An unknown error occurred connecting to POWER01. Check if you have
connection to the host. If the connection is not broken, check that
is configured correctly on the local machine and all host servers areerror"
started on POWER01."
Examining the RDI error log:
"Caused by: java.security.cert.CertPathBuilderException:
PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause
is:
java.security.cert.CertPathValidatorException: The certificate issued by
CN=MyCA, O=MyOrg, ST=MyPlace, C=NL is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining
and
So it says a chaining error. But the local CA is the highest available,
it is defined in the windows certificate stores.--
The same certificate is used for the connections of Access Client
Solutions, and they work just fine.
What piece am I missing here?
Thanks in advance,
Arco Simonse
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.