Hi Tommy,

It's been a long time since we talked. How are you ?

I post this message because I have a problem when I use JCAPI with a ypsID SmartCard S1 from Sagem.

The problem occurs while signing a document using BouncyCastle with JCAPI provider, I get the following error message :

java.io.IOException: error creating signature.
java.security.SignatureException: Exception raised in JCAPI.DLL:
JCAPISignature_sign() - Could not sign the hash.
Error code: 0xea
at
org.bouncycastle.cms.CMSSignedDataStreamGenerator$CmsSignedDataOutputStream.close(Unknown Source)

This happens on a computer with Windows Vista and I would like to know if you know something about this error, if it has already occurs with someone else, and what it is meaning.

This information could tell me if the problem commes from my applet or from JCAPI, in the second case I would make further tests such as importing PKCS11 driver of the token or testing if JCAPI v2 would make a better work.

Thank you in advance.

Regards,
Igor.

Hi Tommy,

Luckily, I've found an other version of the same SmartCard (and token) and I've made some tests on my personnal computer at home which is on Windows XP and it worked properly.

So the problem doesn't come from JCAPI : the service that permits the communication between the token and Windows was badly installed on the Vista computer because of a lack of administrator's rights.

Moreover I've made some researchs on the error code 0xEA and it's a code that means "more data available" which confirm my first hypothesis of a bad communication between the two sides.

So I think we could say that this issue is RESOLVED.

See you.

Regards,
Igor

Hi Igor,

Sorry for the delay of my answer. For some strange reason the system didn't notify me about your new post. I did reboot it and now the notifications work. Strange indeed.

Anyway, everything is fine here even though there is much work with JCAPI v2.0. All those unforeseen details to take care of Thanks for asking. Hope everything goes well with your business too.

I'm glad to see that your problem was solved. Just let us know if any other issues arise.

Regards,
Tommy