[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1508
  • Last Modified:

Imported Certificate Problems - signing data with your private exchange key

Hi,

We have a website that requires certificates.  We have imported the certificate onto our system (windows 2000 SP4) at a client site (not within our domain).  When the user gets in to use the application, the application works but they receive continuous messages (depending on what we do within the application), with a window titled Private Key Container and is an informational window stating 'signing data with your private exchange key' but does not ask for a password.  We did have two certificates for the same site on the system, but have since removed one eventhough it did ask us which one we wanted to use for the site.

We have reviewed security settings for the internet, SSL on the web server but have not found the culprit.  We still have not tested it on another system at the client site, that is happening later this week.

If anyone understands why we are receiveing this informational window we would greatly appreciate the feedback.

Thanks

0
spinewr
Asked:
spinewr
  • 2
  • 2
1 Solution
 
msiceCommented:
You need to make sure the cert is configured for the url you are using.
0
 
spinewrAuthor Commented:
Thanks for the info.  
The cert is an actual working one for the application.  It was exported and emailed to the client.  The client imported it and here we are with this problem.  I wish I was more familiar with configuring certs for urls, but I am not.  Is there a way to check and make sure it is configured for the url?  Or is there a way to check to see if it is corrupt?

Both of these answers could narrow down the hunt!

Thanks,
spinewr
0
 
msiceCommented:
When you or verisign build the certificate you have to enter the url (or give it to them) of the site exactly so if its http://xxx.xxxxx.com that’s what you have to enter.
0
 
spinewrAuthor Commented:
Yes, after checking this out it was done correctly.  Can anyone answer my other question?  How can you tell you have a corrupt cert.  The problem may just be on one pc and not all over.  The problem is I need to have the certificate reissued or export the certificate onto the next box, but I can't tell if the certificate I am using is ok or not.  I am also a long way from home so I can't test this exported cert on a box I know normally works.

Any help would be great!
0
 
Dave_DietzCommented:
This is default behavior for a Personal Certificate that has been set to use Medium Security when imported.  If it was set to High you would be prompted for a password every time the certificate was accessed.

The URL has nothing to do with it - that requirement is for SSL Cewrtificates, not for Personal (Client) Certificates. (Additionally, if you include the http:// in the common name of the certificate it will not function properly since that is not part of the Host field in a standard HTTP/1.1 compliant request)

If your certificate was corrupt you would likely not even get to the point of being told it was being used.  To make sure you could try sending an encrypted or digitally signed message to yourself.  If you can read it properly your certificate is fine.

Hope this helps.

Dave Dietz

0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now