Henrik Troeng (bisse766)
Swedish Unemployment Funds
Platform and Operations
Swedish Unemployment Funds
bisse766 Member since 2014 5 posts
Swedish Unemployment Funds
Posted: March 23, 2016
Last activity: April 8, 2016
Posted: 23 Mar 2016 8:54 EDT
Last activity: 8 Apr 2016 11:02 EDT

Pega 7.2 Web service with authentication - possible to use non-preemptive authentication?


I have set up pega web services that is going to be consumed from Biztalk 2013. I use basic authentication with a custom authentication service, using basic authentication for signon. The services work, and the authentication works when I use preemptive authentication (sending username / pasword in the header) in the request.

Apparently Biztalk don't support this out of the box, it sounds like they are expecting a 401 in return and then they will provide the auth info in the header in the second request.

What I have understand it is that there is an ER logged but has not been implemented in Pega:

PRPC services protected by Basic authentication doesn’t follow the HTTP spec (see, which mandates application to send WWW-Authenticate header along with 401 status code. Wrong behavior of PRPC service forces the service clients to use preemptive authentication.

Has anyone here had similar problems? Did you solve it (on the Pega-side of the integration) ?



Pega Customer Service Data Integration Security
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.