You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2007/12/13 15:05:43 UTC

[jira] Created: (RAMPART-121) Handling of KeyStores

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.

[jira] Commented: (RAMPART-121) Handling of KeyStores

Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600051#action_12600051 ] 

Hans G Knudsen commented on RAMPART-121:
----------------------------------------

Hi!

I will take a look at i and try to com up with a patch.

/hans

> 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.

[jira] Commented: (RAMPART-121) Handling of KeyStores

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598552#action_12598552 ] 

Nandana Mihindukulasooriya commented on RAMPART-121:
----------------------------------------------------

+1 for the idea, It seems that initializing Crypto is an expensive operation and it is a waste to do it multiple times. Can you submit the patch ?

> 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.