I am in the process of moving an IIS based Wildcard SSL certificate to a Domino Keyring file. I saw an article at http://www.turtleweb.com/t
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
When I exported the pfx file, I used the password. I was able to import the pfx file into the Domino KEY DB file as PKCS. I saved this with the name key.p12 . Later when I created a key ring file and try to import this PKCS file (key.p12), I am getting the error
I also tried with OpenSSL, but no luck.
You may need to clear out an old cert:
https://knowledge.verisign
Can also try following the processes laid out here:
http://rafibytes.com/help/
Let me know how it goes.
Business Accounts
Answer for Membership
by: ParanormasticPosted on 2009-04-30 at 13:40:38ID: 24274213
When you exported the pfx file, did you keep the strong protection on, requiring you to assign a password? Or did you remove that so no password? There should be a password if you didn't do that - some programs will behave oddly if you don't. Also, try having a password that is at least 8 characters long - although it shouldn't matter, I've seen issues with less than 4 or 8 characters in some rare cases. Blank passwords (as opposed to no password requirement) messes with a number of programs.
The other thing you can do is to try converting the pfx file to PEM format - some programs work better with a PEM formatted cert. You can download OpenSSL from http://gnuwin32.sourceforg
Here's a script to run - you can pass the variables when you run the .bat file or you can replace them ahead of time.
: %1 = filename (will be used for PFX and PEM filenames)
: %2 = password for input PFX file
: %3 = password for output PEM file
c:\openssl\bin\openssl.exe
pause