[
https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974056#action_12974056
]
Thilina Buddhika commented on RAMPART-121:
------------------------------------------
Hi,
Now we have crypto caching in place to cache the crypto objects which will
address the above mentioned issue. More information about crypto caching can be
found in this mail thread [1].
The instructions on how to enable this crypto caching should be available in
the Rampart site. A jira is created[2] for this and a patch is submitted. Hope
this will be available in the next release.
Thanks,
Thilina
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
