Support Article
REST_ServiceAccessAAA_BasicAuth failed: Rejected by policy
SA-6294
Summary
A REST integration appears to be executed twice, once succsessfully and once with an empty AppID, which causes an error to be thrown. The successful call returns the requested data, so the application is not disrupted, but the error shows up in logs.
Error Messages
Error Call:
Incoming URI=/rest/dbd/dmdsrv/clients/N/00000000000273467560/RBLGVL Headers: Accept=application/json Host=localhost:7002 User-Agent=Apache-HttpClient/UNAVAILABLE (java 1.5) Via=1.1 AQAAAMbVFgM-,1.1 DQAAAHB8sgA- X-Client-IP=<IP Address> ddbus-pm-forwarded-client-ip=<IP Address> ddbus-pm-transaction-id=804700503 Cache-Control=no-transform X-Archived-Client-IP=<IP Address> HTTPMethod=GET
Success Call:
Incoming URI=/rest/dbd/dmdsrv/clients/N/00000000000273467560/RBLGVL Headers: Accept=application/json Host=localhost:7022 User-Agent=Apache-HttpClient/UNAVAILABLE (java 1.5) Authorization=Basic Q1NQUEVHQTp5cGQzbWE4Nw== Via=1.1 AQAAANPfaAE-,1.1 AQAAANTfaAE- X-Client-IP=<IP Address> ddbus-pm-forwarded-client-ip=<IP Address> ddbus-pm-transaction-id=804700503 Cache-Control=no-transform X-Archived-Client-IP=<IP Address> HTTPMethod=GET
Steps to Reproduce
Every time the application runs, error gets logged.
Root Cause
The root cause of this problem is software use/operation error. Without Preemptive Authentication, PRPC Rest client sends Authorization header in return to a 401 response. This results in two requests.
Resolution
The explanation for this behavior is as follows: Enable Preemptive Authentication on the Authentication Profile that Connect-Rest is configured with.
Published February 9, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.