- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Announcing Quantum R82.10!
Learn MoreOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
We have an on premise PDP which is pushing/ sharing the identities to a Azure Cloudguard using the public IP address of the gateway (also restricted on the source public IP address). This is quiet helpfull as this is Out of Band management and not crossing any Azure Load Balancer. This is working and the Azure Cloudguard PEP has all the user information. The Azure Cloudguard also tries to retrieve the identities by connecting to the same IP address but the IP address from the PDP is not reachable.
We know that sk60701 explains how to change the IP address of the identity sharing gateways but we dont want to do that, hence it is already working, but the PDP "complains" that is lost its connection to the Azure Cloudguard. Again the connection from the PDP to Azure firewalls PEP are working fine and the gateways have the identities but the opposite direction is not able to establish the connection.
The only thing we try to avoid is that the PDP is reporting errors but in fact is working fine and the Azure cloudguard does not need to share its identities, but only receive from the PDP.
Is there a way to control and only enforce PDP push identities from the PDP to PEP and not to perform any PDP pull from the PEP in Azure?
Perhaps there is some neat feature called smartpush from PDP to PEP and not to perform any smartpulls, asking for a friend 🙂
You could try changing publish_method on the gateway from smart_pull to push (GuiDBedit: Table -> Network Objects -> network_objects -> FirewallName -> identity_aware_blade -> publish_method), save and install policy.
You may need to reset IA tables after that change (see sk170516 for the commands) and relearn all identities (maintenance window required).
You can check afterwards with "pdp connection pep -e" on PDP. There is column named "Publish" which should show "Smart-Pull" before and "Push" after the change I mentioned.
Personally, Im not aware of such a feature, maybe TAC would be able to confirm for you.
Best regards,
Andy
You could try changing publish_method on the gateway from smart_pull to push (GuiDBedit: Table -> Network Objects -> network_objects -> FirewallName -> identity_aware_blade -> publish_method), save and install policy.
You may need to reset IA tables after that change (see sk170516 for the commands) and relearn all identities (maintenance window required).
You can check afterwards with "pdp connection pep -e" on PDP. There is column named "Publish" which should show "Smart-Pull" before and "Push" after the change I mentioned.
thanks Tobias that worked for me no need to do any restart of PDPD or relearning it just works out of the box, just needed to allow port 15015 towards the gateways that is it.
Thanks for letting us know, glad it worked.
Andy
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 16 | |
| 12 | |
| 8 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY