Question

1
Replies
2038
Views
 Arjan Maus (ArjanM04)
Achmea

Achmea
NL
ArjanM04 Member since 2014 44 posts
Achmea
Posted: December 2, 2016
Last activity: January 4, 2017
Posted: 2 Dec 2016 4:46 EST
Last activity: 4 Jan 2017 9:27 EST
Closed
Solved

SOAP: Requestor authentication failed due to missing credentials although SOAP works fine.

Hi All,


 


We are getting multiple messages in our logging (PEGA 6.2 SP2).


They look like this.


2016-11-30 19:00:41,788 [   WebContainer : 29] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|AE9E791B68EA67119F843945CB3858B45  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials


2016-11-30 19:00:55,059 [   WebContainer : 29] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|AE9E791B68EA67119F843945CB3858B45  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials


2016-11-30 19:00:55,070 [   WebContainer : 22] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|A8532572FC028875AE5980EE1EF141976  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials


This is what I get from my collegues from another department.

Show More

Hi All,

 

We are getting multiple messages in our logging (PEGA 6.2 SP2).

They look like this.

2016-11-30 19:00:41,788 [   WebContainer : 29] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|AE9E791B68EA67119F843945CB3858B45  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials

2016-11-30 19:00:55,059 [   WebContainer : 29] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|AE9E791B68EA67119F843945CB3858B45  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials

2016-11-30 19:00:55,070 [   WebContainer : 22] [  STANDARD] [meaSenIGIWI:01.06.63] (  internal.services.ServiceAPI) ERROR usa10140.unix.corp|145.219.243.242|SOAP|AchmeaSenIGIWISvcSOAP|Services|BatchControleMeldingen|A8532572FC028875AE5980EE1EF141976  - SOAP service [AchmeaSenIGIWISvcSOAP][Services][BatchControleMeldingen] failed:Requestor authentication failed due to missing credentials

This is what I get from my collegues from another department.

“This service is called from a Windows machine, I think this is standard WCF behaviour, at least I have seen it before.

It will first try without credentials and when that fails it will try with credentials, but I am not sure.

Some other collegue googled it and found this:

Read: https://social.msdn.microsoft.com/Forums/en-US/92ad85da-a05c-4e8f-a964-7a5b41af2dd7/all-service-calls-issued-twice-since-the-first-call-always-fails-with-401-unauthorized-access-is?forum=adodotnetdataservices

“This is normal, it's part of the HTTP authentication protocol, used to discover the authentication scheme the server uses, and it cannot be changed.”

When this is correct, then why am I getting al these errors in my PegaRules.log or might I have missed a setting somewhere to suppress these messages?

 

Kund regards,

Arjan Maus

***Updated by Moderator: Marissa to update categories***

Show Less
Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.

Accepted Solution

Posted: 4 years ago
Posted: 2 Dec 2016 5:47 EST
Veera Gangababu Gollapalli (Gangababu)
PEGA
Principal Technical Solutions Engineer
PEG
IN

You could see this kind of errors while testing the services through SOAP UI. Consider SOAP-Service rule uses basic authentication. There are two kind of Pre-Emptive auths named "Global" and "Pre-Emptive"


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.


KIndly refer https://pdn.pega.com/support-articles/redundant-errors-getting-logged-pegaruleslog