I am still in a bit of a State of Shock! Upon learning that SAS, as an organization, does not provide support for proper and secure configuration of the Integrated Apache Tomcat Web Server, I was taken aback, to say the least! How can you provide a Web Interface, but deny any responsibility for configuring SSL\TLS security for that Web Based Product? When I mentioned to the Server Operations mgr & the Information Security Officer, it was several minutes before they could contain their laughter!! I am trying to import a CA Signed Cert into the Tomcat Keystore file. The instructions provided are 3rd party and therefore rather generic and difficult to follow. Instructions want the keychain file and the Cert file imported separately. The Cert file that I have is the Cert and Chain bundled together, and I suspect that may be the source of my troubles, but since SAS does not support the activity, I am not sure whom I can ask for guidance. My importation step received a Successful report. When I try to start the SASStudioWebAppServer it fails with java.io.IOException: Alias name (Aliasname) does not identify a key entry. Has anyone completed a configuration of a CA Signed Cert into their KeyStore file? Have a set of steps/procedures that you can share?
... View more