Question

3
Replies
567
Views
jpbecker Member since 2005 28 posts
Wells Fargo N.A.
Posted: April 2, 2019
Last activity: April 25, 2019
Closed

Problem access REST web service via Connector rule

Getting the following error when I attempt to access a web service from Pega 8.1 (and previously, 7.3) REST Connector.

When I attempt to Test Connectivity, I'm seeing this error in the Response data ...

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 500 Server Error</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /qcbin/api/authentication/sign-in. Reason:
<pre> Server Error</pre></p><h3>Caused by:</h3><pre>java.io.IOException: Redirect failed
at org.owasp.esapi.reference.DefaultHTTPUtilities.sendRedirect(DefaultHTTPUtilities.java:814) ... etc.

I've run tests of the service in a browser (absent of any Pega software) as well. I determined that using Basic authentication I can call the service, enter an Id and Pw in the authentication pop-up that appears, and I'll get a similar error after I hit enter. If I then access the service a second time in the same window/session by highlighting the URL and hitting Enter, the service will render data for me onscreen. So, I know it's authenticating.

Is it possible the redirect for authentication is the problem here? Is the handoff from service->authentication->service not flowing properly? And if so, is that a problem better addressed on the service provider's end and not on my (the consumer of the service) end?

I'm really trying to isolate the problem and don't think I'm comfortable with whether the issue is "your web service isn't redirecting me back to itself properly after it sends me for authentication" or "I have to write something more complex than the OOTB Pega REST Connector rule uses to test connectivity and make this thing work". Any guidance?

Low-Code App Development Data Integration
Moderation Team has archived post
Share this page LinkedIn