Recommend split keyring for new configurations#4645
Recommend split keyring for new configurations#4645pablocarle wants to merge 4 commits intov3.x/stagingfrom
Conversation
Signed-off-by: Pablo Carle <pablo.carle@broadcom.com>
|
build 9484 SUCCEEDED. |
|
Test workflow 7997 is started. |
| /* Connect the z/OSMF root CA signed by a recognized certificate ... */ | ||
| /* authority (CA) with the keyring ................................. */ | ||
| RACDCERT CONNECT(CERTAUTH + | ||
| LABEL('&ROOTZFCA.') + | ||
| RING(&ZOWERING.) USAGE(CERTAUTH)) + | ||
| RING(&ZOWETRST.) USAGE(CERTAUTH)) + | ||
| ID(&ZOWEUSER.) |
There was a problem hiding this comment.
Strange that there is nothing about intemediate z/OSMF's certificate at all...
There was a problem hiding this comment.
Should we add something? any suggestion?
There was a problem hiding this comment.
If you think it make sence, then we could add something similar like for Zowe's:
RACDCERT CONNECT(CERTAUTH +
LABEL('&ITRMZFCA.') +
RING(&ZOWETRST.) USAGE(CERTAUTH)) +
ID(&ZOWEUSER.)
and add new parameter ITRMZFCA in SET section.
Signed-off-by: Pablo Carle <pablo.carle@broadcom.com>
|
build 9490 SUCCEEDED. |
|
Test workflow 8003 is started. |
| //********************************************************************* | ||
| //* ATTENTION! | ||
| //* | ||
| //* This sample is DEPRECATED. |
There was a problem hiding this comment.
This sample is kept due to the SMP/E installation. It is deprecated, but updates are of course possible.
Those changes must be reflected in split versions of this sample:
- Keyring ACF2
- ZWEIKRA1
- ZWEIKRA2
- ZWEIKRA3
- Keyring RACF
- ZWEIKRR1
- ZWEIKRR2
- ZWEIKRR3
- Keyring Top Secret
- ZWEIKRT1
- ZWEIKRT2
- ZWEIKRT3
There was a problem hiding this comment.
Thank you, I'll bring the updates there
|
build 9493 SUCCEEDED. |
|
Test workflow 8006 is started. |
Signed-off-by: Pablo Carle <pablo.carle@broadcom.com>
|
build 9496 SUCCEEDED. |
|
Based on discussion in z/OS squad call, I made changes to files/SZWESAMP/ZWEIKRA1 as a sample, to discuss if these are appropriate changes, once decided I can port to other files |
|
Test workflow 8009 is started. |
| //* If truststore is selected, create keyring for it | ||
| //* If truststore is selected, connect z/OSMF certificate to it, | ||
| //* otherwise, connect to keyring | ||
| //IFTRST IF (&IFTRSTST EQ 1) THEN |
There was a problem hiding this comment.
I am not sure about this:
2 // SET IFTRSTST=0
3 //IF1 IF (&IFTRSTST = 1) THEN
IEFC653I SUBSTITUTION JCL - (0 = 1)
4 //IEFBR15 EXEC PGM=IEFBR15
5 // ELSE
6 //IEFBR14 EXEC PGM=IEFBR14
7 // ENDIF
This JCL ended with ABEND806-04, which means an attempt to call IEFBR15 (which does not exist).
Based on the doc, only predefined operands could be used (RC, ABEND, ABENDCC, RUN).
There was a problem hiding this comment.
The problem might be in empty lines w/o *.
There was a problem hiding this comment.
How can I try out these JCLs?
There was a problem hiding this comment.
Running zwe init generate will give you the rendered JCL in your zowe.setup.dataset.jcllib dataset.
PR type
Changes proposed in this PR
Split keyrings into two:
The reason behind it lies in AT-TLS configurations.
Currently, AT-TLS configuration uses keyring to set up handshakes between services; the problem lies in that some connections may be using the
PERSONALcertificate from the keyring to authenticate without knowing it, since AT-TLS will pick up certificates marked asDEFAULT.The chosen way to deal with this is to split the configuration in AT-TLS to have a keyring that contains the private key and another one that only has trusted certificates acting as a truststore.'
This PR aims at updating the recommendations for new installations, since it's not known at the beginning if the installation will use AT-TLS or not.
Documentation is being updated for the AT-TLS article, targeting the 3.4.0 release.
Does this PR introduce a breaking change?
Does this PR add or change a YAML parameter?
Is there a related doc issue or Pull Request?
Doc issue/PR number:
Other information