JAVA Toolkit
| home | contact



News Menu

Latest News

iSaSiLk 5.105 released!

03/02/2017

iSaSiLk 5.105 Maintenance release fixes some ECC related issues.

New Versions of our [CP]AdES, IAIK-CMS and IAIK-TSP libraries released!

06/12/2016

New versions of our CMS based toolkits IAIK-CMS, IAIK-TSP and [CP]AdES are now available for download! [CP]AdES now supports CAdES/PAdES LTA level signatures, Content Time Stamp and Archive Time Stamp (v3) Validation according to the most recent ETSI EN 319 122-1 and TS 101 733 standards.

References

Our Clients


Errors

 

Q:

When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_TEMPLATE_INCOMPLETE. What is wrong?

A:

Your specified key template seems to miss some attributes. For example an AES template must have set the attribute valueLen (cka_value_length).

Q:

When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_VALUE_INVALID. What is wrong?

A:

Some PKCS#11 modules restrict changing of certain attributes or setting of certain combinations (e.g. key value and key length). Please consult your module's documentation for further details.

Q:

 When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_TYPE_INVALID. What is wrong?
 

A:

Some PKCS#11 modules do not support certain attributes or modifying certain attributes (e.g. object class or key type). As workaround you can try to set the class and key-type attributes as not present. This may look like this:

     secretEnrcyptionKeyTemplate.getObjectClass().setPresent(false);
     secretEnrcyptionKeyTemplate.getKeyType().setPresent(false);

maybe the driver accepts the key template if you try this.

Q:

Why do I always get an java.lang.UnsatisfiedLinkError: no pkcs11wrapper in java.library.path?

A:

 It seems that you do not have the pkcs11wrapper.dll (or libpkcs11wrapper.so under Unix) in you search path. You can provide such a path directly to the Java™ VM setting the java.library.path system property like:
 

java -Djava.library.path==../bin/<windows|unix>/<platform>/release;. 
   -cp classes;../bin/iaikPkcs11Wrapper.jar demo.pkcs.pkcs11.GetInfo cryptoki.dll

 where ../bin/ <windows|unix >/ <platform >/release is the path where the pkcs11wrapper.dll (or libpkcs11wrapper.so under unix) file is. You can also place the file in the folder for binary files of you Java™ Runtime Environment; e.g. the jre/bin folder. Alternatively, you can also place the file pkcs11wrapper.dll in the system directory of Windows. On Unix systems you can place the libpkcs11wrapper.so in a lib directory of the system.
 


 
print    tip a friend
back to previous page back  |  top to the top of the page