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)`

Codar1.80

Configure secure connections for client browsers

The Codar Console is configured to require https (http over a secure connection) for client browsers. For a secure connection to be established, a certificate must first be installed on theCodar server.

A self-signed certificate is created and configured whenCodar is installed and is configured with the fully-qualified domain name that was entered during the installation. This self-signed certificate is used when https browser requests are issued for the Codar Console and expires 120 days after Codar is installed.

When client browsers connect to the Codar Console in this default configuration, the client browser will usually issue warnings that the certificate was not issued by a trusted authority. The end user can choose to continue to the web site or close the browser.

Although the self-signed certificate can be used in production, HPE recommends that you replace this certificate by configuring a trusted third-party Certificate Authority-signed or subordinate Certificate Authority-signed certificate (see Configure Codar to use trusted Certificate Authority-Signed or subordinate Certificate Authority-Signed certificate) or by configuring an internal Certificate Authority-signed certificate (see Configure Codar to use internal Certificate Authority-Signed certificate). Or, you can replace this certificate by configuring a self-signed certificate (see Configure Codar to use self-signed certificate).

Note:Certificate chains require additional configuration and general information about importing a chain of certificates is provided in this section. However, you should consult your security expert for more detailed information when using certificate chains in your environment. Wildcard certificates do not require special configuration.

Note If you have configured Codar to be compliant with FIPS 140-2, you must substitute the Codar server truststore (for example, codar_server_truststore.p12) for the Java truststore (cacerts) and substitute the Codar server truststore password for the Java truststore password. See Create new keystore and truststore for secure communication for more information about the Codar server truststore and password.

Send Help Center feedback