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 |
|
- Configure CSA
- Stop CSA
- Update applicationContext.xml to be FIPS 140-2 Compliant
- Configure Properties in the Java Security File
- Create a CSA Encryption Keystore
- Create a New Keystore and Truststore for Secure Communication
- Re-Encrypt CSA Passwords
- Configure CSA Properties
- Configure the Marketplace Portal for FIPS 140-2 Compliance
- Configure the Identity Management Component
- Disable HP Single Sign-On
- Configure CSA to Use SAML
- Start CSA
- Update the Process Engine Password
- Test Secure Connections
Configure Properties in the Java Security File
Edit the Java security file for the JRE to add additional security providers and
configure properties for FIPS 140-2 compliance.
Open the
<csa_jre>\lib\security\java.security
file in an editor (where <csa_jre>
is the directory in which the JRE that is used by CSA is installed.) and
do the following:
-
For every provider listed (in the format
security.provider.<nn>=<provider_name>
), increment the preference order number (<nn>
) by one. For example, change a provider entry from :security.provider.1=sun.security.provider.Sun
to
security.provider.2=sun.security.provider.Sun
. -
Add a new default provider (RSA JCE). Add the following provider to the top of the provider list:
security.provider.1=com.rsa.jsafe.provider.JsafeJCE
-
Update the SunJSSE provider to use packages that are compliant with FIPS 140-2.
For example, change the following entry from:
security.provider.<nn>=com.sun.net.ssl.internal.ssl.Provider
to
security.provider.<nn>=com.sun.net.ssl.internal.ssl.Provider JsafeJCE
-
Set the default keystore type to PKCS #12. Edit or add the following entry:
keystore.type=PKCS12
-
Add the following entry to ensure RSA BSAFE is used in FIPS 140-2 compliant mode:
com.rsa.cryptoj.fips140initialmode=FIPS140_SSL_MODE
-
Set the default random number generation algorithm to HMAC DRBG with 128-bit security strength:
com.rsa.crypto.default.random = HMACDRBG128
- Exit and save the
java.security
file.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to clouddocs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: