コミュニティアチーブメントバーを展開する。

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Mark Solution

この会話は、活動がないためロックされています。新しい投稿を作成してください。

解決済み

AEP to Pega Customer Decision Hub (OOTB Connector)

Avatar

Level 2

Hi All, 

 

Looking for your support on the AEP to Pega Customer Decision Hub connector. 
We have received the credentials(Client secret, Client ID ect) to connect with the Pega CDH and AEP is able to connect with the Pega destination when we add the credentials. 


We have activated certain segments to the Pega CDH destination but we are getting the error "Authentication error reported while pushing events to the destination. Please check authentication credentials and try again"

 

Has anyone faced this issue before? or was able to successfully establish a connection between AEP and Pega CDH?

Your response will be very helpful!

Thanks 

Ankita

1 受け入れられたソリューション

Avatar

正解者
Level 2

We were able to resolve this issue , by getting Pega on a secured https protocals and whitelisting the statis ips from Adobe. 
This resolved the issue for us . 

Thanks 

元の投稿で解決策を見る

3 返信

Avatar

Level 4

We had similar issues and in our case they were caused by strict IP whitelisting on the Pega end. After finding out all IPs that Adobe is using for this connector, whitelisting them in Pega, it is now working fine.

Check with Pega team if such IP blocking exists in your case.

Avatar

Level 2

Hi 
Thankyou for your response. 
Adobe documentation does not provide any details on ip whitelisting for Pega. But for the time being we have shared the IP allow list present in adobe docs HTTP API streaming destination. 

Do you have the list of Adobe IPs or documentation that we can use to get the all the ips ?

Thanks in advance.

Avatar

正解者
Level 2

We were able to resolve this issue , by getting Pega on a secured https protocals and whitelisting the statis ips from Adobe. 
This resolved the issue for us . 

Thanks