Handling of KeyStores
---------------------
Key: RAMPART-121
URL: https://issues.apache.org/jira/browse/RAMPART-121
Project: Rampart
Issue Type: Improvement
Components: rampart-core
Affects Versions: 1.3
Reporter: Hans G Knudsen
Hi!
Looking at
https://issues.apache.org/jira/browse/RAMPART-78 /
https://issues.apache.org/jira/browse/RAMPART-25
I noticed that encryptionCrypto/signatureCrypto are initialized several times -
causing keystores to be re-read every time. At least through
PolicyBasedResultValidater.verifyTrust(...)
Would it be an idea to move these to eg. RampartConfig - which could the hold
the Crypto once initialized ?
I also looked for a way to hold the information clientside after sending
request - so that it could be reused when receiving response. MessageContext
could be the place - but unfortunately this does not work when using
ReliableMessaging.
Would it be legal in Axis to store an object in the AxisService parameters ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
