ws-wss4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] Resolved: (WSS-195) More detailed exception thrown from CryptoBase.getPrivateKey()
Date Tue, 02 Jun 2009 12:04:07 GMT


Colm O hEigeartaigh resolved WSS-195.

    Resolution: Fixed

> More detailed exception thrown from CryptoBase.getPrivateKey()
> --------------------------------------------------------------
>                 Key: WSS-195
>                 URL:
>             Project: WSS4J
>          Issue Type: Improvement
>          Components: WSS4J Core
>    Affects Versions: 1.5.7
>            Reporter: Aleksander Adamowski
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 1.5.8, 1.6
>         Attachments: wss4j-CryptoBase_better_exception.patch
> 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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message