IBM Support

Authorization failed, no Authorization header on command in the Search Service logs.

Question & Answer


Question

Authorization failed, no Authorization header on command in the Search Service logs.

Answer

Contents

Problem

Authorization failed no Authorization header on command in the Search Service logs.? If authentication is enabled in the Search Server service its log files contain entries such as:

<Authentication reqNum='10639' time='8/11/2008 10:51:51 AM' ip='10.10.10.1'>
Auth failed no Authorization header on cmd: /</Authentication>
<TLSrchSrvRequest reqNum='10641' cmd='/' time='8/11/2008 10:51:51 AM' ip='10.10.10.1' userName='domain\username' group='domain\Tealeaf Admin' query='rawxml=1&amp;username=domain%5cusername' />
<Authentication reqNum='10642' time='8/11/2008 10:52:10 AM' ip='10.10.10.1'>
Auth failed no Authorization header on cmd: /STCSearch</Authentication>

Solution

The Search Server authentication protocol is based on HTTP 401 status code responses to unauthenticated requests. Clients that are capable of complying with the protocol know how to make authenticated requests based on the failed-authentication requests.? Thus the sequence of failed request followed by successful request is normal in an authenticated Tealeaf system.

Article Reference
00000425


Applies to version(s):? 6.2;7.0;7.1;7.2

"

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSERNK","label":"Tealeaf Customer Experience"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 December 2018

UID

ibm10776599