InfoPath Security
Microsoft Office InfoPath 2007 uses XML Signatures to let you digitally sign a form using a digital certificate. XML Signatures defines a standard for XML-based digital signatures that you use to help secure the data contained in XML documents. XML Signatures is a standard governed by the World Wide Web Consortium (W3C).
A digital signature is an electronic, encryption-based, secure stamp of authentication on a macro or document. When digitally signing an InfoPath form, the XML instance entered through the form is "stamped" with a digital signature (the signature public key and signed data digest is written to a dedicated node in the XML). This signature confirms that the XML document originated from the signer and has not been altered. InfoPath provides verifiable, non-repudiable signing, partial signing, cosigning and countersigning through enhanced digital signature support.
The SWIFT InfoPath forms generated with the FormGenerator utility provided by A4SWIFT use the countersigning method of digital signing to let signatures of countersigners to be stacked on top of each other. This countersigning signature stack models the human-oriented process of creating or editing a SWIFT message, having the message reviewed and approved by one or more reviewers and approvers, and finally submitting that message only after all stages in a workflow have signed off.
Repairers, reviewers, or approvers sign the message regardless of whether they approve or reject it. The signature signifies authenticity of the response and does not necessarily signify an "accepted" decision.
When the InfoPath form is submitted, it checks messages for validity and that the user signing the form is in the correct role.
If the message is rejected at any stage in a workflow (besides repair), the message is sent back to the repair stage. If the message is rejected at the repairer or creator stage, Message Repair and New Submission sends the message back to the Message Repair and New Submission orchestration instance with specific properties marking the message as rejected.
This section describes how Message Repair and New Submission handles the digital signatures based on the capabilities defined for a role. The role and capability combination is called a "stage" in the workflow.
Note
The "create" role is limited to a single creator across all departments.
This section contains:
Feedback
Kommer snart: Under hela 2024 kommer vi att fasa ut GitHub-problem som feedbackmekanism för innehåll och ersätta det med ett nytt feedbacksystem. Mer information finns i: https://aka.ms/ContentUserFeedback.
Skicka och visa feedback för