- CheckMates
- :
- Products
- :
- Quantum
- :
- Remote Access VPN
- :
- How to prevent Untrusted Certificate warning mess...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to prevent Untrusted Certificate warning message in checkpoint capsule connect
Hello,
We have deployed new remote access VPN. Where we implemented vpn Client on Mobiles (Checkpoint Capsule connect) but we are getting certificate warning to Trust and Continue. So How to prevent Untrusted Certificate warning message on mobile Phone (checkpoint capsule connect)
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Team,
We have resolved the issue. For Certificate authetication, there was no issue as we have internal PKI certificate attached in Ipsec VPN. We had issue when creating new site in application that was giving trust message with fingerprint. For which we followed below in Mobile blade portal setting certificate.
we had to put the external certificate but digicert was giving only domain name cert so we had to combine this certificate with intermediate and root Certificate, then we created p12 cert which we uploaded Mobile blade portal setting, then trust warning message, gone. It is not asking while crating site.
Thanks all for your support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Prasaddere
Can you share a screenshot of the message?
My first 2 idea for solution.
1:
Use 3rd party certificate. Choose one that its root is installed in the Trusted Root Certificate store on the device.
(eg.:DigiCert)
2:
Install the Check Point's root and issuer certificate onto the devices.
Akos
\m/_(>_<)_\m/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see what Akos is saying. But, first, screenshot would certainly help. Just blur out any sensitive data, please.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Attached screenshot. we have already deployed certificate from internal CA for Mobile blade portal and different certificate for IPSec Client including all root and subordinate CA. Still getting the attached message for certificate trust first time which we need to avoid.
Same we had issue on Windows laptop but we solution to add fingerprint in Windows registry. which we have added. Issue is only with now on Mobile phone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pretty sure you need to deploy the ICA CA certificate to the mobile device as "trusted."
This either has to be done via MDM or manually.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Certificate from internal CA already added in root CA as well issuing CA. Also server certificate attahed on IPsec client. as seperate CSR generated for mobile against which we got another certificate P12 which we import on mobile portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
To be sure, when you accepted the cert and check the certificate chain, everything looks normal?
If you use MDM only one certificate store exists on the device?
Akos
\m/_(>_<)_\m/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
we have tried with the public certificate but there same trust message is coming first time when creating the site.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it same issue if user deletes/re-creates the site?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it is the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you end up opening TAC case?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can say, yes, IND TAC seems do not have expertise, Our many case going month on month with resolutions only asking for logs. lot of delay in response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I suppose you can always get in touch with your local SE and tell them about it or ask for it to be escalated.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure that:
- The gateway is sending the correct certificate?
- The client is actually set to trust certificates signed by the relevant CA and sub-CA(s)? Please provides screenshots from the mobile client(s) showing the same certificate(s) shown in the above as trusted.
Also what mobile device(s) are you having this issue with?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Team,
We have resolved the issue. For Certificate authetication, there was no issue as we have internal PKI certificate attached in Ipsec VPN. We had issue when creating new site in application that was giving trust message with fingerprint. For which we followed below in Mobile blade portal setting certificate.
we had to put the external certificate but digicert was giving only domain name cert so we had to combine this certificate with intermediate and root Certificate, then we created p12 cert which we uploaded Mobile blade portal setting, then trust warning message, gone. It is not asking while crating site.
Thanks all for your support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great job, thanks for letting us know!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's pretty much standard operating procedure for anything related to certificates.
That means your p12 file should (also) contain root and intermediate CA(s).
