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 Management2017.11

Integrate > Service Manager integration methods and tools > Web Services > RESTful API > Consuming Service Manager RESTful API > Implementing TSO for custom RESTful clients

Implementing TSO for custom RESTful clients

The Service Management RESTful framework supports the Trusted Sign-On (TSO) authentication method.

Do the following to use TSO authentication for custom RESTful clients:

Enable two-way SSL between the web service client and the Service Management server, so that they trust each other.
Create a dedicated integration account for the web service client to log in to the Service Management server.
Add a “Pragma: TrustedSignOn” header in the http request, which will make the Service Management server aware that this is a TSO request and hence skip password checking. The Service Management server checks only the integration user to see whether it exists in the Service Management database.

Note When the custom HTTP header “Pragma: TrustedSignOn” is present, the SM Server skips password checking because the presence of the header indicates the client has been authenticated by an external source such as Active Directory, Kerberos, or a custom Single Sign-On third-party server. This document assumes that you have taken the necessary steps to ensure that your custom RESTful client has been successfully pre-authenticated before any transactions with the Service Manager RESTful API begin.

Send Help Center feedback