Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-3371

Make JBoss EAP 6 specific physical file deployment of BC provider

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.0.4
    • Component/s: None
    • Labels:
      None
    • Issue discovered during:
      Customer

      Description

      Using Oracle JDK there is an issue verifying signatures in crypto providers. Historically we have copied BC jars to server/default/lib in JBoss 5. For JBoss 77EAP6 this is much tricker...
      See https://issues.jboss.org/browse/WFLY-5 for a workaround that we can implement in EJBCA.

      We already have a jboss-deployment-structure.xml in EJBCA in src/deploy/ear/META-INF/, so it would be easy to test in a test environment with JBoss EAP 6 and Oracle JDK7 where you can reproduce the issue.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tomas Tomas Gustavsson
                Reporter:
                tomas Tomas Gustavsson
                Verified by:
                Mike Agrenius Kushner
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: