Problem with signature component. | Community
Skip to main content
diogomiranda
Level 3
June 4, 2019
Solved

Problem with signature component.

  • June 4, 2019
  • 7 replies
  • 7094 views

Hello,

app server:

cluster, topology

2 application servers, 1 cluster


db:

DB2 V11.1

OS:

AIX 7200-02-01-1731

When invoking the SignatureService I get the following error:

Error Calling SignatureService

com.adobe.livecycle.signatures.service.impl.DSSConfigurationHelper (initialization failure)

java.lang.SecurityException: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed

JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed

Jun 04, 2019 4:04:50 PM com.adobe.livecycle.signatures.client.types.exceptions.SignaturesBaseException

SEVERE: ALC-DSS-300-000 Generic SignaturesBaseException   (in the operation : certify)

Caused By: java.lang.SecurityException: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(AbstractResponseHolder.java178)

Caused By: com.adobe.livecycle.signatures.service.impl.DSSConfigurationHelper (initialization failure)(J9VMInternals.java96)

Caused By: java.lang.SecurityException: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(SignaturesInitializer.java69)

Caused By: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(null-1)

ALC-DSS-300-000 Generic SignaturesBaseException   (in the operation : certify)

Caused By: java.lang.SecurityException: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(AbstractResponseHolder.java178)

Caused By: com.adobe.livecycle.signatures.service.impl.DSSConfigurationHelper (initialization failure)(J9VMInternals.java96)

Caused By: java.lang.SecurityException: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(SignaturesInitializer.java69)

Caused By: JsafeJCE provider is disabled, a FIPS 140 required self-integrity check failed(null-1)

com.adobe.livecycle.signatures.client.SignatureServiceClient.certify(SignatureServiceClient.java:287)

pt.gbes.teste.SignaturePOC.CertifyDocumentSOAP.main(CertifyDocumentSOAP.java:117)

Caused By: com.adobe.idp.dsc.DSCException

com.adobe.idp.dsc.provider.impl.base.AbstractResponseHolder.handleException(AbstractResponseHolder.java:178)

com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkBindingStubUtil.deSerializeResponse(SoapSdkBindingStubUtil.java:132)

com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatcher.java:148)

com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:69)

com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:215)

com.adobe.livecycle.signatures.client.SignatureServiceClient.certify(SignatureServiceClient.java:264)

pt.gbes.teste.SignaturePOC.CertifyDocumentSOAP.main(CertifyDocumentSOAP.java:117)

Does anyone know what this mean?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Mayank_Gandhi

That is one way to check, or you can downgrade the JDK to 1.8.121 or below and test.

7 replies

Mayank_Gandhi
Adobe Employee
Adobe Employee
June 4, 2019

Hi Diogo,

what's the JDK version?

Adobe Employee
June 4, 2019

Is your signature bundle active

is this in aem forms OSGI?

diogomiranda
Level 3
June 4, 2019

Java version = 1.8.0_151, Java Runtime Version = 8.0.5.7 - pap6480sr5fp7-20171216_01(SR5 FP7), Java Compiler = j9jit29, Java VM name = IBM J9 VM

It's running on Websphere 9.

It's the JEE version

diogomiranda
Level 3
June 4, 2019

Apparently this can be solved by adding MD5 on java:

That's why you asked the jdk version?

Re: JsafeJCE provider is disabled

Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe EmployeeAccepted solution
Adobe Employee
June 4, 2019

That is one way to check, or you can downgrade the JDK to 1.8.121 or below and test.

diogomiranda
Level 3
June 5, 2019

Editing this file:

/usr/IBM/WebSphere/AppServer/java/8.0/jre/lib/security/java.security

As described in the link above solved it.

Mayank_Gandhi
Adobe Employee
Adobe Employee
June 5, 2019

Good to know that it is resolved now!