Question
Verizon Data Services
IN
Last activity: 12 Oct 2018 14:34 EDT
Getting "Transport error : 401 Error: Unauthorized" while configuring AES
Hi Team,
I am facing the below error while configuring AES in my dev environment . I have given the URL of AES system in Predictive Diagnostic Cloud(PDC) , and while doing the test connectivity I am getting an error.
com.pega.pegarules.pub.services.RemoteApplicationException: Soap service failed.
Please help.
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
IN
Hello,
Will the below support article help?
https://community.pega.com/support/support-articles/issue-connect-soap-execution
Thanks,
Gowrishankar
Verizon Data Services
IN
Hi Shankar,
I have gone through the article and found that it's not useful in my context.
Thanks.
Pegasystems Inc.
US
You are getting authentication failures - how did you configure the credentials for the connection from one system to the other system?
Verizon Data Services
IN
The service is using basic authentication and hence I created an authentication profile and given the details of an operator available in AES system in the connect soap rule. The problem is , when I remove the authentication from service-soap and connect-soap then also I get the error.
Pegasystems Inc.
US
By "The service is using basic authentication" do you mean that the Service Package is configured for Basic Authentication?
What do you mean by "remove the authentication from service-soap?"
I do not not think you need to configure any specific authentication for the Service itself if you are using the credentials of a user that has access to the system.
Verizon Data Services
IN
Connect soap will hit the service package which has basic authentication . I disabled the authentication from service package .
Pegasystems Inc.
US
What is the URL that you provided on the "System / Settings / PDC" landing page?
On your AES server, did you customize the AES service package to require authentication? By default AES / PDC services are unauthenticated. Unless you made a change on the AES server side, don't touch the user/password fields on the landing page.
Save and update the "PDC" URL setting, then go to logging levels and enable debug on httpclient.wire.content and httpclient.wire.body. We want to see the messages flowing between your system and AES. The "management daemon" thread on your system is supposed to send AES a HLTH0001 message very two minutes. Wait and see what happens to it ...
Verizon Data Services
IN