Open dkelosky opened 1 week ago
Is this a code bug, or a usability/doc issue?
If san is indeed required (as it appears to be for RACF defaults), there are a few ideas:
WARNING: Due to the limitation of the ZWESECUR job, exit with 0 does not mean the job is fully successful. Please check the job log to determine if there are any inline errors.
Since there could be inline information messages that could indicate a problem, not just errors
This area in the yaml could be marked commonly customized
Start up of api ml should detect this scenario and put out a clearer error message
On a new install of Zowe 2.18, I used "Certificate setup scenario 3" The
zowe.setup.certificate.san
is commented out but does not have the comment eye catcher**COMMONLY_CUSTOMIZED**
. It also appears that if you do not add these values theZWEKRING
job puts out an informational message :This leads to this issue:
Although these are informational messages - API ML will not start up in this state.