-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error after updating client key file #152
Comments
Transactions will complete successfully if |
I also believe, like suggested in #151 , that something appears to have changed in the keystore generation method. When iterating over the entries of our previous (working) keystore here, it iterates over multiple entries including the named certificates reported missing. When using the new keystore, only 1 entry (for the key) is found. Later, when an attempt is made to use the named certificate for signing, it's not found in the identities Map, resulting in the NullPointerError. Inspecting both keystores using the Comparing our working and not-working certificates using this method, one difference I notice is the lack of 'friendlyName' properties in the certificate entries. Can you confirm whether or not this attribute is is what's being used to name the 'Alias' entries in the keystore? Is it possible the missing |
Could you please generate the new key and see if it works ? |
Generating a new key does appear to have resolved the issue. Thank you. |
After attempting to update our expiring key with a new key (.p12 Simple Order key, generated from the Enterprise Business Center), we are seeing the following exception:
This was running on the SDK 6.2.3, But I believe I was also able to reproduce the problem using only the nvp
RunSample
class provided in the 6.2.10 SDK, which generates the following back trace:Restoring our previous key resolves the issue. I have also tried regenerating the key, which all appear to be valid keys, without success.
The text was updated successfully, but these errors were encountered: