AEP to Pega Customer Decision Hub (OOTB Connector) | Community
Skip to main content
A
Ankita05
Level 2
March 24, 2023
Solved

AEP to Pega Customer Decision Hub (OOTB Connector)

  • March 24, 2023
  • 2 replies
  • 1321 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ankita05

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 

2 replies

M
mdonke
Level 4
March 24, 2023

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.

    A
    Ankita05Author
    Level 2
    March 24, 2023

    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.

    A
    Ankita05AuthorAccepted solution
    Level 2
    March 30, 2023

    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 

    Terms & ConditionsAccessibility statement

    Loading footer...