- Products
- Learn
- Local User Groups
- Partners
- More
Firewall Uptime, Reimagined
How AIOps Simplifies Operations and Prevents Outages
Introduction to Lakera:
Securing the AI Frontier!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
Hi All,
I have a site running VSX, with one of the VS's running the IPSEC blade only (MAB not enabled) to which endpoint clients connect. As expected the clients gets a certificate warning when you set up the connection for the first time (the client does a HTTPS connection to the gateway as part of setting up the site).
Usually I would resolve this by installing a trusted certificate via the platform portal setting on the gateway properties. Problem is I can't find this setting, not on the VS or on VS0.
How does one resolve this in a VSX environment? All my searching have come up blank, I'm certain I'm missing something very simple.
Thanks,
Ruan
Seems like I've found the solution. Although there is an instance of Multi-Portal daemon running on VS0, it is actually not running. I simply needed to follow the Client's CA signed certificate steps in sk97648
Did you look there?
Hi Jan,
Unfortunately in this environment MAB is not enabled. Good to know it is an option though!
As mentioned in non VSX environments I resolve this by changing out the platform portal certificate, seems this is not an option with VSX then.
And what about the "UserCheck" config more to the top on the same screenshot?
I know for a fact we didn't modify that cert but it shows the same as our MAB cert
That requires IA to be enabled, which is also not enabled in this environment. But you have given me an idea - What I will test is:
Thanks for responding and I will revert with my results!
weird, we don't have IA enabled on that vs
Sorry that was my mistake, it's not related to IA.
I enabled Content Awareness to get access to the UserCheck portal and replaced the certificate with one trusted by the clients. Testing was successful, however once one disable the the relevant blade the certificate reverts back to the one signed by the internal Check Point CA.
I've got a ticket open with TAC now - will update the thread based on the outcome of that.
It seems I’m also facing the same issue. Have you had any luck with TAC? Couldn’t find any SK on this.
Seems like I've found the solution. Although there is an instance of Multi-Portal daemon running on VS0, it is actually not running. I simply needed to follow the Client's CA signed certificate steps in sk97648
If you can change this in the Gaia UI, you can temporarily turn off VSX mode on the Gateway, make the appropriate changes, then turn VSX mode back on.
is it that simple?
are there any side effects of temporarily turning off VSX mode on the Gateway, then re-enabling VSX mode ?
thankyou
Not that I've seen.
I would make certain no one is making changes to VSX objects while VSX mode is off, though.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
12 | |
12 | |
11 | |
7 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 |
Tue 07 Oct 2025 @ 10:00 AM (CEST)
Cloud Architect Series: AI-Powered API Security with CloudGuard WAFThu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Thu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Wed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY