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 |
|
- Install and configure the standalone IdM service
- Task 1: Deploy IdM on a web application server
- Task 2: Configure SSL in the IdM web application server
- Task 3: Create an IdM client trust store
- Task 4: Configure SAML SSO
- Task 5: Configure a tenant and specify the ADFS metadata URL
- Task 6: Configure the IdM service for LW-SSO compatibility
- Task 7: Specify an IdM token signing key
- Task 8: Specify an IdM user account for Service Manager
- Task 9: Replace JRE policy files for the IdM server
- Task 10: Configure the SAML keystore in IdM
- Task 11: Import the IdP public key into the IdM SAML keystore
- Task 12: Encrypt IdM passwords and keys
- Task 13: Create an empty database for IdM
- Task 14: Configure database connection in the IdM service
- Task 15: Download the IdM metadata
- Task 16: Create a trust relationship with ADFS
- Task 17: Adjust the max authentication age setting in the IdM service
- Configure SAML authentication by using the IdM admin console
Task 12: Encrypt IdM passwords and keys
Note This is an optional task.
In this task, you will run the IdM encryption tool to encrypt all IdM passwords and keys. This task is optional but highly recommended for the best security in production environments.
To do this, follow these steps:
-
Update the second column of the following table with the passwords and keys that you have configured for IdM.
Location Password/Key Description <idm-service>\WEB-INF\classes\integrationusers.properties idmTransportUser=xxxxxx
This is the IdM password that Service Manager uses to access the IdM service.
-
XXXXXX is a string that defines the password and other properties of the IdM user account. For example:
idmTransportUser=1Qaz2wsx3edc,ROLE_ADMIN,PERM_IMPERSONATE,enabled
- You must encrypt the entire string on the right side of the equals sign.
<idm-service>\WEB-INF\spring\applicationContext.properties idm.encryptedSigningKey=xxxxxx
This is the signing key used to sign IdM tokens.
<idm-service>\WEB-INF\spring\applicationContext.properties idm.persistence.connection.password = xxxxxx
This is the password of the IdM database connection account.
<idm-service>\WEB-INF\spring\applicationContext.properties idm.saml.keystore.password=xxxxxx
idm.saml.keystore.defaultKey.name=xxxxxx
idm.saml.keystore.defaultKey.password=xxxxxx
This is the password, default key name and passwords of the IdM SAML keystore file: <idm-service>\WEB-INF\classes\security\samlKeystore.jks.
If you use the out-of-box keystore file, these parameter values are already encrypted and you must not change them.
-
-
Unzip <idm package>.zip, find the "dataprotection-passwordtool-1.0.3-standalone.jar" file and copy it to the <idm-service>/WEB-INF/classes/security directory.
-
Edit the <idm-service>/WEB-INF/classes/security/key-configuration.properties file. Comment out other profile such as strong128, and then uncomment the following legacy items:
enckeytype.local.profile=legacyCSA enckeytype.local.jce=SunJCE enckeytype.local.passphrase.name=local legacy passphrase enckeytype.local.passphrase.provider=file enckeytype.local.passphrase.file=key-local-legacy-passphrase.txt enckeytype.local.passphrase.deleteFile=false enckeytype.network.profile=legacyCSA enckeytype.network.jce=SunJCE enckeytype.network.passphrase.name=network legacy passphrase enckeytype.network.passphrase.provider=file enckeytype.network.passphrase.file=key-network-legacy-passphrase.txt enckeytype.network.passphrase.deleteFile=false
-
For each parameter value in the previous table, run the following command:
java -jar dataprotection-passwordtool-1.0.3-standalone.jar --encrypt –conf . local <mypassword>
Example:
-
Copy the encrypted value back to the IdM configuration file to overwrite the original parameter value by using the following format:
Parameter=ENC(encrypted value)
Here are examples:
idmTransportUser=ENC(gJL7uUNgKWMvi7YuZPaXjTwATek8gkEFbaJoDdk8ANqeLbnjumbTPQQXkOgrP0w1A322u4gucc+Q0CMjq+2G3BaeOGymyvYhgh1rNg==)
idm.encryptedSigningKey=ENC(gJL7uUNgKWMvi7YuZPaXjTwATek8gkEFbaJoDdk8ANqeLbnjumbTPQQXkOgrP0w1A322u4gucc+Q0CMjq+2G3BaeOGymyvYhgh1rNg==)