Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: How to add or remove ciphers in server.xml and verify the same in web browser (521858)

Last Updated: 5/29/2020Categories: How toTotal Views: 3574Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

Below are the steps to add or remove ciphers in NCM:

Log into the Application Server via CLI

Set home variable by doing the following:
source /etc/voyence.conf

Navigate to $VOYENCE_HOME/ncmcore/conf

You will find server.xml file here

Create a backup of server.xml file before making any changes so you can restore the file any moment

Open server.xml in vi editor mode: vi server.xml

Enable vi edit mode by pressing "i"

Navigate to below tag in server.xml file:
<!--  <Connector port="8880" maxHttpHeaderSize="8192" maxThreads="100" minSpareThreads="5" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true" ^M
acceptCount="100"   scheme="https" secure="true" protocol="org.apache.coyote.http11.Http11NioProtocol"^M
keystoreFile="/opt/smarts-ncm/conf/voyence-ssl.keystore"^M
clientAuth="false" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true" keystorePass="change management"^M
ciphers="TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5"/> -->

Uncomment the Connector tag by removing "<!--" open and "-->" closing tags.                                                                  (Note: You will find two <Connector port="8880"> tags in server.xml. One will be uncommented by default (below line <Executor maxThreads="300" minSpareThreads="50" name="tomcatThreadPool" namePrefix="tomcat-http--"/>) You will have to uncomment tag above this tag.)

Add or remove ciphers from above ciphers="" option ( Refer EMC Smarts Network Configuration Manager Security Configuration Guide to know list of supported ciphers for customer's NCM version)

To save changes press ESC key and type !wq

Restart vcmaster service to apply changes:
service vcmaster restart

To verify cipher used by browser after changes are made:

1.Open Mozilla firefox browser
2. Navigate to url https://<AS IP>:8880
3. You will receive unsecure connection error displayed on browser screen
4. Click Advanced

5. Click Add Exception

6. You will see Apache tomcat homepage
7. Right click on empty space. Select "View Page info"

8. Go to Security Tab

9. Under "Technical Details" section you will find the cipher that is used by the browser after changes were applied in server.xml file

Related Information

Please refer EMC Smarts Network Configuration Manager Security Configuration Guide to know list of supported ciphers for customer's NCM version

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant