[prev in list] [next in list] [prev in thread] [next in thread]
List: racf-l
Subject: Re: FTPS executing from one LPAR to another but fails
From: "VANDER WOUDE, PETER" <pwoude () HARRISTEETER ! COM>
Date: 2021-10-11 13:16:24
Message-ID: BLAPR15MB402094CD0499C6C6FC7389C4ADB59 () BLAPR15MB4020 ! namprd15 ! prod ! outlook ! com
[Download RAW message or body]
I don't recall if you mentioned, but are the certificates self-signed? If so, then \
you have to add the public key to the keyring of the other lpar, with usage type of \
CERTAUTH.
Regards,
Peter
-----Original Message-----
From: RACF Discussion List <RACF-L@LISTSERV.UGA.EDU> On Behalf Of Spivey, Debra
Sent: Monday, October 11, 2021 9:12 AM
To: RACF-L@LISTSERV.UGA.EDU
Subject: Re: FTPS executing from one LPAR to another but fails
CAUTION: This email originated from outside the organization. Do not click links or \
open attachments unless you recognize the sender and know the content is safe.
We are using the same PAGENT for both LPAR's.
-----Original Message-----
From: RACF Discussion List <RACF-L@LISTSERV.UGA.EDU> On Behalf Of Steve Beaver
Sent: Friday, October 8, 2021 11:27 AM
To: RACF-L@LISTSERV.UGA.EDU
Subject: [External] Re: FTPS executing from one LPAR to another but fails
EXTERNAL: This email originated from outside of the organization. Do not click any \
links or open any attachments unless you trust the sender and know the content is \
safe.
Looks like you have a certificate problem. Does this work on your other LPAR? And is \
Pagent the same on both LPARS?
Sent from my iPhone
No one said I could type with one thumb
> On Oct 8, 2021, at 09:47, Massimo Biancucci <mad4ict@gmail.com> wrote:
>
> Debra,
>
> what about the client ?
> Windows, Linux ?
> I googled and somebody reported issues coming from the client configuration..
> So maybe it's not a strictly-RACF issue.
>
> Regards.
>
> Max
>
> > Il giorno ven 8 ott 2021 alle ore 16:25 Spivey, Debra
> > <spiveyd@labcorp.com> ha scritto:
> >
> > Here is part of the error when the job is submitted via a id with
> > RACF
> > SPECIAL:
> >
> > FC0287 ftpAuth: security values: mech=TLS, tlsmech=ATTLS, tlsreuse=N,
> > sFTP=A, s
> > FC2963 ftpAuthAttls: AT-TLS policy set as application controlled.
> > FU2342 TTLSRule: FTPC@SecureClient
> > FU2348 TTLSGroupAction: FTPC@SecureGrpAct
> > FU2354 TTLSEnvironmentAction: FTPC@SecureServerEnvAct EZA1701I >>>
> > AUTH TLS
> > 234 Proceed with negotiation.
> > FC3130 authServerAttls: Start Handshake
> > FC3139 authServerAttls: ioctl() failed on SIOCTTLSCTL - EDC8121I
> > Connection res EZA1735I Std Return Code = 10234, Error Code = 00010
> > EZA2897I Authentication negotiation failed EZA1534I *** Control
> > connection with ????????.LABCORP.COM dies.
> >
> > ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
> > ÄÄÄÄÄ
-This e-mail and any attachments may contain CONFIDENTIAL information, including \
PROTECTED HEALTH INFORMATION, and is meant to be viewed solely by the intended \
recipient. If you are not the intended recipient, any use or disclosure of this \
information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any \
attachments and notify the sender immediately.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic