Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Redundant error's getting logged to PegaRules.log

SA-4642

Summary



The below Error message is getting logged to PegaRules.log, for every WebService call (irrespective of successive/incorrect authentication).

SOAP service [ServicePackage][Services][WebService] failed:Requestor authentication failed due to missing credentials


Error Messages




2014-10-28 00:08:02,257 [fault (self-tuning)'] [ STANDARD] [ KPNChannel:01.01.07] ( internal.services.ServiceAPI) ERROR sz0999.app.gen.local|10.68.189.219|SOAP|KPNChannelAOS|Services|AOSDetermination|AB8EB8415E72A26FC6D627FAD76D9E4D5 - SOAP service [KPNChannelAOS][Services][AOSDetermination] failed:Requestor authentication failed due to missing credentials


Steps to Reproduce



NA

Root Cause



The root cause of this problem is in a third-party product integrated with PRPC. Credentials are not coming as part of first request. Request was send with authorization type 
Global HTTP Settings.


Resolution



While using SoapUI, it is suggested to use Preemptive.


Preemptive means “HttpClient will send the basic authentication response even before the server gives an unauthorized response in certain situations, thus reducing the overhead of making the connection”.

Global HTTP Setting means “HttpClient will send the request without credentials then server throws exception, if authentication is enabled request resends with credentials again for same request.”

For external system it will be configurable to send the credential in the first request itself. Example in PRPC : Authentication Profile have preemptive check box to send the credential in first request itself.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us