Basic Authentication HTTP 401 Error on Service Rest

We have created a Service Rest in Pega which can be used for external systems. We added a Authorization Header in request Header. But When we called the service in Pega, Postman, SoapUI, we get a http 401 authentication error.

After when we investigate a solution i found a weblogic configuration that must be done from different support article in community (SA-22512 - Unable to use Authorization on Pega REST API calls). I made a configuration change in weblogic config.xml file and other action in SA-22512. But our problem is continue. Error message is that, "The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11"


Keep up to date on this post and subscribe to comments

September 13, 2019 - 10:42am

Are you using preemptive authentication on the client side? If yes, this looks like a Weblogic specific issue. Weblogic has regular security patches and sometimes that break certain well-established features (sometimes this is intentional and sometimes it is a defect from Oracle). Engage Oracle support would be my recommendation. Post the exact Weblogic path version, I might be able to do some search. 

September 15, 2019 - 12:42pm


We want to use Basic Auth on client side. And we are using Oracle Weblogic, version. I ll investigate problem on weblogic.