The validation assumes that the protocol is always safkeyring. It is not true since Java 11, it should allow at least safkeyringjce. Anyway, there are also other types, so the proper validation should be like ^safkeyring[a-z]*:\/\/.
There are workarounds:
disable validation
use systems environment such as SERVER_SSL_KEYRING to provide the correct value
I confirm that zss and app-server both tolerate safkeyring.
zss checks for `"safkeyring.://" app-server checks for"safkeyring.*"`
So, a schema change here and use of java 11 names wont break them
https://github.com/zowe/zowe-install-packaging/blob/07b929e02b1a20dc256b806ab35c055273faa61a/schemas/zowe-yaml-schema.json#L807
The validation assumes that the protocol is always
safkeyring
. It is not true since Java 11, it should allow at leastsafkeyringjce
. Anyway, there are also other types, so the proper validation should be like^safkeyring[a-z]*:\/\/.
There are workarounds: