000035426 - Test - Article Break Fix 3- Please Ignore

Document created by RSA Customer Support Employee on Aug 2, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035426
Applies ToCAUTION:
This procedure is not intended for use in Security Analytics 10.4.0.2, as additional steps are required.  To apply a Public CA certificate at that version, follow the steps in the knowledgebase article How to Install a Public CA Certificate on RSA Security Analytics 10.4.0.2.  If you are on RSA Security Analytics 10.6.1 or above please refer to the procedure documented in Sec/User Mgmt: Step 3. Import Server Certificate and Trusted CA Certificate.
For instructions on installing a public CA certificate on Security Analytics 10.0.x, 10.1.x, or 10.2.x running Jetty 7, refer to the knowledgebase article How to enable SSL with a CA-signed certificate on RSA Security Analytics 10.3.0 and below or RSA NetWitness Spectrum.
Issue For detailed instructions on performing this process, refer to the document entitled Installing a Public CA Certificate on RSA Security Analytics Running Jetty 9.
CauseAs documented in the JIRA ticket SACE-2368, the jetty- ssl . xml file in version 10.4.0.2 has been modified to point to a different keystore , utilizing an additional puppet recipe, which prevents customer CA certificates from being applied to Jetty.  Following the procedure in this article will result in the Jetty service repeatedly crashing.
WorkaroundAs documented in the JIRA ticket SACE-2368, the jetty- ssl . xml file in version 10.4.0.2 has been modified to point to a different keystore , utilizing an additional puppet recipe, which prevents customer CA certificates from being applied to Jetty.  Following the procedure in this article will result in the Jetty service repeatedly crashing.

Attachments

    Outcomes