Hello good morning,
I'm working with JCAPI v1 and everything is OK.
I have recently updated to JCAPI version 2.2.1 and something very strange occurs. Replacing JCAPI.jar v1 with JCAPI v2 in my project produces the following error in java console in the signing process:
JCAPISignature_sign() - Could not acquire a key container handle for CSP: Microsoft Base Cryptographic Provider v1.0


The strange behaviour ocurrs when testing the same project in other machine. Oh my god!!! Everything is OK. No problems found.

My question is:
Why JCAPI v2 fails in my computer when JACPI v1 works OK???
Any suggestion?


I have checked that working with JCAPI v2 the .DLL is correctly registered in the system.
In my java class I can get certificate aliases form keystore but fails when signing process begins...

Hello good morning again...

I have been testing de JCAPI v2.2.1 in several machines (Windows 7 64 bits) (where JCAPI v1 works OK) and the results are not very encouraging:

For seven machines tested:
Three machines works OK and four machines fails in the signature process.
The error produced is the same as mentioned in previos issue:
"JCAPISignature_sign() - Could not acquire a key container handle for CSP: Microsoft Base Cryptographic Provider v1.0 "


But errors don´t stop here:
When signing with certificate stored in eToken (Aladdin) the six machines fails with the following message:
JCAPISignature_sign() - Could not acquire a key container handle for CSP: eToken Base Cryptographic Provider.

The six machines works OK with Aladdin etoken when using JCAPI v1.

Hi oria,

Thank you for the input.
This is not acceptable. Version 1 and 2 must be identical when it comes to both enryption and signing. Apparently this is not the case. Sorry for that. We'll investigate it immediately.

First we need to reproduce the problems in our test lab. We'll start now, but it would help us a lot along the way if you could provide the following info:
1. Which version of JCAPI v1 are you using?
2. Have you only tried with JCAPI v2.2.1 or does it work with previous v2 releases?
3. What operating systems and machine architectures (32-, 64-bits) are working/failing?

Thanks.

Regards,
Tommy

Hi again oria,

We have now tested v2.2.1 towards all supported platforms to find your reported problems. Unfortunately, we have not been able to reproduce them. I have attached two small isolated test programs which you can use to reproduce it yourself. They will cover both your eToken and Base Provider problems you had. If they can't be reproduced, then please modify them to trig the problems you have so we can fix them.

Thanks.

Regards,
Tommy

First of all thank you very much for your help.

Strange things still occurs but now the JCAPI v2.2.1 is working OK.
The bad thing is that I dont know want what I've done to achieve it.

When updating from JCAPI v1 to JCAPI v2 I had to enclose the signing process between doPrivilege() block to achive application works....
but... now when I remove doPrivilege() block I am not able to reproduce the error again (no cache exists).....STRANGE!!!!
I have been testing it for an huour but now I am not able to reproduce it...!!!

Now it works but...what will happen in the future?

I'll tell you if I find this X expedient....

thank you very much!!!

Hi oria,

That's ok. Just glad it works out for you at last.
Unfortunately we can't figure out the reason for this weird behavior.
We have not received a single issue from any customer yet (except for you) due to this upgrade, and some of them are using JCAPI on 24/7 VISA/Mastercard servers.

If you encounter any other strange issues when using JCAPI, then please tell us as soon as possible. Thanks.

Take care.

Regards,
Tommy