Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.5.7
-
None
Description
Having a problem with getting a key from one of keystores used by a web service client, I've patched and build my own version of WSS4J that adds keystore-identifying information to the exception thrown from CryptoBase.getPrivateKey() instead of only the looked up alias.
This way, I were able to identify the particular keystore the application was looking for key in.
I'm attaching my patch.
Note that similar improvements should probably be made to other methods in CryptoBase.
The exceptions currently thrown by CryptoBase only specify the alias which was looked up in a keystore. They may not be not sufficient in a complex set up with multiple keystores because they give no hint whatsover about what kind of keystore with what contents was the search performed in.