[
https://issues.apache.org/jira/browse/RAMPART-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika reassigned RAMPART-197:
Assignee: Thilina Buddhika (was: Nandana Mihindukulasooriya)
> Rampart handler no
[
https://issues.apache.org/jira/browse/RAMPART-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
asela pathberiya updated RAMPART-326:
-
Attachment: RAMPART-326.patch
Patch for issue is provided.
> Soap faults would not be
[
https://issues.apache.org/jira/browse/RAMPART-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-281.
--
Resolution: Duplicate
This duplicates RAMPART-197
> Axis2/Java client throws exceptio
[
https://issues.apache.org/jira/browse/RAMPART-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Mishra updated RAMPART-324:
---
Priority: Blocker (was: Critical)
Issue Type: Question (was: Bug)
> Caused by: org.a
One instruction for using Rampant is to configure the bouncy castle.jar in
java security file in java runtime lib/security file
security.provider.99=org.bouncycastle.jce.provider.BouncyCastleProvider
There are many security providers out there, can this step be
skipped so that JVM uses other
Good Morning Jeff
you will need to specify another Crypto-J provider (such as the Crypto-J
provider from RSA)
be aware that The (Crypto-J) provider could become disabled if either
1)the JCE-required self-integrity check failed or
2)one of the FIPS-required self-tests failed.
a test harness to
