Hello Werner,
Thanks :). Its working perfect now.
I am not using the JAX-RPC handler outside Axis, our current requirement
was to keep in mind that we might use our code outside Axis. I am still
using the WSS4JHandler.java inside the axis.
Description :
I extended WSS4JHandler.java and override four functions.
loadEncryptionCrypto(), loadDecryptionCrypto(), loadSignatureCrypto(), and
loadSamlIssuer()
This allows me to load the keystore and SamlIssuer from our security
infrastructure instead of the property files.
Thanks,
Ashok.
On Sat, 21 May 2005 13:15:28 -0700, Werner Dittmann
<[EMAIL PROTECTED]> wrote:
Ashok,
just applied your patch and commited it. I also changed the way how
the handler serializes the resuting SOAP request to avoid unnecessary
namespace deleration.
Can you pls check if it all works? TIA.
BTW, can you send a schort description (or even a code snippet) to show
how you used the JAX-RPX handler? We miss some docu here.
Regards,
Werner
Ashok Shah schrieb:
Hello,
I am using the WSS4J's SAML profile. Because of our infrastructure, we
cannot use property files to initialize the security components for the
WSS4J handlers. I was able to remove the property files dependency for
the keystore by extending the WSS4JHandler.java class and overridding
the functions that return the Crypto instances (loadEncryptionCrypto,
loadDecryptionCrypto, loadSignatureCrypto).
The methods performSTAction and performST_SIGAction have private
access. The code to load the SAML Assertion (using the property file)
is located in this function. I was wonderinig if the piece of code that
loads the SAML Assertion could be seperated from this methods, and put
into a method with protected acces which returns SAML Assertion, like
the crypto methods.
Thanks,
Ashok
--
Ashok Shah
