EBICS Signing Service

The EBICS Signing service performs the EBICS signing and verification of order data on the SHA-256 digest, computed in pipeline mode.

The following table provides an overview of the EBICS Signing service:

System Name	EBICS Signing Service
Graphical Process Modeler (GPM) categories	All Services
Description	This service performs the EBICS signing and verification of order data on the SHA-256 digest, computed in pipeline mode.
Business usage	The EBICS Signing service performs a part of the packing and unpacking of order data.
Usage examples	A business process is called by the EBICS Order Processing service to either sign or verify payload data.
Preconfigured?	This service must be installed and deployed before it is invoked. No configuration parameters are required.
Requires third-party files?	No
Platform availability	All supported Sterling B2B Integrator platforms.
Related services	None
Application requirements	None
Initiates business processes?	No
Invocation	This service is invoked from a business process.
Business process context considerations	Use this service in a business process to either sign or verify order data.
Returned status values	Fatal - Nonrecoverable error Transient – Recoverable error Logic - Recoverable error Success Warning
Restrictions	None
Persistence level	System default
Debug	Debugging information for this service is located in Sterling B2B Integrator. Navigate to Operations > System > Logs > EBICS.

Output from Business Process to EBICS Signing Service

The following table contains the parameters passed from a business process to the EBICS Signing service:

Parameter	Description
action	Required. The action to be performed. Valid values are SIGN and VERIFY.
certAlias	Required if the value of certId is null. EBICS Banking Server certificate alias used by the EBICS Client if certId is not provided.
certId	Required. Certificate ID.
CommSessionId	Required. The communication session ID to which the service belongs to, for example, 012345.
pipelineTimeout	Optional. The pipeline timeout value. Default value is 300 seconds.
signatureValue	Required only if the value of the action parameter is Verify. Signature value in Base64 encoded format that must be provided for verification of order data. It is not required for signing.
signatureVersion	Required. EBICS signature version, for example, A005 and A006.
TransactionId	Required. The ID of the EBICS transaction, for example, TransactionId012345.
WfId	Required. The workflow ID of the transaction, for example, WfId012345.
trxSignId	Required if the value of mode is Server. ID of each EBICS signature.
mode	Optional. Indicates if the service is being invoked by the EBICS Banking Server or the EBICS Client. Valid values are Server and Client. The default value is Server. If you do not provide a value for this parameter, the default value is used.

Output from EBICS Signing Service to Business Process

The following table contains the parameter passed from the EBICS Signing service to a business process.

Parameter	Description
signatureValue	Required only if the value of the action parameter is Sign. Signature value in Base64 encoded format that must be provided for signing of order data. It is not required for verification.

Business Process Examples

The following example business process illustrates payload signing:

<process name="ebicssigning">
  <sequence>
    <operation>
      <participant name="EBICSSigningService"/>
      <output message="signRequest">
        <assign to="." from="*"/>
        <assign to="action"from="'SIGN'"/>
        <assign to="certId" from="'certid'"/>
      </output>
      <input message="signResponse">
        <assign to="." from="*"/>
      </input>
    </operation>
  </sequence>
</process>

The following example business process illustrates payload verification:

<process name="ebicssigning">
  <operation>
    <participant name="EBICSSigningService"/>
    <output message="verifyRequest">
      <assign to="." from="*"/>
      <assign to="action" from="'VERIFY'"/>
      <assign to="certId" from="'certid'"/>
      <assign to="signatureValue" 
from="'joeRiPzfV78gwZdENC3tH7nZqwWFPkMqT3fBmyUfNlFCAGUlGwLnBChRhRFr
l7jkg6IuRBhTDvhnmMIfl034XFbra6hzdyQicgdE3UzrDMAM5701RkrKFwueA0jdb8
BlBsm8ol5Ibe2PRDC10X5TMWsycfcR1LoxKvGsEGI/gXI='"/>
    </output>
    <input message="verifyResponse">
      <assign to="." from="*"/>
    </input>
  </operation>
</process>