SA-13972

Summary

In AES EE 7.1, the AES Manager portal allows you to manage the SOAP Authentication using the DASS. However, the value is never used by the SOAP connector.

The scripts that set up the SOAP request collect the Authentication credentials, but the Connect SOAP rules require the use of Authentication Profile, AESRemoteUser. There is no way to edit this to change the behavior without building changes on top of the AES application.

Note: The problem described here (and reported in September 2015) for AES EE 7.1 does not exist for AES 7.2 on Pega 7.2.

Error Messages

HTTP Error 401 - Unauthorized: Access is denied due to invalid credentials.

Steps to Reproduce

1. On AES EE 7.1, set up SOAP authentication, keeping the current setting Authentication Profile specified as AESRemoteUser..
2. If you edit the Authentication Profile to anything other than AESRemoteUser, you get the 401 error.

Root Cause

A defect or configuration issue in the operating environment that has been resolved in AES 7.2 on Pega 7.2
The remote operator name is hard coded instead of being read from a property whose value is set by the Data Admin System Setting (DASS).

AES 7.2 Pega 7.2 integration supports both messages from monitored node to AES and AES messages to monitored node.

Resolution

Apply HFix-23400 if you need to run AES EE 7.1.
Best Practice: Upgrade or update to AES 7.2 on Pega 7.2.

Related Content
https://pdn.pega.com/documents/autonomic-event-services-aes-installation-and-upgrade-guide-72
https://pdn.pega.com/documents/aes-node-configuration-guide-72