- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Call For Papers
Your Expertise. Our Stage
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
Hi All,
I've tried mobile access sslvpn certificate replace but there is a error that "the password you entered is incorrect".
How I reset this password or how can I solve this problem ?
Thank you.
Hi all,
I just ran into the exact same issue, even though I was pretty sure the password was correct (unless my PC's copy-and-paste function was broken). After some testing, seemed that the .pfx (renamed to .p12) was exported from a Windows machine using AES256-SHA256 to encrypt the export-password. Re-exporting the certificate with a 3DES-SHA1 encryption of the export-password did wonders.
Just adding my two cents here. If it saves anybody some time, it was worth the while.
Please explain which certificate you are replacing and how. If the password is for p12 certificate file, you cannot "reset" it.
Thanx for reply. Yes, p12 certificate file. How can I renew it without password reset ?
You need to find out the password or create another p12 file with a password you know
Thank you.
Hi Val,
I thought this was the case too, because the password is a part of the certificate right?
However, my colleague showed me you can change the password from the checkpoint mobile client.
If you select your p12 certificate, then click on the certificate icon beneath browse, this will give you the option to change password on the new window that appears.
Can you explain how this works? I thought the password was part of the certificate itself, in order to change the password, you needed to change the certiifcate? I though a new enrollment would be needed.
Pls help to explain.
Thanks.
Hi all,
I just ran into the exact same issue, even though I was pretty sure the password was correct (unless my PC's copy-and-paste function was broken). After some testing, seemed that the .pfx (renamed to .p12) was exported from a Windows machine using AES256-SHA256 to encrypt the export-password. Re-exporting the certificate with a 3DES-SHA1 encryption of the export-password did wonders.
Just adding my two cents here. If it saves anybody some time, it was worth the while.
Thank you for that! I've already spent some time debugging though. 😄
I've generated a key pair with Keystore Explorer. For every PKCS#12 export I got the message ""the password you entered is incorrect". I've changed the Explorer's settings from "strong" PKCS#12 encryption to "legacy" encryption and was able to import the cert on the gateway. R81.10
How can I change the Explorer's settings from "strong" PKCS#12 encryption to "legacy" encryption ? Do you mean file explorer? Or maybe Edge browser?
You make the choice between "Strong" and "Legacy" PKCS#12 the moment you export the certificate from your windows system.
Consider the following scenario :
You obtain a certificate for use with your SSL VPN on the Check Point, either from one of the publicly trusted issuers (like DigiCert, VeriSign, GlobalSign, etc...) or from some other corporate/enterprise/internal PKI.
You import it into the Check Point, but are confronted with the 'the password you entered is incorrect' error.
As a solution, you can import this certificate into the certificate store of a Windows machine, and export it out again (making sure to export the private key as well) in a PKCS#12 format. At this point you can choose what type of encryption is used for the private key and the password used for this encryption. This is where you select 'legacy' encryption. (°)
Normally, this exported certificate can now be imported into the Check Point.
Importing and exporting certificates is done through the certificate manager (mmc plug-in 'Certificates'), and has no bearing whatsoever with Windows explorer and/or Edge browser.
(°) In my up to date Windows 11 machine, I see that these encryption options have been changed/renamed to 'TripleDES-SHA1' or 'AES256-SHA256'.
I exported from windows to TripleDES-SHA1 and then the import to checkpoint was successful
Thx
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 76 | |
| 29 | |
| 14 | |
| 13 | |
| 13 | |
| 12 | |
| 10 | |
| 9 | |
| 8 | |
| 8 |
Tue 21 Apr 2026 @ 05:00 PM (IDT)
AI Security Masters E7: How CPR Broke ChatGPT's Isolation and What It Means for YouTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 21 Apr 2026 @ 05:00 PM (IDT)
AI Security Masters E7: How CPR Broke ChatGPT's Isolation and What It Means for YouTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY