Replies: 5 comments 5 replies
-
Does it show any exception in the log file of EJBCA? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
@primetomas thanks!
for
not yet, because previously it does not help and it seems to be a matter of HSM authentication itself. but I will try this. once tested, I will report here.
these do not work either. (I tried
anyway to confirm your hypothesis? FYI, Another CA server product which I tested concurrently, can create key on HSM where ejbca fails to create. I think configuration of underlying PKCS11 library is exactly same. regards, |
Beta Was this translation helpful? Give feedback.
-
@primetomas I tried
but I find pkcs11 error when generateKey fails with full stacktrace is here:
hope this helps regards, |
Beta Was this translation helpful? Give feedback.
-
Long time no see, the following hack solved the problem by avoiding Here we want to create an object for ejbca using a token on PS3 called ThalesHSMSlot.
This will ensure that For this method to work, a new cryptotoken must be created before creating the HSM's token, the third method allows the creation of a new cryptotoken each time without increasing the number of cryptotokens. maybe in some situation, ejbca's PKCS11CryptoToken driver that logs into the HSM session using HSM PIN only the first time, but skips logins thereafter. If we successfully create a dummy cryptotoken, we can use the authorized session afterwards, so there may not be a problem with skipped logins. hope this helps. regards, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
it is continued from #230
in above discussion, we could run ejbca correctly with ptk emurator mode hsm by using
ejbca-ee
andPkcs11NgCryptoToken
, then proceeding to real hardware (ProtectServer 3+ External).cryptotoken creation seems to work. but when we try to list keys in created cryptotoken, ejbca.sh throws following error
CryptoToken is not active
:of course, we created cryptotoken with
--autoactivate true
andejbca.sh cryptotoken list
shows it actually activatedkey pair generation also throws strange error which did not happen with ptk emurator mode hsm
Error retrieving objects to determine whether alias is used
:it seems that
Pkcs11NgCryptoToken
cannot authenticate itself correctly with real hardwareProtectServer 3+ External
.any ideas?
regards,
Beta Was this translation helpful? Give feedback.
All reactions