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

Pega Dispute - authorization not getting set in request



Testing of the Verifi activities is showing failure with HTTP 400 code  and missing authorization credential. Debugging has revealed that Pega is not adding the authorization header to the outbound message and Verifi is confirming that "username and password is missing from request header".

Error Messages

[note: DEBUG statements generated with pyInvokeRestConnector logger enabled]

2016-01-22 10:07:24,036 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) INFO   r579878 - HTTP Status code: 400 
2016-01-22 10:07:24,036 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) DEBUG  r579878 - Reading inbound header values from HTTP response 
2016-01-22 10:07:24,036 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) DEBUG  r579878 - Mapping response headers to clipboard 
2016-01-22 10:07:24,037 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) DEBUG  r579878 -  
------------------HTTP RESPONSE CONTENTS------------------ 
Response Headers: 
 x-verifi-call-id: 479690606 Content-Length: 38 Date: Fri, 22 Jan 2016 15:07:23 GMT Connection: close Server:   
Response Message Data: 
Missing authorization credential - 400 
----------------END HTTP RESPONSE CONTENTS---------------- 
2016-01-22 10:07:24,037 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) INFO   r579878 - Reading HTTP response message data 
2016-01-22 10:07:24,037 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) DEBUG  r579878 - Mapping response parameters to clipboard 
2016-01-22 10:07:24,037 [    WebContainer : 4] [ABTHREAD12] [                    ] [        IDM:01.01.01] (ector.Rule_Connect_REST.Action) ERROR  r579878 - the HTTP response code of 400 indicated a client error. The response data may contain a reason. // The service response contained insufficient data for mapping:  The following header(s) were not populated: [location].

Steps to Reproduce

Not applicable.

Root Cause

The test was conducted against an endpoint in conflict with the .VerifiHostHeader defined in InitializeVerifiData data transform.


As with the .VerifiIssuerID and .VerifiSecretKey, the customer is expected to "over-write" the .VerifiHostHeader values when using this data transform.


Published February 13, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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