Hi Charles, The message is misleading. i spoke with the vendor and the message came from their side,
Tx. ITschak On Tue, Sep 4, 2018 at 12:58 AM Charles Mills <[email protected]> wrote: > What is it that our associate @Phil says? > > 1. The problem is with the certificates. > 2. See rule 1. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of ITschak Mugzach > Sent: Monday, September 3, 2018 1:47 PM > To: [email protected] > Subject: Re: HTTPS end-up with rc 417 for self-signed certificate > > Yes. same results. > > ITschak > > On Mon, Sep 3, 2018 at 11:35 PM Charles Mills <[email protected]> wrote: > > > Did you mark the CA certificate as trusted? > > > > Charles > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of ITschak Mugzach > > Sent: Monday, September 3, 2018 1:25 PM > > To: [email protected] > > Subject: HTTPS end-up with rc 417 for self-signed certificate > > > > I uploaded a self signed certificate to RACF, added it to my keyring as > > personal, trust & default. When trying to connect to the server, I get rc > > 417 and msg "Self-signed certificate cannot be validated". I tried to > > upload the CA certificate (self signed as well) as a certauth and added > it > > to my keyring. DIGTCERT and DIGTRISG refreshed. > > It worked in the past, but this is a new racf, and somehow I list the > JCL I > > used. > > > > Is there any guide on how-to with self signed certificates? > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > -- > ITschak Mugzach > *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring > for Legacy **| * > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
