Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Signature

Signature

Select this policy assertion as described in Adding Policy Assertions.
A signature policy describes the parts of a SOAP message to sign with an XML Signature, using an X.509 Certificate token to allow for verification and trust of the signed information.
  • Inbound
    signature is for messages received for My Role services and for replies from invoked Partner Role services. It indicates that the My Role partner role accepts signed message content and will verify the signature.
  • Outbound
    signature is for replies from My Role services and messages sent to invoked Partner Role services.
Set the following parameters:
SignatureParts alias
Optional keystore alias used to retrieve the key to sign. The default is the alias specified in the crypto properties file.
Content Name
Message part or element to be signed
Content Namespace:
Target namespace of the message part or element
Example
<abp:SignatureParts alias="keystore_alias"> <abp:Element namespace="http://docs.oasis-open.org/wss /2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" name="UsernameToken"/> </abp:SignatureParts>
As a message consumer, Process Server service endpoints accept and consume messages that conform to options deemed allowable under WS-I guidelines. As a message producer, Process Server supports only the recommended algorithms, references and identifiers.
The following algorithms are used for signing SOAP message parts.
  • X.509 Token
    Direct Binary Reference (send and receive): Preferred method, used where possible.
    Issuer Serial (send and receive): Preferred external reference method, if direct not possible.
    X509 Identifier (receive only)
    Subject Key Identifier (receive only)
    Embedded Token References (receive only)
  • Signature Digest Algorithm:
    http://www.w3.org/2000/09/xmldsig#sha1 (send and receive)
  • Signature Algorithm:
    http://www.w3.org/2000/09/xmldsig#rsa-sha1 (send and receive)
  • Cannonical XML Transform Algorithm:
    http://www.w3.org/2001/10/xml-exc-c14n# (send and receive)


Updated March 30, 2020