Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- System security
- Encryption of configuration file settings
- Encryption of operator passwords
- Encryption of client keystore passwords
- Randomly generated master keys
- Inactivity timer
- Lockout feature
- System quiesce: Login restrictions
- Mandanten file security
- Multicompany mode
- Script utilities
- Security tables
- Secure Sockets Layer (SSL) encryption and server certificates
- Support of the HTTP Strict Transport Security protocol
- Trusted sign-on
- Common Access Card (CAC) sign-on
- SAML Single Sign-On
- FIPS mode
- Tokenization
Randomly generated master keys
Service Manager (SM) uses randomly generated master keys to protect local sensitive data (for example, keystore passwords) of the SM Server, web tier, Windows Client, Mobility Client, and Service Request Catalog (SRC).
Service Manager automatically generates a master key at the first startup of each of the following components and writes it to their corresponding configuration file.
Important The data contained in these files should be considered sensitive. Be sure to take appropriate measures to protect these files by ensuring only those users with appropriate access privileges are allowed to access and view the contents of these files.
Component | Master key parameter | Configuration file |
---|---|---|
Server | smmasterkey |
Server\RUN\sm.ini Tip The encryptionkey parameter is used for encrypting fields in the database. If it is not configured, the master key in the sm.ini file is used instead. |
Web tier | masterKey |
<customize-folder>\config\webtier.properties or <web tier>\WEB-INF\webtier.properties Where: <customize-folder> represents the directory defined in the customize-folder parameter. |
Windows Client | masterKey |
%USERPROFILE%\ServiceManager\workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings\com.hp.ov.sm.client.eclipse.base.prefs |
Mobility Client | randomRawKey | <webapp>\WEB-INF\web.properties |
SRC | randomRawKey | <SRC>\WEB-INF\classes\applicationContext.properties |
Caution Once a master key is generated, do not remove it or change its value, otherwise the Service Manager Server will not start or other SM components (for example, the web tier) will not work.
You do not need to change the system-generated master keys; however, if you want the system to generate a new master key for an SM component, perform the following steps:
-
Remove the master key parameter from the corresponding configuration file of the SM component.
- Reset all encrypted parameter values in the configuration file to clear text.
-
Restart the Service Manager Server, web application server, Windows Client, Mobility application server, or SRC application server.
A new master key is automatically generated; the parameter values are encrypted again.
Related topics