This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

NetWitness Community

  • Home
  • Products
    • NetWitness Platform
      • Advisories
      • Documentation
        • Platform Documentation
        • Known Issues
        • Security Fixes
        • Hardware Documentation
        • Threat Content
        • Unified Data Model
        • Videos
      • Downloads
      • Integrations
      • Knowledge Base
    • NetWitness Cloud SIEM
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Detect AI
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Investigator
    • NetWitness Orchestrator
      • Advisories
      • Documentation
      • Knowledge Base
      • Legacy NetWitness Orchestrator
        • Advisories
        • Documentation
  • Community
    • Blog
    • Discussions
    • Events
    • Idea Exchange
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Community Support Forum
      • Community Support Articles
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Training
    • Blog
    • Certification Program
    • Course Catalog
      • Netwitness XDR
      • EC-Council Training
    • New Product Readiness
    • On-Demand Subscriptions
    • Student Resources
    • Upcoming Events
    • Role-Based Training
  • Technology Partners
  • Trust Center
Sign InRegister Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
NetWitness Discussions
  • NetWitness Community
  • Discussions
  • Re: updating Public CA certificate on 11.1
  • Options
    • Subscribe to RSS Feed
    • Mark Topic as New
    • Mark Topic as Read
    • Float this Topic for Current User
    • Bookmark
    • Subscribe
    • Mute
    • Printer Friendly Page

updating Public CA certificate on 11.1

Go to solution
GayathriPulla
GayathriPulla New Contributor
New Contributor
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 07:33 AM

Hi All, 
Is there any article how to update the Public ca certificate and server certificate for NW server console. I am not able to find any article for 11.1

  • Community Thread
  • Discussion
  • Forum Thread
  • NetWitness
  • NW
  • NWP
  • RSA NetWitness
  • RSA NetWitness Platform
0 Likes
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
SeanKoniarz
SeanKoniarz Beginner
Beginner
In response to GayathriPulla
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 09:37 AM

This is taken from the security config guide.  I can confirm that this works perfectly.

 

1.Rename your certificate files and save them in for NGINX.

Rename the customer provided cert.pem certificate pem file to web-server-cert.pem.

Rename the customer provided key.pem key pem file to web-server-key.pem.

Rename customer provided cert.chain certificate chain file to web-server-cert.chain.

Rename cert.p7b certificate p7b file to web-server-cert.p7b.


2.SSH to the NW Server.


3.Replace the existing NetWitness Suite generated /etc/pki/nw/web/web-server-cert.pem, /etc/pki/nw/web/web-server-key.pem, /etc/pki/nw/web/web-server-cert.chain and /etc/pki/nw/web/web-server-cert.p7b files with the files you renamed in step 1.


4.Restart NGINX service.service nginx restart.

View solution in original post

0 Likes
Reply
10 REPLIES 10

Go to solution
AaronMartin2
Employee AaronMartin2
Employee
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 09:15 AM

Have a look at this guy:

 

https://community.rsa.com/docs/DOC-90913 

 

Page 61, last I checked.

0 Likes
Reply

Go to solution
GayathriPulla
GayathriPulla New Contributor
New Contributor
In response to AaronMartin2
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 09:28 AM

Hi Martin, 
There is no process mentioned on page 61 for updating external certificates as well there is column mentioned to refer "SSL Certificate Guidance for NetWitness Suite" to upload External certificates. But I am not able to find the article for the same.

 

pastedImage_1.png

0 Likes
Reply

Go to solution
SeanKoniarz
SeanKoniarz Beginner
Beginner
In response to GayathriPulla
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 09:37 AM

This is taken from the security config guide.  I can confirm that this works perfectly.

 

1.Rename your certificate files and save them in for NGINX.

Rename the customer provided cert.pem certificate pem file to web-server-cert.pem.

Rename the customer provided key.pem key pem file to web-server-key.pem.

Rename customer provided cert.chain certificate chain file to web-server-cert.chain.

Rename cert.p7b certificate p7b file to web-server-cert.p7b.


2.SSH to the NW Server.


3.Replace the existing NetWitness Suite generated /etc/pki/nw/web/web-server-cert.pem, /etc/pki/nw/web/web-server-key.pem, /etc/pki/nw/web/web-server-cert.chain and /etc/pki/nw/web/web-server-cert.p7b files with the files you renamed in step 1.


4.Restart NGINX service.service nginx restart.

0 Likes
Reply

Go to solution
AaronMartin2
Employee AaronMartin2
Employee
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-23 09:41 AM

Sean's steps are correct. It would appear that the document has since been changed since I last interacted with it. I apologize for that. I am currently looking for their new location.

Thanks Sean.

0 Likes
Reply

Go to solution
GayathriPulla
GayathriPulla New Contributor
New Contributor
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-24 03:44 AM

Hi Aaron & Sean,

 

Thanks for the steps, that would be much more useful., I was provided with with a certificate in .crt form which I can convert to .pem form 
 /etc/pki/nw/web/web-server-cert.pem-- this is for server certificate
/etc/pki/nw/web/web-server-key.pem, -Key for server certificate
/etc/pki/nw/web/web-server-cert.chain - Root & Intermediate certificate?
/etc/pki/nw/web/web-server-cert.p7b- what would this be?
Please clarify whether I am correct ? Also, would it be Okay, If I have no Key certificate?

0 Likes
Reply

Go to solution
AaronMartin2
Employee AaronMartin2
Employee
In response to GayathriPulla
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-07-24 09:32 AM

You'll need the key. The p7b is a bundle contains the certificate and any chain certificates that exist. No key is included in this bundle.

And I must add that you should backup the /etc/pki/nw/web/ files before you replace them up.

 

If your organization has a certificate authority, you can probably show them these instructions and they should be able to get exactly what you need.

2 Likes
Reply

Go to solution
GayathriPulla
GayathriPulla New Contributor
New Contributor
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-09-20 05:54 AM

Hi I have added the root Certificate as well as the server certificate as suggested, but still it is showing me Not secure option as below. Its not showing any Invalid Ceritificate as well.. Then how can I remove this insecure thing.

pastedImage_1.png

0 Likes
Reply

Go to solution
JoshRandall
Valued Contributor JoshRandall Valued Contributor
Valued Contributor
In response to GayathriPulla
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-09-21 05:06 PM

It might be an issue with the cert not being part of your OS's and/or browser's trusted certificate store.  You can import your server cert and your CA cert and see if those help resolve this.

 

And fwiw, in my lab I have run through this process and Firefox shows everything Secure/Green, but Chrome does not.

 

image002.jpg

 

image004.jpg


Mr. Mongo
0 Likes
Reply

Go to solution
HemanathSeethar
HemanathSeethar Beginner
Beginner
In response to JoshRandall
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2018-09-24 05:27 AM

We should  include Subject Alternative Name into the certificate when we generate the same. 

 

For Chrome 58 and later, only the subjectAlternativeName extension, not commonName, is used to match the domain name and site certificate. The certificate subject alternative name can be a domain name or IP address. 

 

https://support.google.com/chrome/a/answer/7391219?hl=en

0 Likes
Reply
  • « Previous
    • 1
    • 2
  • Next »
Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Acceptable Use Policy
  • Employee Login
© 2022 RSA Security LLC or its affiliates. All rights reserved.