Posted: 21 Mar 2017 9:28 EDT Last activity: 27 Mar 2017 7:51 EDT
Issue facing while sending push notification through pega function
We have a requirement to send the push notification for Apple iOS. For this we are using a function @(PegaMKT-PushNotification:PushNotification).SendNotificationToIOS. So when we are firing our request using this function, there is no issue, errors in tracer and in logs too. But even though we are not able to receive the notifications. After drilling more into the issue we come to know that our request is not able to authorize itself to the certifying authority (CA) certificates installed at our customer premises and hence request is not able to pass through the firewall, which connects to the outside world. So the question over here, is there any way to authorize those certificates using the above mentioned function. Like we use to do it any connector rule by providing trust store under security settings tab.
***Updated by moderator: Lochan to add Categories***
Can you confirm if you are using the Pega Marketing application to send out iOS push notifications?
If yes, then please refer to the Pega Markeinting User Guide Chapter 24: Push Notifications for details on pre-requisites and infrastructure that must be in place before you can send push notifications.
No, we are not using pega marketing push notification functionality to send the push notification.
The architecture of our application is as follows:
We are using Pega-Marketing to run a campaign and then we are saving the data into our database tables and on those tables we have configured the agent to send out the notifications.
In that agent activity we are initiating the pega flow to create a work object.
In the flow, we are referring a activity through utlity shape to send out notifications through the function @(PegaMKT-PushNotification:PushNotification).SendNotificationToIOS.
But issue we are facing here is the pega push request is not able to pass through the client's firewall due to certification authorization issue and this function do not support 2waySSL and proxy. So, is there any local fix or work around to authorize the certificates install at client's firewall level. Like we use do to in Connect-Http rule by providing Truststore under Security Settings?