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 "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org> on 2008/04/22 07:01:21 UTC

[jira] Resolved: (RAMPART-10) Improve Rampart configuration

     [ https://issues.apache.org/jira/browse/RAMPART-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandana Mihindukulasooriya resolved RAMPART-10.
-----------------------------------------------

    Resolution: Fixed

This fixed in the trunk. Now we don't need properties files and we do using the  RampartConfig Assertion. 

> Improve Rampart configuration
> -----------------------------
>
>                 Key: RAMPART-10
>                 URL: https://issues.apache.org/jira/browse/RAMPART-10
>             Project: Rampart
>          Issue Type: Improvement
>            Reporter: Ruchith Udayanga Fernando
>            Assignee: Ruchith Udayanga Fernando
>
> Right now rampart requires uses to provide a property file to est the WSS4J crypto information. We have to move the information in this property file into an axis2 parameter to make the configuration consistent with axis2 ways of configuring.
> Also in the case when we use Merlin crypto impl in Rampart, the appropriate place to look for the keystore file  is 
>   - META-INF directory of a service
>   - classpath of the client
> Rampart should simply look for a keystore.jks or keystore.p12 file (JKS and PKCS12 cases).

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