Open jimmschlo89 opened 9 months ago
Hi,
When you want to use keyrings in which you bring your own cert, 2 things could be done
1) You don't have a keyring, but you do have a cert to CONNECT: edit the zowe yaml for option 4, and then run zwe init certificate
, which either creates the keyring & updates the yaml, or in dry-run mode, prints out which JCL you should execute and what to update your yaml with when done. (see https://docs.zowe.org/stable/user-guide/import-certificates#importing-an-existing-jceracfks-certificate)
2) You already have a keyring: skip all options, and edit the zowe yaml directly, after ensuring the keyring is valid for use with zowe
see the sort of values you'd specify in the yaml as in the bottom of this example image
by the way, if you do run zwe init certificate
, we'd need to see that output for if there were an error that led to your current output.
Ok I have done that. Seemed to fix the problem. However the server still won't start.
Seems like TomCat can't start properly. I'm also seeing a constant cycle of the Caching Service starting/failing with these errors following the initial startup attempt:
Also is "Server Internal SSL Enabled: false" the default? Does that take additional config for internal SSL comms?
Hi, to understand more about what's going wrong now, someone would need to see the logs.
You can post them here but this is a public place so you may also prefer to email me at sgrady@rocketsoftware.com
for discretion
Will do. Thank you!
Hello! I have installed a fresh new Zowe version. I'm trying to start it but I'm running into these errors:
The errors are accurate, in that those files don't exist, but they should need to. I have an existing Zowe keyring/cert/certauth that was setup for the previous version of Zowe. I used "Option 4" in the zowe.yaml file. So why would Zowe need these files? Also isn't Zowe supposed to create them upon startup?
This seems to be preventing Zowe from starting and I'm not sure why. Any advice on what to try would be great!
Looking forward to a response! Thank you.