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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.52

Administer > System security > FIPS mode > Configuring LW-SSO in FIPS mode > Configure LW-SSO in the Server for FIPS mode

Configure LW-SSO in the Server for FIPS mode

Applies to User Roles:

System Administrator

Enabling LW-SSO in the Service Manager (SM) Server enables web service integrations from other HPE products to bypass Service Manager authentication if the product user is already authenticated and a proper token is used; enabling LW-SSO in both the Service Manager Server and Web Tier enables users to bypass the login prompts when launching the Service Manager web client from other HPE applications.

Caution To use LW-SSO, your Service Manager Web Tier and Server must be deployed in the same domain; therefore you should use the same domain name for the Web Tier and Server. If you fail to do so, users who log in from another application to the web tier can log in but may be forcibly logged out after a while.

Prerequisite:

Before you proceed, make sure you have enabled FIPS mode on the Service Manager Server side. For detailed instructions, see Configure FIPS mode in the Server.

To configure LW-SSO in the Service Manager server for FIPS mode, follow these steps:

Go to the <Service Manager server installation path>/RUN folder, and open lwssofmconf.xml in a text editor.
Make sure that the enableLWSSOFramework attribute is set to true (default).

Locate the following section.

<lwssoValidation>
            <domain>example.com</domain>
            <crypto cipherType="symmetricBlockCipher"
              engineName="AES" paddingModeName="CBC" keySize="256"
              encodingMode="Base64Url"
              initString="This is a shared secret passphrase"/>
            <!-- When Service Manager is running in FIPS mode, the crypto configuration above needs to be replaced with the configuration below. The initString value must be 32 characters long and contain no spaces.  -->
            <!--
            <crypto cryptoSource="jce" cipherType="symmetricBlockCipher"
              engineName="AES" paddingModeName="CBC" keySize="256"
              pbeDigestAlgorithm="SHA1" encodingMode="Base64Url"
              jcePbeAlgorithmName="AES" jcePbeMacAlgorithmName="AES"
              macType="hmac"
              macAlgorithmName="SHA1" directKeyEncoded="true" directKeyEncoding="Base64Url"
              algorithmPaddingName="PKCS5Padding"
              pbeCount="20" macKeySize="256" macPbeCount="20"
              initString="rqa9mkdmfkvdvienfj4usldo9205mvid">
            </crypto>
            --> 
</lwssoValidation>

Update this section by doing the following:

Comment out the ordinary crypoto configuration part.
Uncomment the FIPS mode crypto configuration part.
Configure the domain of the host.
Update the default initString value to your own value, if needed.

Caution The initString value is shared among all parties that participate in LW-SSO. In FIPs mode, this value must be 32 characters long and contain no spaces; otherwise LW-SSO will not work in FIPS mode.

The following is an example:

<lwssoValidation>
    <domain>myhostdomain.com</domain>
     <!--
           <crypto cipherType="symmetricBlockCipher"
              engineName="AES" paddingModeName="CBC" keySize="256"
              encodingMode="Base64Url"
              initString="This is a shared secret passphrase"/>
      -->
      <!-- When Service Manager is running in FIPS mode, the crypto configuration above needs to be replaced with the configuration below.
      The initString value must be 32 characters long and contain no spaces. --> 
  
            <crypto cryptoSource="jce" cipherType="symmetricBlockCipher"
              engineName="AES" paddingModeName="CBC" keySize="256"
              pbeDigestAlgorithm="SHA1" encodingMode="Base64Url"
              jcePbeAlgorithmName="AES" jcePbeMacAlgorithmName="AES"
              macType="hmac"
              macAlgorithmName="SHA1" directKeyEncoded="true" directKeyEncoding="Base64Url"
              algorithmPaddingName="PKCS5Padding"
              pbeCount="20" macKeySize="256" macPbeCount="20"
              initString="1qaz2wsxfkvdvienfj4usldo9205mvid">
            </crypto>
</lwssoValidation>

Note Here, myhostdomain.com refers to the domain of the SM Server host.

Note

You are not recommended to modify the paddingModeName, keySize, encodingMode, engineName, and cipherType attributes. If you need to modify them, be careful to ensure security and make sure that they are same with the LW-SSO settings of the other HPE product that you want to integrate with Service Manager.
Do not change the other configurations, such as the content in tag <restURLs>, and the attribute of tag <service>.

Send Help Center feedback