Once integrated by following the readme guide, I got those errors in log file when clicking on "Send for Signature" from the docusign context menu:

• com.ibm.ecm.struts.actions.PluginAction.isSecureService() Invalid plugin id: DocuSignPlugin. This is likely a logic error in the plugin itself.
• com.ibm.ecm.struts.actions.BaseActionHandlerImpl.executeAction()
java.lang.NullPointerException

Hello emshedu,

Hope you're going great :) So we did setup the up-to-date Docusign plugin code, and configured the schedule async task as suggested in the readme. But when the task is triggered, it makes the websphere server crash.

Here is the log of our websphere server:
FINE: Enter addError: exception=com.ibm.ecm.util.security.CryptionException: javax.crypto.BadPaddingException: Given final block not properly padded
[3/22/22 12:01:00:343 CDT] 00000252 SystemErr R Mar 22, 2022 12:01:00 PM BaseTask run
SEVERE: Exception
com.ibm.ecm.util.security.CryptionException: javax.crypto.BadPaddingException: Given final block not properly padded
at com.ibm.ecm.util.security.Cryption.decrypt(Cryption.java:304)
at com.ibm.ecm.util.security.Cryption.decryptFromBytes(Cryption.java:242)
at com.ibm.ecm.util.security.Cryption.decrypt(Cryption.java:212)
at com.ibm.ecm.util.security.Cryption.decrypt(Cryption.java:192)
at com.ibm.ecm.icntasks.util.TaskUtils.getDecryptedPassword(TaskUtils.java:160)
at com.ibm.icn.extension.docusign.util.P8ConnectionUtil.getTargetOS(P8ConnectionUtil.java:63)
at com.ibm.icn.extension.docusign.tasks.CheckInSignedDocument.performTask(CheckInSignedDocument.java:80)
at com.ibm.ecm.task.commonj.work.BaseTask.run(BaseTask.java:104)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:267)
at java.security.AccessController.doPrivileged(AccessController.java:708)
at javax.security.auth.Subject.doAs(Subject.java:490)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:133)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:91)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:338)
at java.security.AccessController.doPrivileged(AccessController.java:738)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1174)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:199)
at com.ibm.ws.asynchbeans.CJWorkItemImpl.run(CJWorkItemImpl.java:237)
at java.lang.Thread.run(Thread.java:825)
Caused by: javax.crypto.BadPaddingException: Given final block not properly padded
at com.ibm.crypto.fips.provider.at.a(Unknown Source)
at com.ibm.crypto.fips.provider.at.b(Unknown Source)
at com.ibm.crypto.fips.provider.at.engineDoFinal(Unknown Source)
at javax.crypto.Cipher.doFinal(Unknown Source)
at com.ibm.ecm.util.security.Cryption.decrypt(Cryption.java:287)
... 18 more

Do you have any ideas why?
TIA

hello Emshedu,

I was wondering if the autocheckin process of the plugin was complete? I actually set the last version of the plugin and set the async task in my icn desktop but even if the async taks instance is complete, there is no change in the icons for the concerned document.

TIA

The send button remains disabled after selecting 1 or more users from the drop down.

This is with ICN 3.0.11.

If I remove the emailLookupPlugin.jar from the desktop and then try it again, the Send button is activated when a new email is added to the To line.

Trying to use this plugin I am running into the issue that the iframe (XDomainViewerWindow.html) presents a login page and then immediately presents the login prompt again: Your session expired. Log in again.
When loading the plugin directly
http://localhost:9081/icn/?desktop=embeddedViewerDesktop&feature=embeddedContentViewer&sideChrome=2
it works so there doesn't seem to be the issue.

I am using ICN 3.0.15/FN 5.5.12/WAS 8.5. Current hunch is that it is somehow related to session and cookies?!?

Hello emshedu,

I was doing some testing and found that the email for signature is sending the document twice to review. In my test, I have 2 recipients and as the document is sent twice within the email, my both signees have to complete twice the signing part before the process is completed
below the both review to do by each recipient