[
https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin....
]
Tomaz Cerar updated WFLY-4576:
------------------------------
Workaround Description:
- deploy as a module and use a dependency
- register in the JDK as any other JCE library
or add jboss-deployment-structure.xml
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<resources>
<resource-root path="WEB-INF/lib/bcprov-jdk15on-1.51.jar"
use-physical-code-source="true"/>
</resources>
</deployment>
</jboss-deployment-structure>
{code}
was:
- deploy as a module and use a dependency
- register in the JDK as any other JCE library
However: this means extra configuration, while shipping inside the war file requires none
at all.
JCE jar file inside a deployment fails the signature check
------------------------------------------------------------
Key: WFLY-4576
URL:
https://issues.jboss.org/browse/WFLY-4576
Project: WildFly
Issue Type: Bug
Components: VFS
Affects Versions: 9.0.0.Beta2
Environment: Wildfly build from master on April 22, 2015
Reporter: Tom Fonteyne
Assignee: Tomaz Cerar
Attachments: bouncycastle.zip
deploy a war file which contains the bouncycastle (or any other JCE) signed jar file.
Initialise and try to use a cipher results in a failure due to VFS not being able to read
and verify the file
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)